evxxvi

Uhh, Kerbal Alarm Clock can do such things? Have to take a closer look...

Hi all, the title says it: what is your rule of thumb for planning interplanetary injection maneuvers? To be more specific: only with in-game available tools, i.e., maneuver nodes. After some practice I can easily dock my space station from whatever kerbular orbit or go from Mun to Minimus or vice versa by intuition+maneuver nodes. I didn't get a deterministic rule of thumb for getting to Duna or Eve, even after some interplanetary practice following tutorials which magically bring me to the right trajectory. So how do you plan your interplanetary travel?

Yep: solution confirmed after updating I tried to run the binary without "setenv LC_ALL C" just to try wether it is still neccessary (I forgot to mention that). This messed up the savegames. Gladly backups were taken :-D After starting with LC_ALL set to C i could ingame load my backup savegame and all my orbiters are orbiting again :-) Someone should mark the thread as solved (I don't know how)!

It might be relevant that the system is Linux: Debian@AMD64. All native 64bit running the KSP.x86_64 binary. KSP 0.25 runs flawless on the system until old savegames enter the scene. I suspect that the problem is mostly about lost decimal points in savegame sfs files.

Hi all, short description what happend: 1. steam auto-upgrades to 0.25 from 0.24.2 2. find billions of science points in my science mode savegame (w/o cheating intention!!) 3. orbiting in savegame is nearly impossible... seems like physics time is totally out of sync with graphics time which is again out of sync with maneuver planning time 4. all saved flights are lost (several unmanned probes in stable orbits just vanished) 5. Starting a New Game works perfectly (but I don't want to loose my science progress). comparing 0.25ed savegame with old backup i find missing decimal points all over the place. Here one example: backup from 0.24.2: " SCENARIO { name = ProgressTracking scene = 7, 8, 5 Progress { FirstLaunch { completed = 103.759999999997 } "after loading in 0.25 " SCENARIO { name = ProgressTracking scene = 7, 8, 5 Progress { FirstLaunch { completed = 103759999999997 }" The wrong numbers might clearly mess things up.