
Another is whitelisting the executable - both starsector.exe, and the java.exe found under jre/bin in the game folder - with whatever antivirus you've got running. One thing that might help is always running the game as administrator. So, if you manually rename "" to "campaign.xml", that should get you a working save.Īs to why this keeps happening for you, I'm not sure! One possibility is it's a file system permissions issue. In this case, it looks like step 3) failed for some reason. This is done so that if something goes wrong while saving, there's a chance that a working copy of the save will still be present. But there IS a .īasically, the process when the game is saved is:ġ) Write out a temporary file with the new save dataĢ) Rename the old campaign.xml to ģ) Rename to campaign.xml So, hmm the main savefile with the data - campaign.xml - is actually missing here. If you're able to send a non-working save to me (fractalsoftworks gmail com) that might shed some light on the situation, too. Chances are it'll be a more recent version that your latest save copy.Īnd, finally - what are the error messages you're getting? The stack trace from the log would be good to see as well. bak extension from the backup files so they get used by the game. What's in each save folder is:Īnd you want to move off the. Take a region pic where the ship is, make sure its symmetrical.

Search for the screenshot in the game files screenshot file (usually 'Starsectors installation location/screenshots') 3. So if a save fails to load, you can get back to the previous version by using the. Take an ingame screenshot with Print Screen or another button the command is bound to, while the camera is locked on the ship with T. If you're not aware: in your save folder, there's a backup for each save. In your shoes, I'd do this just in case - it's not at all certain that this is the problem, but better safe than sorry.)
#Starsector game save taking long windows
(It might be worth checking in windows Event Viewer to see if you're getting any System or Application errors that might point at, say, failing hardware, or some such. That's a bit unusual that is, I hear about an occasional save being corrupted in vanilla, but it being persistent like this is odd.
