UI/UX Digit after decimal point on navball velocity display is always 0 when velocity is above 100m/s

[arthomnix]

Reported Version: v0.1.3 (latest) | Mods: too many to fit here; see https://i.imgur.com/jvTIoq1.png | Can replicate without mods? Yes 
OS: Windows 11 22H2 | CPU: AMD Custom APU 0405 (Steam Deck) | GPU: AMD Custom GPU 0405 | RAM: 16GB LPDDR5 (12GB usable; 4GB dedicated as VRAM)

 

When the vessel is moving above 100m/s, the digit after the decimal point on the velocity display is always 0, even if this is not the true velocity. (In the attached screenshot, the true velocity as shown by the Micro Engineer mod is 156.3m/s, but the game displays 156.0m/s.)

This bug can be seen in (as far as I know) every screenshot or video where the UI is shown and the vessel is moving at above 100m/s - as an example see the first 30 seconds of Matt Lowne's latest video:

The velocity is shown correctly up to 100m/s; once the vessel reaches 100m/s, the bug appears.

 

Cause and Fix

This happens because the game is configured to truncate the displayed velocity to an integer when the velocity is above 100m/s, but is also configured to always display this truncated value to 1 decimal place.

This can be fixed by setting the `dontTruncateValue` field of each `UnitEntry` on the velocity display to true. This fix has been successfully applied in version 0.6.0 of the Community Fixes mod. This results in the last digit of the velocity displaying correctly.

 

Included Attachments:

Edited July 9, 2023 by Anth12