I've now done a few test flights with the 170 and 195, both recently downloaded versions so they're up-to-date. For some reason the 170 will NOT hold speed at altitude regardless of whether it's FMS/MAN. In fact, in the video I took within X-Plane, I went to MAN mode and decreased the speed whilst the actual speed kept increasing. I suspect there may be some sort of coding error with the 170 that appears to not exist in the 195 regarding this. Please advise.
Addendum: I just did another test while in-flight. If you notice in the video my aircraft was assigned FL300 but it maintained altitude at 29980 (or 90) which is NOT altitude. So I put the aircraft in VS mode, made sure to climb the extra 20-30 feet to be literally at-altitude, and re-engaged A/T. It seems to work now.
So perhaps the issue isn't the A/T itself but the fact that, without intervention, this a/c isn't reaching the precise cruise altitude assigned and therefore the A/T isn't properly engaging?
This intervention seems to have worked since I've been flying at FL300 now for over 10 minutes and the A/T is keeping the speed within an acceptable range.
I hope this can be fixed but, until then, I suppose we can call it a "quirk" and flyers will need to ensure that their a/c is at the precise altitude they input.
Please let me know if this helps!
we are working into a new version that will fix this. the solution tip now is manually pitch few meters up.
thanks