Coming back to the INS drift simulation, I just completed a 9-hour flight from Sao Paulo to Lisbon. On purpose I did not perform any position update procedures during the whole flight. After parking on Position 801 in Lisbon, I performed the INS post-flight drift check by entering the parking spot in waypoint 1, activating track change 0 --> 1 and switching the INS Mode to DIS/TIME/

1. Actual position

2. LPPT Stand 801 coordinates --> Track change 0 to 1.

3. Distance offset for both INS 1 and 2 showing 0.0 nautical miles.

As you can see, at least for INS's 1 and 2 the net INS Drift over 9 hours of operation was 0.0 nautical miles. Which clearly indicates the INS Drift is still not there. p.s. Yes, INS Drift was enabled. I also flew with a buddy who flew out of Rio to Lisbon. Same result. No INS Drift.

I'll pass this along to the team, thank you.

I'll test this again. I did a 5.5 hour flight yesterday, and I did a couple of inflight position updates. Landed with a 1.4nm position difference. HOWEVER, that could have been a data entry error on my part. (The "INSERT" light does not light up after entering a latitude in HOLD mode. I don't know if it should or not, but I think someone should double check, since it's the only mode I've seen where it doesn't)

I have tested this again. The bug isn't what we think. They DO drift, but every time you enter a new waypoint manually, they magically reset to the correct, actual aircraft position. See video:
https://youtu.be/56t3ZEmLk9E?si=uG24GOAz-x2Nync7

2 hours ago, Joshua Green said:

I have tested this again. The bug isn't what we think. They DO drift, but every time you enter a new waypoint manually, they magically reset to the correct, actual aircraft position. See video:
https://youtu.be/56t3ZEmLk9E?si=uG24GOAz-x2Nync7

Very interesting. This would explain why while crossing the Atlantic and entering all waypoints manually, I pass directly overhead every waypoint because I keep resetting the airplane's position everytime I enter waypoints.

I may have mentioned it in another thread but if not I'll add it here that I have updated the team with the added information provided by Joshua

Hello all, this behavior has been refined already for the upcoming v.1.0.6; let me know in here how things progress following the release of v.1.0.6. Thank you.