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
Booting from archive fails when loading the ship (e.g. jumping from Tracking Station or Kerbal Alarm Clock).
The problem appears to be that:
The boot script is not copied from archive to local disk if starting from archive.
Home connection is not yet ready, thus booting from archive fails.
[LOG 20:55:23.877] [FLIGHT GLOBALS]: Switching To Vessel Relay ----------------------
...
[LOG 20:55:26.697] kOS: OnStart: Orbital READY
[WRN 20:55:26.700] kOS: First Update()
[LOG 20:55:26.717] kOS: Pushing context staring with: File Line:Col IP label opcode operand
[LOG 20:55:26.722] kOS: Saving and removing 0 pointers
[LOG 20:55:26.746] kOS: FlightControlManager.AddTo ddcc7e58-aec0-4084-9ebc-f7fc2f92fc05
[EXC 20:55:26.772] KOSVolumeOutOfRangeException: The Boot volume is out of range and not accessible.
UnityEngine.Debug:LogException(Exception)
kOS.KSPLogger:LogException(Exception)
kOS.Module.kOSProcessor:CheckCanBoot()
kOS.Safe.Execution.CPU:Boot()
kOS.Module.kOSProcessor:FixedUpdate()
So, it either has to copy the boot script to local drive even if starting from archive is enabled,
or there needs to be some mechanism added to wait until the ship is fully loaded or maybe even delay the boot until it can trully boot from archive (when connection is lost - wait for connection, signal that in the terminal allowing to cancel the boot by ^C).
Better explanation in the terminal would also help, but that is #2121
P.S.: The other (inactive) ship boots correctly when I jump to one that is near another. And my new version of Boot() prints Could not boot from /boot/boot.ks and Probably no connection to home (see #2121 for the code). The inactive prints Booting from....
The text was updated successfully, but these errors were encountered:
Booting from archive fails when loading the ship (e.g. jumping from Tracking Station or Kerbal Alarm Clock).
The problem appears to be that:
So, it either has to copy the boot script to local drive even if starting from archive is enabled,
or there needs to be some mechanism added to wait until the ship is fully loaded or maybe even delay the boot until it can trully boot from archive (when connection is lost - wait for connection, signal that in the terminal allowing to cancel the boot by ^C).
Better explanation in the terminal would also help, but that is #2121
P.S.: The other (inactive) ship boots correctly when I jump to one that is near another. And my new version of
Boot()
printsCould not boot from /boot/boot.ks
andProbably no connection to home
(see #2121 for the code). The inactive printsBooting from...
.The text was updated successfully, but these errors were encountered: