AP "Speed hold" visually fighting throller axis input
Since I have not seen this in the "tracked bugs":
When activating "AP speed hold" the 3D throttle in the cockpit starts to jump back-and-forth between the manual axis setting (from the HOTAS) … and the target throttle position which is computed (set) by the AP subsystem.
In my case I am using the Virpil CM2 throttle (bound to the single "throttle axis" input).
- T@Tasker
Same issue with Logitech Extreme 3D Pro. New issue from v1.0.2
Miltech Simulations @MiltechSimulationsWill Investigate
- In reply toTasker⬆:
@nenenuiI have this in v1.0 already … so (at least in my setup) it is not new in v1.0.2
- Miltech Simulations @MiltechSimulations
- @nenenui
I will make a video later today.
- @nenenui
I made a video … https://www.objectfarm.org/Public/Misc/2022.11.19-MSFS-MV22B-Bug-AP-ThrottleJumping.mp4
- I fly with AP but airspeed manually adjusted to 170 ktas
- I set AP airspeed to 220 ktas … activate it
- throttle starts jumping
- I deactive airspeed hold … it stops jumping
PS: Prior to that I again had one of those strange "AP rapid climb while HS Hold = 0 ft" … but sadly my video was not recording … but I will try to make a video of that some day
- Miltech Simulations @MiltechSimulations
Interesting, I haven't been able to reproduce this with my joystick. I'll investigate more with other throttle quadrants.
- Miltech Simulations @MiltechSimulations
I've been able to replicate this with a Saitek Throttle Quadrant.
It seems to happen at any throttle level EXCEPT 0. With the throttle at zero, the issue does not occur. With my regular throttle, this issue does not occur. It seems that it may be related to perhaps the refresh rate or sensitivity of some controllers.
Please confirm if lowering the throttle to Zero helps to keep the throttle from fighting. I'll investigate more the issue and look for a solution.
- @nenenui
I can confirm …
- if I activate speed HOLD … 3D throttle jumps
- I pull back my HOTAS throttle to zero … 3D throttle stay calm … and is placed according to AP
- … and pushing to axis "max" does the same trick as zero (at least with my Virpil CM2)
I also think that this is related to throttle axis sensor resolution (and maybe also ADC sampling "noise")
… for values above zero the axis will continuously send value updates to the sim … which triggers the "visual fighting"
… and most likely "zero" (and "max") are more "exact" (always the same value) and therefore do not trigger the jumping- Miltech Simulations @MiltechSimulations
That seems to be the issue indeed. Very likely this is other aircraft devs have experienced before. Added to the list of "requires more investigation but will be eventually fixed"