Kerbal Space Program

Thank you for your report. However, it does not meet the requirements for a critical priority. Please read our Guide for details on how to report an issue, and what the priorities mean.

As a developer, I'm sure you will appreciate the need for specifics when reporting a bug. These are sadly lacking here. Again, please refer to our guide.

The expected behaviour, if I'm correct in interpreting the report, is that when saving a game, that this will automatically be loaded when resuming again later?

The actual behaviour is thus:

• A persistence file is created at the start of a game.
• Auto saves are periodically written to persistence.
• A change of scene (eg going from Tracking Station to flight) or other significant change to the game state will also write to persistence.
• The persistence file is loaded when resuming a game.

• A quicksave creates a snapshot.
• Quicksaves are made pressing F5.
• A second quicksave overwrites the existing quicksave.
• Loading a quicksave is performed by pressing F9 for a few seconds.
• Quick saves do not overwrite persistence file, but the next autosave will.
• Quick saves are not auto loaded.

• Named saves also create a snapshot.
• These can be made from the KSC esc menu or by pressing mod+F5 key combination.
• These saves can be named, and have a suggested name of quicksave + an increment (quicksave1 etc)
• Loading a named save is performed using the mod+F9 key combination. Any save can be loaded from this menu, including the persistence file. This can also be performed from the KSC esc menu.
• Named saves do not overwrite the persistence file, but the next autosave will.
• Named saves are not auto loaded.

The persistence file is not versioned or incremented. It is a record of the entire world state at the current time (persistence defined)
Quicksaves are unique snapshots of the persistence at a particular time. Loading them will roll back to that time. My understanding of the report is that this is expected to be automatic.

It is unfortunate that you felt it necessary to throw games away, but the ability to preserve the game is available at any time, and furthermore can be restored to that state at any time. The persistence file is the only file that is loaded when resuming a game.

It is conceded that the save mechanism is not well documented, nor particularly intuitive, so as a result I have changed this issue to feedback. The alternative is to mark it as not a bug when the detailed explanation of the behaviour is considered.

Please be assured that steps are being made to improve the user experience of the save and load system.

[Addendum]

Case sensitivity is noted as having caused issues on Linux and OSX.

neuron wrote:

Both times this has failed for me I've tried to save over an existing savegame. I haven't gotten an error or anything like that, but it just hasn't updated the file. Therefor I assume everything is well, but So when I load the game again it's an ancient one.

This also overwrites the persistant world state, so I have no way to recover.

Thanks. The persistence will be updated, and this is by design. However, if a named save is not saving, then it is most certainly a bug.

A copy of the named save affected, together with copies of the logs that cover the attempt to overwrite can tell us a lot about what might be going wrong. Does saving under a different name work correctly for that particular save? If so, please attach both the original and the new save? Again, logs of the event are most useful.

Disregarding the autosave behaviour which sounds like it is working as designed, the failing to overwrite needs attention, but we really do need to get an understanding on why this is happening under some circumstances.

The actions of the enter and escape key are fixed now so this should no longer occur.

Closing. No response.