Read many posts here from people, their app crashes after 5 or 6 hours.
it’s probably a good time to make stopovers. Will resume ultra long haul after this issue is fixed.
Just wanted to give another update on where we are with this issue.
We’re still hard at work trying to narrow this down, but we are making progress. As we mentioned in the past, it seems related to a third-party library Infinite Flight relies upon, and we’re trying to find what changed to cause these crashes, and how we can get this fixed soon so long-haul flights can resume without issues.
Hopefully more to share soon, but in the meantime, thanks again to everyone for bearing with us on this :)
What was your airplane count?
for departure it was medium then once I was airborne it was none
A workaround that could work in the meantime is to keep the camera pointing up while you’re flying so the terrain doesn’t refresh.
Cameras for that can be the tail cam pointing at the sky or freecam left where it is when activated since it won’t move)
Terrain code refreshes tiles when they are in view, is there are no new tiles to view, the code that causes the leak doesn’t run.
So you can take off, then in cruise, change to one of the cams above, and only switch back to the other cams when needed.
Some users have tested this and reported to us that they had some success.
As @Cameron said, we’re hopefully going to be able to share more soon.
It does work Laura. I’ve mainly done it to keep my iOS phone from overheating and when I wake up it’s stone cold still!
I’ve always naturally pointed the no virtual cockpit camera up to the sky and set it to night time. I have seen it works sometimes.
Ok thank you so much
App crashed 14 hours 29 minutes into flight just this morning :(
Settings ALL low, limiter ON, Plane count Low, will try sky-facing camera “fix” on second attempt at flight.
Are Iphone 11 Pro Max A13 gpu not yet supported?
Bummer how such a high-end device still managed to yield an App Crash on a ULH flight :/
Going off of this list:
Your crash was most likely related to something else and not due to the memory leak.
I’ve flown 18hrs to 22hrs on both iPad Pro (2018) and iPhone 11 Pro Max with settings on medium-high.
I also have the cinematic camera view when flying as I don’t find any issues with ULH flights anymore which I did in the early days of 19.4 launching. I’m also on iOS and iPadOS 13.3, and not 13.4, if that makes any difference.
All I have done to be able to fly ULHs is; Turning Off Anti-Aliasing and that’s basically what has worked for me. I know that similar settings for others have not gone that great and there are those with almost no issues at all from the get go with high end devices.
“something else”? I’ve diligently scanned the 19.4 troubleshooting guide a good 10 times, followed every step and tweak with the exception of this last “sky-facing camera” fix. Phone sits on a desk with full wifi bars to a 120mbps connection, last message on replay UI lists “reconnected to server possible connection issue detected”
Running in background were:
And this might actually be it. Connectivity issues may cause the app to crash. It is more likely in your case since your device have excellent performance metrics.
Ive erred on the side of caution ever since 19.4, actually my first app crash on 11 pro Max iPhone, but this was also my first 14hours + ULH attempt. Aliasing always off, graphics settings on low, airplane count low, limiter on, seems a waste of hardware playing this game on low everything… oh well
understood… i guess its a huge bummer how even with blazing fast wifi conxs. we’re still at the mercy of a wireless signal which can drop out any second :/
Anything else i should/could be doing to minimize the risks of this re-occuring, planning on having a go at the flight again in order to compare results
It’s quite unfortunate to say the least. The best we can do is to wait, as the Developers progresses further into finding some sort of solution.
I too have faced crashes at 10hrs and at 16hrs but the past two months I’ve been able to push both the iPhone and iPad to 20hrs+, but ofc I can not get anywhere near those 50 or 70hrs of flying like in the past :(
Speed is not the most important thing here. Stability is. That you’re running 3(!) separate apps hammering the API might not be improving the situation.
current wifi installation i must say is rather stable, reason for which i remembered to disclose using 3 third party apps, ill try ditching the Passengers App on my second attempt, appreciate your replies.
I did a long haul today on my ageing IPad Air 2, with medium range settingS. Adopting the approach of pointIng the camera to the sky has seemed to have worked! 11 hours in the A350 and no crashes. Thanks for the workaround Laura!