So I’ve started 2 flights trying to fly Madrid to Madrid (via Christchurch) in a A350. Once I reach cruising altitude I’m going 504 knots Ground Speed but then once I leave and check the map, the aircraft appears to be moving at anywhere between 3 knots - 10 knots GS. I tried ending the flight and starting a new one this time with the flight plan only going up to Christchurch but the same issue appeared.
Unfortunately I can’t attach a video but I did post it in the discord.
I’m confused on the problem. It shows a GS of over 500kts, and it looks like about 1 minute has passed between screenshots, and the plane has travelled an accurate distance for a minute of travel? I’m not bashing the problem, I’m just genuinely confused as to what the issue is.
Screenshot 1 says the AP+ expires in 47 hours 31 minutes while the 2nd one shows it expires in 45 hours 58 minutes it’s the only way I could show the passage of time. Just as another example, another 30 minutes later I haven’ even passed LEOT which is the next airport after LEAB.
Yep, this is all AP+ at the moment. I jumped back in and it seems to be travelling at the correct speed. But the moment I jump back out it goes back to travelling incredibly slowly.
Just as a second side effect, it appears I’m not showing up on InfiniteX or Infinite View anymore but still appear on my AP+. I tried refreshing my Infinite Flight app and it still says I’m there but tracking sites seem to think differently.
Yeah, that’s what I’ve been trying to figure out. I couldn’t find you I know this may not be ideal, but a reboot of the app might be the best decision. As in, deleting and reinstalling. I hate losing my replays, but it always works for me. This is most bizarre though
Yeah. I’ve been paying a lot of attention to the different bugs showing up on this most recent update, and I’ve seen nothing like this. Let me know if you choose to reboot or if something else works. I’ll want to store the knowledge away in case this comes up again.
I ended up uninstalling the game and reinstalling, but it seems like the bug is still there. I’m wondering if it has something to do with the length of the flight? Since Christchurch is literally on the opposite side of the world. I’ll delete the flight and retry with a shorter flight and get back to you.
So as an update, I have started a flight from SAWH to SABE, and looks like I’m flying at a normal speed now, which means this bug has something to do with incredibly long flights. I have no idea where the buffer is between getting the bug and not getting it since WSSS-KJFK seems to be fine where as LEMD-NZCH is not.
I know this may not be ideal, but a reboot of the app might be the best decision. As in, deleting and reinstalling. I hate losing my replays, but it always works for me. This is most bizarre though