UI/UX When in Target Mode Navball Indicators are Incorrectly Moving according to Rotational Speed

[Anth]

Reported Version: v0.1.4.1 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32GB

Following Shows the issue when it's bugged (0.1.4.1) and when it isn't (0.1.2.0):

Spoiler

0.1.4.1 Showing the Problem:
https://youtu.be/xuX0u4Nb6tY

0.1.2.0 Showing how it should be:
https://youtu.be/M8PWbOQX3vQ

Note:
The retrograde/prograde indicators are all over the place being affected by rotational movements in 0.1.4.1

Save File Used:
0120TestSave.json

Following shows it bugged but slower to give a better idea of what is happening:

Spoiler

0.1.4.1 Showing the issue in small/slow movements
https://youtu.be/nA70U_E8wR8?t=17s (Starting at 17s, watch the navball)

Steps to Replicate:

1. Load RotationalSpeedTestSave.json
2. Load again if there is spinning
3. Turn off SAS
4. Undock left craft
5. Timewarp for a moment
6. Target other craft
7. Change to target mode
8. Turn on Precision Mode (Capslock)
9. Use W ans S to move the retrograde indicator away a little from the target indicator and note rotational movement
10. Use W and S to move the retrograde indicator back to the target indicate and note rotation ceases

 

Note:
The speed of rotation is directly proportional to how far the retrograde indicator moves away from the target indicator

Credit:
Thanks to Discord chat for helping me get this bug report to a point of being more simply explained.

Edited October 2, 2023 by Anth12

[Stephensan]

i must say io haven't done a real fine docking since the "instant explosion" stage of the game, did a test, i saw similar results.

 

also nice 95 fps :3

[Anth]

1 hour ago, Stephensan said:

i must say io haven't done a real fine docking since the "instant explosion" stage of the game, did a test, i saw similar results.

Updated it. Hopefully it will make more sense now.