Hello, I took off at 14:53 local time, and right now it’s 23:37, that’s 8 hours 44 minutes, yet, the sim ( and infinite info ) has only registered 6 hrs and 56 mins of flight time?
MUC-PEK, will be descending shortly, there is also no way I’d have crossed all that distance in just under 7 hours! It’s been almost 9hrs.
I saw you did your flight on 25.1 - we have some improvements to the stats system coming in 26.1 which should handle flight time tracking when switching to/from AP+ better.
Looking forward to it! Yeah I switched back to 25.1 because the the the performance has been so stuttery for me on the beta, my iPad would overheat and the FPS would drop.
Though it works perfectly fine, and won’t even overheat at all on 25.1.
Thank You for your response!
Hello!
Just FYI - we’re seeing increased reports about this on RTM.
It’s being looked into but we’re fairly sure the flight time is still saved, it’s just not showing properly in the non-Beta version of the app.
But we’ll investigate and report back when we have something.
Small update:
AP+ flight time not being recorded on the RTM version (non-beta) of the app should be resolved now.
There is still an intermittent issue where flight time isn’t saved at all - unfortunately, that will remain until 26.1 is released. Our apologies for the inconvenience, but the fix requires a non-backwards compatible change that will address AP+ issues moving forward and will be included in 26.1.
Does the beta have the issues as well or only the current version. If not then I’m switching to the beta version cause this issue is kind of ruining the fun for me.
Same question! Does anyone have the answer?
Right now it went from happening occasionally to literally happening every single flight for me! It’s definitely so annoying.
Worst part is your flight will disappear from tracking apps as well. So you can’t track progress.
Does that issue happens in Beta too?
From what I’ve noticed, the issue happens when AP+ runs continuously for about 3 hours. After that, the flight may disappear from tracking, and any flight time past the 3-hour mark might not be counted.
As a temporary solution, for flights longer than 3 hours, you should re-enter the flight at every 2–3 hour interval of flight time. You don’t need to stay logged in for 2–3 hours just log back in briefly, then re-enable AP+.
For example, on a 10-hour flight, re-log at 2, 4, 6, and 8 hours of flight time. Avoid going past 3 hours without re-logging, or progress after that point may be lost.
It may seem annoying to re-log during the flight, but it’s better than losing your flight time.
Hey @DansSkuy! Welcome to the community form!
Thank you for sharing this helpful tip about AP+ and long flights. Your advice will surely help others avoid losing flight time!
I can confirm that the issue still exists in the beta version of the app. I just ended a 12+ hour flight AP+ in the beta version and it was recorded as 0 hours, 0 XP, not even 3 hours like the non beta version. It’s still a big issue
It’s important that you report this in Open Beta - it’s two very different things at this time.
Thank you for that helpful info! I will try that moving forward. But it’s definitely so annoying for an overnight fight! Hope it gets patched asap!
Hello, do I make new post there?
If you’re having issues in the Open Beta version of the app - yes.
In the normal version (RTM), it’s different.
Another small update:
We identified an issue in our AP+ server code that would make flights stop after 3 hours in given circumstances. We’ve now pushed a fix and this should be resolved.
So sorry for the inconvenience!
For both the beta version and 25.1?
Yes, it’s on the server so it’s for any version
Do we need to end the flight for it to take effect or will it work after we update the app?
If your flight is active on AP+ already, it’ll be fine. You don’t need to do anything extra or we would have specified 
