0.25 with 0.24.2 savegames strange behaviour

[evxxvi]

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.

[evxxvi]

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.

[vexx32]

You need to run KSP using the LC_ALL=C command. If you're running it via Steam, you'll need to go into KSP's Properties and Set Launch Options, then enter LC_ALL=C %command% (verbatim) and then confirm all dialogs. This will, however, not fix anything for the current save (and it'll only launch the x86 executable anyway). What's happened is that KSP has mis-read all the decimal points in the save file, treating the high-precision floating-point numbers as though they were immensely large (which results in a massive loss of precision, causing the weird physics issues you mentioned) -- basically, all decimal points are ignored and subsequently removed from the save file when the game is saved or autosaved.

If you have a quicksave you can revert to (that was before this issue appeared), it might work. If not, you'll need to go through your backup and infer the missing decimal points as best you can, save the file, then reopen KSP. Make sure you use the LC_ALL=C command, though; you can run KSP from terminal with it too, e.g., LC_ALL=C /Path/To/KSP.x86_64. This is, in essence, a locale issue.

[evxxvi]

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)!