Since updating to version 3.171, the indicated direction of the dropzone is very often incorrect.
Hi, That's an interesting observation. I can't quite figure it out (yet). Which software version did you update from? As far as I recall, there haven't been any recent changes to the direction calculation. But I'll be happy to look into it. We'll go through the code to see if there's any indication of such behavior.
if you have more background information, please let us know
@ajanky To be honest, I’m not sure what the previous version was, I think it was 3.15; but I’ve noticed a change in behavior: before, once the landing point was set, the arrow always pointed to the correct spot, whereas now, after the update, it’s often incorrect (sometimes significantly so).
OK, we made a code review for three versions, specifically from 2024, 2025, and 2026 (=V3.17x), and found no relevant code changes, as I suggested.
However, what we changed with the V3.17 is increasing the GPS acceleration limit to 2G because we sometimes noticed a short period of GPS dropouts exactly during canopy openings. This change can matter in the problem you have seen because GPS-heading filtering inside the GPS receiver is reduced for high-speed acceleration, notably in low-speed situations.
So we will add extra filtering for low-speed heading values and will see if this improves the arrow. It needs some testing, and I would be happy to send you a version with our edits to see if it improves.
Thank you for your input, we're working on this.
Andreas
@ajanky To tell the truth, I found this problem during the flight in an airplane.
