Autopilot+ Glitching continuously

Support
1

Device:Nothing 2A,6/256 gb
Operating system: ANDROID

I’ve been getting issues with my the Autopilot+ feature from past 3-4 days.What happens is when I’m around 30 mins away from destination and i press continue to resume flight,the flight literally starts from where i pressed Autopilot+ and pretty far from destination. I’ve attached screen recording here as well where you can see that my flight from EHAM to LHBP had 00:29 minutes to land and i resumed the flight and i went back to the start of autopilot+ with LHBP ETE again going over by an hour.The flight summary literally shows that I’ve covered maximum distance and even flight time is recorded correctly but the resumption doesn’t work.

I don’t know what is happening.I stay on the same network and everything stays same.I never encountered such problem before.I even uninstalled and re-installed the game and even restarted my phone but nothing seems to work and I’ve around 75+gb storage free in my mobile so storage might not be the problem. Does anyone know what should be done in such situation.

Google drive link for the recording - Infinite flight - Google Drive

2

Hello!

This is an issue we’re aware of occurring in version 26.1.1 that have been addressed for 26.2.
In most cases, the trigger for this issue is related to the flightplan being not more than just your departure airport and arrival airport. So if you know that’s a thing, try filing a full flightplan and hopefully it should be OK for you!

3

I’ll try this and let you know. I generally fill only departure and arrival airport in the flight plan,so I’ll check it a day or two and will update in the community.Thank you for your prompt response.

4

Hey, just a quick update.The solution you provided works.I had 2 flights after this discussion and in both of them AP+ worked successfully.I just added one waypoint extra between departure and arrival airport in the flight plan and it worked.So yeah a full flight plan or even minimum 1 extra waypoint in between works.

5

Great!

It’s not always that works. But in 8/10 times, that’s been the root cause of the issue.
It should be OK in the next update :slight_smile: