Posts by madpat

    I have an ipad pro 10.5 with 256GB. Airports I tested and experienced low frame rate were San Diego, Palm Springs and SFO. But in another thread this was already picked up by you.

    I noticed some new objects in Palm Springs and wondered whether this causes the choppy experience.

    Prefer the previous experience.

    Edit: SFO in R22 - unplayable. Flight school crashes App immediately.

    BTW: Again, I had to go to the app store, look for the FS2019 App and then click on the update button. The update was not announced on my ipad as usual.

    I am not a friend of these workable cockpits in mobile for several reasons, but it's impressive and the team did a smart move with letting the user choose whether to use them or not.

    BUT: Framerate decreased a A LOT on or close to airports when landing. SFO reminds me of C64 times. Textures flicker. Don't know what to say, I am both disappointed and impressed at the same time.

    Now that is really helpful! Thanks a lot! Still quite complex, but I'm sure a lot of thought went into it.

    So, now pleae adress that unintentional copilot interference even when switched off :S

    I don't understand the ILS behaviour in FS2019. When I am following a nav route in the Dash8, it picks up several ILS frequencys on the way (blue) but when I am approaching the designated ILS runway at my destination, it only shows the FMS approach. So no ILS diamonds, just the FMS altitude indicator (purple) and the, not sure what it is called, the indicator on the compass below the artifical horizon on the PFD.

    Even with the description above, the question remains why en route ILS is captured and displayed automatically, but not when approachinh my designated ILS runway??


    You paid 8€ for a sophisticated flight simulator with dozens of airports and several planes. While its desktop sibling cost around 50€, admittedly with more features.

    I mean, come on guys, you think the world is for free?

    Nevertheless, I hope for future updates, too, but we are not talking about Microsoft or Google here with thousends of developers. And Aerofly FS is certainly more complex than Angry Birds...

    Sometimes I really feel those developers deserve a little more respect than just adding items to a wishlist that can never be satisfied.

    Yes, the Discus bm allows to extend and use the propeller. Not sure though whether this plane is included from the start or if you have to buy it.

    Please note that some cool features of AF2 and 2019 are not in AF1, like PAPI lights, different daytime etc.

    Feels like the same behaviour as described by me, but here, thrust is also affected. And the plane trims in very very high speed. Trim wheels almost fall off8o

    For reproducing, I just set autopilot altitude to a lower one than currently flying at, then descend and slow down manually. It helps to be rather slow when approaching the selected altitude, then it goes all haywire.

    I'm not a pilot, but I could imagine this it what it feels like if an MCAS or other stall protection system kicks in unintentionally. Guess I will try this at night with zero visibilty, this will be fun.

    BTW: Thrust levers move in the 737 when this happens, but not the control slider.

    Yep, if you mean try the same with climbing to an altitude - same behaviour. When reaching the altitude in manual mode, plane pitches down, although autopilot off. Not so dangerous though, because thrust is usually higher and no flaps. Disturbing nevertheless. With glass cockpits, I think ALTSEL becomes highlighted.

    As mentioned in another thread about the copilot / autopilot interfering massivly although switched off, this happened again today and I figured out the pattern. I tried it three times afterwards with different planes (Dash8, LearJet, Cessna), and it happend everytime! Following is a description how to reproduce. The actual error is the autopilot still trying to keep altitude although switched off. The first few steps are just to make it reproducable quickly.

    • Select plane from the menu
    • Select a starting point in the air, lets's say 5,000 feet
    • start flight
    • Activate autopilot, press CTR for level flight (speed setting does not matter)
    • select a lower designated autopilot altitude, let's say 2,500 feet
    • select a V/S for descent, let's say 1,000 fpm
    • Before reaching the altitude, I change my mind and deactive the autopilot by touching that on/off button - all buttons are white now
    • Flaps 1, steady descent, zero throttle (depends on plane, of course)
    • AND NOW IT GETS HAIRY: When approaching the selected altitude, I see that the V/S of the autopilot (although switched off!) increases (see instruments or HUD view), until it even reaches positive values.
    • I do not move the device, but elevator goes back (can't see whether it's trimming or autopilot moving)
    • Result: Plane pitches up when reaching the altitude or is already below - but thrust is still idle, or at least way too low for achieving these V/S values - results in unusual attitudes or bevahviour.
    • Flaps are also retracted and extracted by copilot
    • It's quite a fight to get the plane under control again, it feels completely out of trim, but at a certain stage, autopilot is not messing up any more.

    Would be good of you could reproduce - and solve - this.



    After flying quite extensivly during the festive season, I collected some more feedback items from my side. It's not really sorted, made these notes whenever they occured to me or I remembered them. Although not always reproducable, I hope they provide some help for improvement nevertheless:

    • Some in-game hints need to be updated. Once, there was a hint displayed stating I should use the + and - buttons to change auto/co-pilot settings. These aren't there in FS2019.
    • Co-Pilot / Autopilot >> see my other post in the FS2019 co-pilot thread
    • Autotrim failed three times / trim runaway >> see my other post in the FS2019 co-pilot thread
    • PAPI-lights: Although now seemingly the same as in the desktop version (played that as well in the last weeks), they are not usable for me anymore, at least in daylight. In FS2, they have a nice halo so that you can recognize them very well in the final approach, but now I can hardly see whether they are red or white even when reaching the runway threshhold.
    • KingAir Flap setting 50 is not turning green when selected
    • VOR only works with glass cockpits. Cessna, Baron58 etc. show the same behaviour as in FS2: frequencies are fixed, and so instruments only work when close to these navaids. They don't take any input from setting a route in the navigation display.
    • There are some pixels / spots with completely different colours than the surrounding at various locations. Only a minor issue, though. Can easily be seen on the upper enging cowlings of the KingAir when looking at them from the pilots seat.
    • HUD view is quite useless now, because the compass with the route is now only visible when zooming out completely, and due to the fisheye-view is then quite distorted. Funnily enough, this also the same in the PC version, was much better in FS2.
    • HUD settings in the settings menu only works with the HUD view - where it makes no sense at all to me, because there is already a horizontal course displayed.
    • In the LearJet, there is no pilot when sitting on the co-pilots seat - scary =O. It is there when looking from the outside or passenger seats.
    • Same as in F2: Sometimes when I want to pan around, I am zooming. As if a second finger is on the screen, which is not. Maybe I need to clean my surface more often? ;)
    • R22 helicopter: when on the ground, pulling the collective / thrust lever full down will make it turn green - and not responding any more. I learned that in planes this act as some kind of parking brake? Only after catapulting yourself in the air again with that Lift-Me-Up button it works again.
    • Sometimes textures become missing. The most obvious part is south of the Mexican border, which you can already see in the maps. But even in flights, terrain became transparent in larger spots, either then white or one time I was even able to see the moon through it 8)
    • Same as in FS2: Sometimes I am "loosing" the rudder from below my thumb. Or it tries to sneak away from me, although keeping the thumb in the same position on the screen. Usually I am using it in manual mode.
    • F18 shadows/texture broken on runway.

    Guess that's it for now. Neverthless, I enjoy FS2019 A LOT :thumbup::thumbup::thumbup:

    Still amazed what you get nowadays for only 7.99 € (I'm coming from the ages when games cost real money in stores) and then on mobile - awesome!


    Oh dear, please let this be an option I can turn off. While it would certainly add more realism, it also shows me the limitations of flying with an iPad instead of on a PC with full equipment. When looking at Xplane on the iPad, where you can already manipulate all kinds of switches, its really frustrating zooming in and out while still having to fly with holding the iPad. Also, I think screen sizes are quite limited for that, except you have a 12" iPad Pro maybe. I always liked wiith Aerofly that it is quite simple to use, but fells very realistic nevertheless. Not only with the scenery, but also with the flight physics (not a real pilot, but it feels right). But if you make this manual mode an option, then why not.

    There seems to be an issue with FS2 and runway lights on some iPads. So, there is no Setting to turn on lights. But some airstrips actually don‘t even have lights, like Shoshone and Dunsmuir, I think.

    On my devices (iPad Air 1st gen and iPad Pro 10.5“, all with iOS 12), lights work.


    I had all but given up on Aerofly mobile but swung by here to see if there was anything new. I didn't realise a new version had been released. Given I participated in beta testing on the prior version and did a lot of promotion through YouTube content and forum r...

    I agree on most terms of your statements. Maybe we should consider this a „soft launch“, with us a testers of a release candidate version?

    To me, the developers‘ strategy makes some sense. Maybe they weren‘t so sure of this new version or the timing themselves, but wanted to give an Xmas present to those that look for it. I certainly did, but was totally caught out by surprise myself.

    Considering the most work went into streamlining the iOS version with the PC version code-wise, this is actually a new programme. But one that looks almost identical to the previous one, but lacking features (Switzerland). Hence the new compatibility. And so it even makes more sense to market it as a new programme, so that the FS2 can stay in the App Store for users that can‘t play the new FS2019 or want to fly in Switzerland.

    I really hope this is just the beginning now, which helps the developers to respond faster and develop new things faster as the code might be shared now in significant amounts. I also hope that there won‘t be any disappointing tradeoffs. If the unavailability of InApp purchases for regions or aircraft turns out to be one, wow, this would be a disappointment. Switzerland is a must, not an option, to me. Not because I‘m flying there that often, but because it is available in FS2 (although it took some time to find it‘s way there, too).

    For now, I‘m happy with the Dash8, better textures where before was just washed out colors, the whole new dimension of a helicopter.

    Nevertheless, I will open a new thread with a collection of issues I already encountered.

    Keep up the good work guys, and don‘t let yourself get turned down when reading ridiculous App Store reviews or requests like ‚I want to have a real time boarding experience‘ ;(


    It‘s the same rudder that you use in airplanes, on the bottom right of the screen. Have you tried to change the rudder assist in the control settings? I have them on manual and had no problems with the R22.

    In manual mode, you have to use rudder more intense while starting and landing, almost not at all when flying straight with the helicopter.

    I realised what the problem is with flaps in the King Air. Although the button says 50%, after pushing (or: touching) it feedback says "flaps 35". Can't remember now whether its degrees or perecent. Either way, the button stays white. Confusing.