Any time I stage which jettisons a part with a script, I get a misleading flight log message that the program has run out of juice and that I need to charge my batteries.
Technically the part about the program not having any juice is true, but it's also no longer connected to any command module, or even part of the flight after it's staged away -- this would make sense as part of the local log, but not the flight log -- as I still have other vizzy programs running without issue on the active flight.
The message says to charge my batteries when they are at 99% -- my batteries are not the cause of the program stopping.
The message also implies I'd be able to resume the program; however this is impossible as the jettisoned part has no command module, no docking port; it's nothing more than an empty tube with some spent solid engine nozzles floating away to be destroyed.
GENERAL INFO
- Created On: Windows
- Game Version: 1.3.116.0
- Planetary System: Juno System
- Planets: 20
- Game Time: 6.0 days
CRAFTS
Name | Location | Part Count | Mass | Altitude | Velocity |
---|---|---|---|---|---|
Heliosync | Droo | 4 | 63kg | 954 km | 2.68 km/s |
Luna Flyby | Droo | 4 | 88kg | 29,236 km | 792.0 m/s |
Orbiter - Lunar flyby (Yuri) | Droo | 7 | 1,674kg | Ground | 0.0 m/s |
Juno Fly By | Juno | 4 | 55kg | 15,545.7 Mm | 3.42 km/s |
Lander | Brigo | 32 | 2,377kg | Ground | 0.0 m/s |
Docking Pod | Droo | 35 | 10,832kg | 500 km | 2.99 km/s |
Docking Pod-159 | Droo | 30 | 13,899kg | 97 km | 3.54 km/s |
Docking Pod | Droo | 35 | 10,292kg | 466 km | 3.03 km/s |
Docking Pod-163 | Droo | 30 | 12,738kg | 428 km | 2.91 km/s |