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
I love how KerbalAlarmClock stored maneuver nodes with a maneuver alarm.
However, sometimes I wish I could import these saved nodes to the current vessel. For example, when I set up multiple nodes in advance, but then need to undock or dock, which means the vessel ID changes so the nodes are lost or attached to the wrong vessel.
Right now KerbalAlarmClock only states that the stored vessel ID no longer exists. There should be a way in this case (or even in the case where it still exists) to import the saved nodes, in the same way nodes are set when the selected alarm is already for the active vessel.
Alternatively, allow switching the vessel ID of an alarm to the active vessel, or make a copy of the alarm for the current vessel.
The text was updated successfully, but these errors were encountered:
Thats got some challenges as when you undock you will change the orbit and the maneuver will no longer be the same (only by small amounts, but wont match up). I'll have a think of if theres a quick/easy way to do that one
It's true that you have make minor corrections, but that's still much better than reconstructing the maneuver node from scratch.
Currently I do this by hacking the savegame and changing the VesselID of the alarm to the new one, which works just fine. So maybe all that needs to be done is removing the check on the VesselID (or rather, change the "replace node" text with "import node" when it doesn't match).
I love how KerbalAlarmClock stored maneuver nodes with a maneuver alarm.
However, sometimes I wish I could import these saved nodes to the current vessel. For example, when I set up multiple nodes in advance, but then need to undock or dock, which means the vessel ID changes so the nodes are lost or attached to the wrong vessel.
Right now KerbalAlarmClock only states that the stored vessel ID no longer exists. There should be a way in this case (or even in the case where it still exists) to import the saved nodes, in the same way nodes are set when the selected alarm is already for the active vessel.
Alternatively, allow switching the vessel ID of an alarm to the active vessel, or make a copy of the alarm for the current vessel.
The text was updated successfully, but these errors were encountered: