Notes:
Crash first appear with the first version of ACE and so on.
It seem to happened after the same amount of game time, even if i take an old save and keep playing until i reach it, i get the CTD.
From the log file only the end seem relevant.
sysinfo | Memory Stats: Fatal Exception
sysinfo | Total System Memory: 15.939 GB (17114390528 bytes)
sysinfo | Current Memory Usage: 2.521 GB (2707275776 bytes)
sysinfo | Total Address Space: 8.000 TB (8796092891136 bytes)
sysinfo | Available Address Space: 7.997 TB (8792616792064 bytes)
sysinfo | Used Address Space: 3.237 GB (3476099072 bytes)
The xpcall is usually mod related and can sometimes be fixed by just closing and opening. The others were remnants of an older version of ACE installed. The Archipelago mod has also been updated to prevent some of these errors. I will test out the save to see what’s up
All fixed. The issues were caused by an outdated version of ace (Please update from the workshop by subscribing to it), you were out of inventory space ( I sold a few things to give you room ), and an ogre group spawn off map. Everything is fixed, you just need to update ACE. When you load this file, choose the GREEN button that says “Apply Mods”.
I have just tried the save and apply the mod change, but i’m getting the same result.
This is the new log and updated save.
I was trying to add some stone chest near my storage building and it CTD just after i add 2 of them.
Ok, in your Stonehearth file, can you please delete user_setting.json and launch stonehearth? It will create a new file. After that, can you please launch your save. You will need to pause the game the second you load in, teleport any idle hearthling you see in the town citizens window (by going to their character info window, and clicking the teleport icon in the upper right). After that, make sure you split your patrolling parties (knights/clerics/footmen/bowmen) into 2 groups (you can click the group flag color and then click the button with the 3 faces on it to add or remove hearthlings from each).
The save I sent you was run for a full day/night cycle and only this latest one, you’ve just uploaded, am I experiencing crashing with. I am crashing the moment the hearthlings start looking for food and a few are out of range.
Even after fixing, this error is happening (so I would redownload the upload I sent you, not the latest one you just uploaded):
2019-01-03 17:50:35.124167 | server | 0 | simulation.core | took 954 ms to update game state
2019-01-03 17:50:35.124167 | server | 1 | simulation.core | game loop exhausted before any jobs processed!
2019-01-03 17:52:44.805006 | server | 0 | simulation.core | took 120 ms to update game state
2019-01-03 17:52:44.806006 | server | 1 | simulation.core | game loop exhausted before any jobs processed!
2019-01-03 17:52:49.305004 | client | 1 | horde.general | over_lifetime_[rgb] properties are no longer supported. Use a single over_lifetime property.
There are also a few stuck hearthlings too, that are just standing in place. There should be 4 that you have to teleport to the surface or to an open space. Your food storage is too far from where they sit and eat at. The one hearthling (511238 Eyla Oppen) is attempting to get food and sit down, but her way to get to the seating is too far (when I tp her closer, I can atleast get her to finish eating before the game crashes)
Thanks for the help @Nikia, but this save is unrecoverable.
It keep crashing at approximatly the same moment in game.
I’ve move to another Save without ACE for the moment.
I encountered late game crashes with no dumps when trying to save my game. If this is the case, I have found 90% of the time an item is bugged, and selling it triggers a crash upon saving. I rapid fire save & load emptying my inventory of non-essentials until landing on the item that causes the crashes. With a bit of repetition you can manage to sell or delete the item and save, giving you a checkpoint of sorts to continue past the bug. From there you shouldn’t encounter any more problems.
This is all assuming you had the same type of crashes, but perhaps troubleshooting your inventory is necessary.
With some experimentation however, it might be a gearbox getting picked up / moved that’s breaking things. Will keep playing for a bit but I destroyed the block instead & it hasn’t crashed yet.
