They’ll also continue streamlining the 32-bit version as well. There’s lot of things that need to be optimized more, so until then we’ll see issues like memory leaks (which are tied to the problems with the pathfinder and lua, as well as being unable to save the game).
In the near future (hopefully this week), we’re going to push a build to the unstable Steam branch with two fixes. The first should fix the overwrite save bug. If the game crashes in the middle of overwriting a previous save, your original save should still be there when you start a new game.
The second is to add an experimental 64-bit version of the game. Only 3 or 4 people in the world have ever run with this thing, so it’s highly unstable. When it works, though, it should completely eliminate all crashing bugs due to running out of memory. Hooray! The 64-bit version of the game will run automatically if you are on a 64-bit operating system.
Long term, we’re going to work aggressively on using less memory so that even people running on 32-bit operating systems can run massive games without issue. This will take some time, but hopefully we’ll begin to address it in Alpha 9.
Decided to test this in [205], I was able to successfully save my town and save the Kingdom of Calgary. the 18 Hearthlings of Doom are no longer plaguing my kingdom.
I’m Game count me in for 64bit! If it doesn’t work I’ll just keep buggin ya till you get it working… well not in a whiny self entitled way, more like a kid at Christmas waiting to open a new gift Is it done yet!
I have encountered this bug in 205 and the save file that got overwritten had both the client and server .bin files but was missing the metadata.json and screenshot files.
I decided to test what would happen if I copied these missing files from a working save game into the broken save folder. As it turns out, the only downside was that the screenshot and info on the load page were identical to the save game I copied them from, so I had to edit the screenshot to make it identifiable. When I loaded the game it was exactly where I recall the broken save being created. I was also able to save again after loading and continuing the previously broken saved game.
Wow! Was just talking to @Ponder and he confirms that this could work IF the crash happens during the generation of the screenshot. It won’t work if the crash happens earlier. But how often does the crash happen during screenshot generation? This is where you come in. If you try this solution, let us know if it worked or didn’t work!