UI/UX New Burn Timer Displays Time Incorrectly When the Node is Above 99 Days.

[Anth]

KSP2 Version: 0.1.2.0.22258
Operating System: Windows 10
CPU+GPU+RAM: i9 9900K+3070ti+32GB
Mods Used: None

Screenshot:

Video Evidence:
Showing the issue going from 99 days which is good to 99+ when it isn't.
https://youtu.be/QPr2Uk-fsLk

Save File from Video:
https://www.dropbox.com/s/ni2ngkwfwjn8gg5/0120BurnTimerDisplayWrongSave.zip?dl=0

Edited June 1, 2023 by Anth12

[Filed.Teeth]

Looks like it switches to two lines from being full when it adds the extra digit, and the text is right-justified so the "T-" is pushed back to line 1?

I don't remember was it diff in Patch 0 and 1?

[Anth]

10 hours ago, Filed.Teeth said:

I don't remember was it diff in Patch 0 and 1?

Patch 2 has a new display. I never saw that happen with 0.1.0.0 or 0.1.1.0

Edited April 22, 2023 by Anth12

[Filed.Teeth]

Now that I'm looking at it, I've noticed something else. No allowance for years. The "Start Burn In" counter just rolls over to 0 after 424:05:59:59. 

Does the same in reverse, so if you set a node 435 days out, it will count down from 10 days, then switch to 424:05:59:59 when the 10 hits zero.

(and on two lines as long as there's 3 digits in the days.)

Edited April 23, 2023 by Filed.Teeth

[Anth]

2 hours ago, Filed.Teeth said:

Now that I'm looking at it, I've noticed something else. No allowance for years. The "Start Burn In" counter just rolls over to 0 after 424:05:59:59. 

Does the same in reverse, so if you set a node 435 days out, it will count down from 10 days, then switch to 424:05:59:59 when the 10 hits zero.

(and on two lines as long as there's 3 digits in the days.)

yeah there are other places that have similar issues. Like the AP/PE below the navball being limited to 6 hours.

[Dakota]

This has been fixed as of v0.1.3.