Hi,
The flight path marker is incorrectly tied the to Baro VSI. The velocity vector is based of GPS velocities, not baro.
Hello @MrTommymxr
The feedback I got so far is that this is the expected behavior for most avionics, Garmin ones included.
Do you have any source saying otherwise?
Regards,
Sylvain
When I perform a go around, I use the flight path marker to indicate positive climb as it reacts faster than the VSI.
Also this video. Look the 2 take offs and go around
There is a smoothing applied on the flight path marker position that possibly plays an even bigger role in the delay you observe.
This will be investigated further.
Regards,
Sylvain
There is actually very little smoothing applied to the FPM. Watch the videos attached.
In turbulence it can jump around a lot.
The problem is that the “VERTICAL SPEED” Avar is used which is tied to the “vertical_speed_time_constant” config and any pitot/static failures and not GPS
eg.
vertical_speed_time_constant = 0.01
vertical_speed_time_constant = 10
From personal experience I cant tell you that the smoothing applied is too much.
