Hey there community,
I’m publishing way too much of this tag nowadays…
You know the drill… I am using a brand new Ipad Air, with the latest IOS system, running as the only app IF (bought the Ipad to play the simulator) and more than 40gb free storage. I restart my Ipad before every flight and I have no apps in the background. I followed every moderator instructions about graphics etc…
My game crashed a few days ago 1 hour before landing after a 16 hours flight, my game crashed this morning after just 7 minutes using it doing pattern work in Greenland and my game just crashed when i clicked on my screen exiting Low Power mode during a long haul.
I am honestly quite desperate, i’ve been flying on IF since 2011 and I never had that much crashes of this sort on any device. I am aware there is a crashing issue on IOS but it really needs to get fixed, because even when I took a break from IF for months i kept my subscription to support the devs, but now that I can’t even do a full flight I’m getting tired.
No offense wanted but I’m sure you can all understand my frustration
But we’ve been waiting since December, 1/4 of my flights end up in a game crash on a brand new device, I’m sorry but it is unfair to pay for that service. I always and will always support the devs but come on. I can wait for the 777 and clouds but I just want to have a stable experience
Your device has 3 GB of RAM. This is different then your iPad storage of 64 GB. I personally only have 2 GB of RAM on my iPad and I can’t even do flights over 10 hours.This is just how it is right now with the memory leak issue. I’m sorry that you have to experience it as well.
Well, there is not really any solution here, hope a staff or a moderator hears me and might give us some news, because in the meantime, in my case, the game is almost unplayable and I might need to find an alternate
We are working on this. And have tried to the best of our ability explained the complexity surrounding this issue in a understandable way, in the topic previously linked. It’s as painful for us to have this issue lurking around as it is for you :(