Confirmed with the latest build 2081. I’m getting the same thing after every new save using the Steam build.
Same problem here. Cleaning out the save game folder is no help BTW. Seems like a rather serious error in the graphics engine (Horde3D = open source rendering engine).
Time to page @sdee, @Ponder et al I think; hopefully they can get a fix out in the next day or two for this.
I want to look at @Silas game file, and see the save root in the files. See the difference. He said he not getting the problem with latest build. Maybe it just needs some lines readjusted or rewritten or added. 
I’ll give it another load tonight to make sure and then post it up
Okay cool. I hope its just a line direction code. If so it might be an easy fix.
Yes please 
I think a few would really appreciate it very much. Even if it doesn’t work for.
Also seeing this bug. Win7, Intel HD4000 integrated graphics, playing the game through Steam, and running the 2081 dev build. The bug appears whether I try to load a saved game (Load…) or use the default (Continue…) menu options. Both saves that have been corrupted in this way featured substantial underground digging and I may have exited while the game was in “Slice” view.
I also have had the game crash to desktop once with this build but didn’t get an error dialog.
Here is the save File. Build 2081, This is save number 5 i think.
Let’s see if it works for anyone else!
1 Like
Doesn’t work. I get the same error. Uninstalled the game from steam and deleted all the local content and tried with the same result as well.
Okay gonna look at file, but I think it the actual game code, that I need to see, where the code line is to direct where to load and continue the saves. I need to see that. The problem is, it is trying to load the saves from a different source. that doesn’t exist.
Same here - get an Assertion Failed Error too - build develop 2081:
Here is the savegame:
Hope this helps in any way …
The save file won’t load. @Silas, send me your radiant folder in c:\ I think that what most are missing, if you don’t have it, then I don’t know why we can not load, it missing a command in the direction or we are missing the egRendererBase.h:65 file. I looked through all of stonehearth and can not find it.
Edit: This is from your saved game, in the log.
2015-Jan-24 21:52:34.302166logger initialized
2015-Jan-24 21:52:34.303166 | server | 1 | app | Stonehearth Version 0.1.0.2081
2015-Jan-24 21:52:34.303166 | server | 1 | simulation.core | QPC count: 99183479348, frequency: 3312871
2015-Jan-24 21:52:34.303166 | server | 1 | simulation.core | QPC count: 99183479525, frequency: 3312871
2015-Jan-24 21:52:34.303166 | server | 1 | simulation.core | QPC count: 99183479720, frequency: 3312871
2015-Jan-24 21:52:34.303166 | server | 1 | simulation.core | QPC count: 99183479909, frequency: 3312871
2015-Jan-24 21:52:34.303166 | server | 1 | simulation.core | QPC count: 99183480091, frequency: 3312871
2015-Jan-24 21:52:34.303166 | server | 1 | simulation.core | QPC count: 99183480232, frequency: 3312871
2015-Jan-24 21:52:34.304166 | server | 1 | simulation.core | QPC count: 99183480418, frequency: 3312871
2015-Jan-24 21:52:34.304166 | server | 1 | simulation.core | QPC count: 99183480604, frequency: 3312871
2015-Jan-24 21:52:34.763193 | server | 0 | lua.data | lua jit is enabled
2015-Jan-24 21:52:35.402229 | server | 1 | resources | Modules are verified prestine.
2015-Jan-24 21:52:35.419230 | server | 1 | app | Running Stonehearth server on port 48916
2015-Jan-24 21:52:35.440231 | server | 0 | mod stonehearth | greedy task scheduling enabled
2015-Jan-24 21:52:36.015264 | client | 1 | browser | cef started.
2015-Jan-24 21:52:36.027265 | server | 2 | network | server allocating new send buffer (total: 0)
2015-Jan-24 21:52:36.060267 | client | 2 | network | client allocating new send buffer (total: 0)
2015-Jan-24 21:52:44.537752 | client | 0 | client.core | loading save “1422076152566”:
2015-Jan-24 21:52:44.538752 | client | 0 | client.core | {
2015-Jan-24 21:52:44.538752 | client | 0 | client.core | “name” : “”,
2015-Jan-24 21:52:44.538752 | client | 0 | client.core | “town_name” : “Scyllaton”,
2015-Jan-24 21:52:44.538752 | client | 0 | client.core | “game_date” : “day 10 of Deepmun, 1000”,
2015-Jan-24 21:52:44.538752 | client | 0 | client.core | “game_time” : “10 : 23 pm”,
2015-Jan-24 21:52:44.538752 | client | 0 | client.core | “time” : “1/23/2015, 10:09:12 PM”,
2015-Jan-24 21:52:44.538752 | client | 0 | client.core | “version” : "0.1.0.2081"
2015-Jan-24 21:52:44.538752 | client | 0 | client.core | }
2015-Jan-24 21:52:44.538752 | client | 0 | app | Assertion Failed: i != end(c:\radiant\bamboo-remote-agent\buildroot\sh-ob-build\stonehearth\source\horde3d\source\horde3dengine\egRendererBase.h:65)
2015-Jan-24 21:52:45.053781 | server | 1 | simulation.remote_client | started buffering client updates. (seq:184 ack:174)
2015-Jan-24 22:03:36.197025 | client | 0 | sysinfo | Memory Stats: Fatal Exception
2015-Jan-24 22:03:36.197025 | client | 0 | sysinfo | Total System Memory: 7.983 GB (8571527168 bytes)
2015-Jan-24 22:03:36.197025 | client | 0 | sysinfo | Current Memory Usage: 162.953 MB (170868736 bytes)
2015-Jan-24 22:03:36.197025 | client | 0 | sysinfo | Total Address Space: 2.000 GB (2147352576 bytes)
2015-Jan-24 22:03:36.197025 | client | 0 | sysinfo | Available Address Space: 1.518 GB (1629687808 bytes)
2015-Jan-24 22:03:36.197025 | client | 0 | sysinfo | Used Address Space: 493.684 MB (517664768 bytes)
1 Like
I’ve dug into the game engine a little deeper and the error is coming from one of the two following functions at the assert lines:
void remove( uint32 handle )
{
ASSERT( handle > 0 && handle <= _objects.size() );
_objects[handle - 1] = T(); // Destruct and replace with default object
_freeList.push_back( handle - 1 );
}
T &getRef( uint32 handle )
{
ASSERT( handle > 0 && handle <= _objects.size() );
return _objects[handle - 1];
}
Also, they’re using Horde3D 1.0.0 Beta 5 so maybe that might help someone else that’s looking into this as well. Not idea why this is happening yet but I’ll keep digging 
2 Likes
hey guys iv been getting the same error as everyone else and i fixed mine by going into the settings and turning off all of the graphics. It seems that you have to delete the game saves that had this error because they wont work no matter what you do, figured out this by some trial and error.
5 Likes
Holy crap you found a workaround! 
Now to figure out what the heck in the graphics settings is causing the Horde3D renderer to freak on loading
EDIT: Tested on all of my saves and they’re all loading in just fine after turning down/off all graphics settings. So it’s not a corrupted save issue. Something be broke in the renderer for sure!
3 Likes
Now that I have a workaround to test with I’ve narrowed the problem down considerably. It’s specifically to do with AA and shadows though I’m not sure what just yet. If either setting are turned on at all then it freaks out when trying to load a save game. Other graphics settings don’t cause the crash bug, just the AA and shadows on any setting other than “Off”.
So it would seem that for now you have to change your settings back to off on both options when you are done and close the game then once you’ve loaded up your save again the next time you play then turn the options back on while you play. Seems to be working fine when used in-game just can’t be turned on when first loading up the game. Also, you can’t load the game then turn them off to try to load. They must be turned off before the game starts.
EDIT: It has been pointed out that AA is in fact not the issue and I have confirmed that as well. Must have left shadows on or something while I was testing out each setting. Yay progress
8 Likes
HEY hey HEY, I can play and I’m twitching too, i was getting stonehearth withdraw.
Kudos to @sontaikles and @chessmaster42 for finding this work around so I could test it all Thanks Bud.
3 Likes
Confirmed that its working its a weird fix but its A fix
I can confirm this walk-around “fix”. I have been getting that same issue, and I did as @sontaikles and @chessmaster42 said- turning down both Anti-Aliasing and Shadows all the way off.
Well, we found a work-around, but something is definitely clashing with the shadows and AA graphics area. Radiant, we all have faith in you! You have yet to let us down, even if we had this slight scare. Keep it up! 
Assertion Failed bug. It seems to be related to a previous bug thread I submitted earlier (See Custom Building Error). I saved the game and tried to reload saved game when this error popped up. Screenshot below:
