Map & Tracking Station Changing Thrust Limiter Settings not immediately recognized by current Maneuver Node

[dansiegel30]

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Win10 | CPU: Intel i7 10700 2.9GHz | GPU: NVIDIA 2060 Super | RAM: 16GB DDR4

 

When attempting to perform precise maneuvers, the accuracy of when the maneuver starts and stops is vital.  When performing this manually, the longer the burn duration, the more accuracy can be given to the DV amount applied in the burn.  This is needed, even though the LEDs and sounds for burn stop and start in an AWESOME improvement over KSP1 in this regards.  Extending burn duration is even MORE important during correctional burns, when the engine being used was primarily meant for injection burns, not minute course corrections.  Therefore small DV burns quite often have a 1 or <1 second burn time, which can yield a large inaccuracy when done manually.  Increasing that small DV burn duration from 1 second to 30 seconds as an example can vastly improve the accuracy of the resulting burn.  However, when changing the Thrust Limiter setting of the engine AFTER creating a maneuver node does not automatically adjust the duration of the burn (as indicated in the Burn.Timer window's "Stop Burn In" parameter).  At this point the use, can delete the maneuver and re-create it again, or MODIFY the burn, which apparently sends an updated value of the Thrust Limiter parameter, causing a recalculation of the Stop Burn In parameter.  Thus, the Stop Burn In parameter needs to be automatically updated if and whenever the Thrust Limiter parameter is changed, and an existing maneuver has already been created.

 

Video Evidence:

 

 

 

Edited November 18, 2023 by Anth

[Anth]

@dansiegel30 Embedded your video. (moved your other bug report with the same issue to the archive.