v1.0.4 (and prior) … I now can reproduce (trigger) the shifted HDP digit bugs (and I have a video too, if needed)
- I activate the AP … and set a HDG
- When I use the 3D cockpit button … I can turn on-off the HDG hold just fine
- When I use the command binding for "Toggle AP HDG Hold" then
- the Y base point for the last (third) digit starts to shift from the normal base line
- and multiple toggle actions continue to shift the base line … while also changing the on-off state.
Not sure which language is used for the AP code … but if it where "C" then this somehow would feel like "memory corruption" to me, as there is no logical relationship between the on-off state … and a base drawing coordinate … the only logical relationship seems to be the code (struct) proximity.
- Miltech Simulations @MiltechSimulations
Please share the video. We’ve never used command bindings to test the autopilot (except for master AP engage/disengage), so likely that’s why I’ve never seen the issue.
- @nenenui
In this video … https://www.objectfarm.org/Public/Misc/2022.12.03-MSFS-MV22B-Bug-AP-HDG_digit_jump.mp4 … you can see:
- 0:00 … a shifted third HDG digit
- 0:01 … I press the 3D HDG Hold button … the digit stays as it is
- 0:08 … I turn the HDG dial … it corrects the display again
- 0:20 … I start using the HDP Hold command binding … and now the third digit starts jumping
- 0:26 … now even the second digit did jump … from 220 to 210
- however … the Osprey is not trying to turn … it stays on 220 deg
- … so this is only messing with the display, and not the real "target HDG" setpoint.
- Miltech Simulations @MiltechSimulations
Thanks, will investigate the issue.
- Miltech Simulations @MiltechSimulations
It seems that the input binding is outputting decimal values (x.1-x.9) while the knob rotation gives exact integer values, hence the issue.
We are looking at a possible solution.
- Progresswith handling this problem
- Miltech Simulations @MiltechSimulations
Still investigating, haven't found a solution for this issue yet (low priority for now)
- Miltech Simulations @MiltechSimulations
We have a potential fix for this issue, however, we would like to share it with you for testing before we release the fix publically. Could you please email us at contact at miltechsimulations dot com?