So is it bad for my phone to play aerofly while not plugged in?
I wouldn't say so, just means you need to recharge more often. I think the iPhone is rated for around 500 full recharge cycles before you would see any degradation which means a daily recharge would see you get over a year and a half before that may potentially be an issue.
I left AF2 running on my works iPhone 5 when plugged in so I could test flying round the globe. With brightness up, it got very hot. It gets warm on the IPhone 6 but more localised and not as warm. I have the brightness turned down and limit framerate turned on. Never noticed it in my iPad Air 2 or mini 2 but they both have a decent case on. Will try the 5s today.
With the ability to fly around the globe and new regions getting added, it would be great if we could A.Fly between regions and B.Skip forwards through time or more likely distance.
I'm thinking of the scenario where you can set SFO as the departure point and select Paris say as the destination airport using the Navigation page if Paris was an available region. Now when you take off and set autopilot for your heading, it would be great if there was a distance skip feature where by tapping it progressed you in 100 mile increments. This would make long haul flights a real option in the game as you could you keep tapping the skip distance button to progress through your flight and then fly the last ~ 100 miles in to land. A real long haul flight could be completed in about 20 minutes if needed. At the very least, you could skip past all the lower resolution imagery and focus on the more involved parts of the flight.
I think this could be a great future feature.
Well I have no prior knowledge of nav so will be more than happy to give it a try and feed back. 
I want this to act as a master list for known bugs so people can update with bugs found or search to see if it is a known issue. Please let me know of others and I will update the list in bullet form on the first post. Please keep the thread on topic and advise if anything listed is not a bug or is now resolved.
Bugs:
Thanks Gary. I haven't tried this kind of navigation so will give this a try over the weekend if I get some time. I'll just need to try and summarise your instructions into a more palatable flight plan of sorts as it is a lot of information to go through during the flight.
Should be fun.
Donka, maybe it's time to rename the thread to something like "Pending issues" or simply "Bugs"...
Yup, it was called this at iPacs' request.
IPACS Support, do you have an alternative way for us to track bugs or issues in Aerofly 2 or will we just create a single Bugs thread?
Not a glitch as such but just tried out the 737 on the iPhone 6 there and the Autopilot controls at the bottom are very hard to distinguish against the cockpit dials in bright sunlight. I much prefer the positioning of the AP controls down here as opposed up top but they may need a little contrast or colour option to make them more visible in such scenarios?
I don't get the whole wish for being able to turn on seatbelt signs and the like but would certainly like to hear altitude announcements on final.
A couple of graphical issues I wanted to highlight. On approach to runway 29 at Oakland, the start of the runway flickers as you approach. This is more obvious in cockpit view - see attached cropped Image.
The HUD view on the Aermacchi goes into the ground when on a runway.
And that reminds me, there is a similar issue at the start of runway 29 at Oakland as you come in to land. It is easiest to see in cockpit view but can be seen from some other views to depending on aircraft and angle.
OK, I can replicate the flicker on both a mini 2 with Retina and the Air 2. It's harder to see on the mini and best to zoom in to see it. It happens in normal flight but I think it is exacerbated by the slightest of movements.
I noticed that if you set autopilot for altitude and once you reach that altitude, the flicker is much less pronounced, to the point of disappearing. If you then pan your view a little left or right then it returns so I suspect it is related to the current point of view and because the view in the is cockpit is dynamic, anything that alters that such as normal hand movement or moving the angle of view when on the level brings it back.
Sorry I forgot to put the version of aerofly, it is 2.0.3
That explains why I could replicate the issue! 
Really looking forward to the new regions.
Great video Donka!
What software are you using to capture video and audio with such high quality?
Btw, I can't see the flickering glitch on top of the cockpit's panel. Can you confirm if there's any noticeable artifact in the cockpit of your P-38?
Thanks. I'm just using Quick Time player on the Mac with the iPad plugged in via USB.
I'll check again did this flickering but I haven't noticed it so far.
Posted a video of the P-38 in the videos thread.
An overview of the P-38 Lightning in 2.0.5 on the iPad Air 2. No commentary, just raw video.
[video=youtube_share;vMNaoaGfa1o]
Just tried Sacramento Mather. Both runways, both directions with a couple of different aircraft. I can't replicate the sinking issue.
So my iPad air 2 won't see clouds if you create them
The Air 2 is currently the most powerful iOS device available. It's a certainty to see clouds.
