You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Don't delete the last manœuvre node from the navball until the node is deleted from the flight plan (or the flightplan itself is deleted, obviously).
Rationale:
Having the blue indicator available after burn can be very helpful for course corrections with RCS afther the node, to compensate for too short or long burns, do some minor adjustments - and it would help immensely with kOS.
Often I use kOS for node execution with principia. Once my manœuvre is all set up, I type this into the console: sas off. lock steering to nextnode:deltav.
Then I wait until principia tells me to ignite the engine, and do this... lock throttle to 1. wait 231.4. lock throttle to 0. unlock all.
Problem is, once the burn duration (231.4 seconds) is up, the navigation node is deleted by principia, causing kOS to panic and nope out of program execution.
PS: having a way to get principias burn duration and ignition time for the next node into kOS would be really cool :)
The text was updated successfully, but these errors were encountered:
In addition to kOS, issue exists when not burning full throttle for additional precision. MJ disables stability augmentation entirely, causing imprecision. Even when keeping the last known node position (either SAS or KILL ROT), it drifts off designated prograde/retrograde et al. markers.
issue exists when not burning full throttle for additional precision.
Agree. When you finishing burn, it's better to smoothly decrease throttle, for more precise delta-v. But maneuver point on navball already disappeared.
Don't delete the last manœuvre node from the navball until the node is deleted from the flight plan (or the flightplan itself is deleted, obviously).
Rationale:
Having the blue indicator available after burn can be very helpful for course corrections with RCS afther the node, to compensate for too short or long burns, do some minor adjustments - and it would help immensely with kOS.
Often I use kOS for node execution with principia. Once my manœuvre is all set up, I type this into the console:
sas off. lock steering to nextnode:deltav.
Then I wait until principia tells me to ignite the engine, and do this...
lock throttle to 1. wait 231.4. lock throttle to 0. unlock all.
Problem is, once the burn duration (231.4 seconds) is up, the navigation node is deleted by principia, causing kOS to panic and nope out of program execution.
PS: having a way to get principias burn duration and ignition time for the next node into kOS would be really cool :)
The text was updated successfully, but these errors were encountered: