Time to Apoapsis is Wrong Once You Pass It While Suborbital

[whatsEJstandfor]

Version 0.1.0.0.20892, Win11, Ryzen 9 3900X, Radeon RX 5700, 32 GB

When on a suborbital trajectory (in this particular case, I just launched a Kerbal-K1 vertically to an apoapsis above the atmosphere and then killed the engines), the time-to-apoapsis countdown is correct up until the actual apoapsis. At that point, the time is still listed in terms of T minus, but the timer starts counting up. In my screenshot, I reached apoapsis 38 seconds ago, and the "AP in" readout says T-00:00:38. Note my retrograde marker and vertical speed indicator; I'm now on a collision course with Kerbin.

I suppose I would have expected it to either read "AP 78,270 m in T+00:00:38" or "AP 78,270 m in N/A"; whatever would most clearly convey that I've passed apoapsis and won't be reaching it again since I'm suborbital.

Incidentally, I actually believe it'd be clearer if the "T-" was dropped altogether. As in, if I were reaching that same apoapsis in, say, 60 seconds, I think it should read "AP 78,270 m in 00:00:60". I think adding "T-" gives it some flavor but it also doesn't make much sense, and it doesn't add any information.

Edited February 26, 2023 by whatsEJstandfor