This is happening too early. Change should be at M.82 but it already noses down at .78. Maybe already mentioned but I couldn't find anything

I previously reported it here:

That topic was locked as a fix is supposedly already in progress. Hopefully the changelog for the next update will have a fix for this issue in it...

6 hours ago, zbrainlezz said:

I previously reported it here:

That topic was locked as a fix is supposedly already in progress. Hopefully the changelog for the next update will have a fix for this issue in it...

Fixes regarding this look to be making their way into 1.0.3 barring any unforeseen circumstances. Thank you 🙂

Thanks

2 hours ago, IniJamir said:

Fixes regarding this look to be making their way into 1.0.3 barring any unforeseen circumstances.

I very much hope so, as right now that's one of the last major issues that's preventing me from making a fully satisfactory flight with the TriStar. Thanks 👍

This issue (VNAV mode transitioning from IAS to Mach too early in the climb, and vice versa too late in the descent) is unfortunately still present in 1.0.3. Another issue that has still not been corrected is that the autopilot's actuation of the stabilizer trim is too slow when in IAS and MACH vertical modes, causing constantly alternating overshoot and undershoot of the target speeds and therefore slow vertical oscillations. This means I have to use VS mode to correct when the aforementioned VNAV problem occurs. I hope these issues will be fixed in 1.0.4, as again, they are the last major problems that prevent me from fully enjoying the plane.

Edited April 21Apr 21 by zbrainlezz

This issue is still present in 1.0.4. It's seriously beginning to get on my nerves, especially since the IAS and MACH modes also still don't work properly.

I can confirm this issue is finally fixed in 1.0.5. To the dev team: thank you very much. One more major issue fixed.

Glad to hear it :)