Huge performance drop when digging in water

I currently have a couple hearthlings that are digging out some tiles to connect a lake to my moat. As soon as they started digging these tiles out, the game began lagging terribly. During this period, the debug bar was showing that most time was being spent in LUA.

Steps to reproduce:

  1. Dig an area out near a lake
  2. Dig out the blocks between the lake and the area dug out in #1

It hasn’t really effected the digging or the performance so I am unsure what the cause is.

Bumping this, here’s my save http://puu.sh/j7qkx/40f1e0de2a.7z digging this tunnel out
http://puu.sh/j7qtr/76841cf433.jpg
is causing a huge delay in the hearthlings thought process, not actual lag so to speak aside from a little stutter every now and then. when this tunnel finishes the delay stops and performance improves.

2 Likes

I know this is this still in Alpha testing, and I have switched to and fro from Alpha 10.5 to 11 and back again, which I’ve not had any problems with, the game does limit my use of files from one to the other, and that’s all peachy king.

The new problem and I’m sure I’m not the only one with this, is that the Lua code overload and it forces me to close the game via outside and unable to save. I’m only digging three blocks deep in the lake and wham, 14 engine errors come up, so I close it. Suddenly another Engine fails and it’s a rapid count of errors and it continued… I think I had to force shut off at 200 before it really got bad. Aside from having to force shut down, it somehow jumped from one memory bog into Steam’s. I’ve had this on the lowest possible settings and I had to save faster than usual before my little peeps could get out of the water via ladder (And that stupid fox is still in there, refusing to get out unless it gets hungry.) I have a file of the problem, but it’s pretty lengthy. I’m not sure where the error is, since I cannot read code, but if someone else wants to have a look and make the dev’s eyes hurt a lot less, I’m more than willing to give it to you. That aside, is there a way to fix this?

hey there @Omikaru welcome to the discourse :smile:

i just merged your topic with this one, as they seem to be the same thing.

Summary
Yep had the same thing. when they were digging into the water and got to a deeper layer, huge performance drop; when they were done, the performance drop did go away. Also had an error popping up which won’t go away with F5, close permanently doesn’t work either.

Step to produce
Can’t reproduce it anymore while mining in the water; but just incase report this error

workaround
Reload savegame when Close permanently doesn’t work

Expected Result
Just digging a few layers with succes

Actual Result

Error1
release-489 (x64)
@stonehearth/components/water/water_component.luac:81: error growing water region. bad top layer: (45 cubes of area 34866), good top layer: (42 cubes of area 35157)
stack traceback:
radiant/modules/common.luac:46: in function ‘report_traceback’
radiant/modules/common.luac:125: in function ‘verify’
stonehearth/components/water/water_component.luac:81: in function ‘_grow_region’
stonehearth/components/water/water_component.luac:54: in function ‘_add_water’
…rth/services/server/hydrology/hydrology_service.luac:184: in function ‘add_water’
…rth/services/server/hydrology/hydrology_service.luac:262: in function ‘_process_water_queue’
…rth/services/server/hydrology/hydrology_service.luac:260: in function ‘_on_tick’
…rth/services/server/hydrology/hydrology_service.luac:14: in function ‘_fn’
radiant/controllers/timer_controller.luac:33: in function ‘fire’
radiant/controllers/time_tracker_controller.luac:9: in function <radiant/controllers/time_tracker_controller.luac:9>
[C]: in function ‘xpcall’
radiant/controllers/time_tracker_controller.luac:9: in function ‘set_now’
…earth/services/server/calendar/calendar_service.luac:133: in function ‘fn’
radiant/modules/events.luac:97: in function <radiant/modules/events.luac:96>
[C]: in function ‘xpcall’
radiant/modules/events.luac:96: in function ‘trigger’
radiant/modules/events.luac:121: in function ‘_trigger_gameloop’
radiant/modules/events.luac:150: in function ‘_update’
radiant/server.luac:19: in function <radiant/server.luac:17>

Error2
release-489 (x64)
…rth/services/server/hydrology/hydrology_service.luac:230: assertion failed!
stack traceback:
radiant/modules/common.luac:46: in function <radiant/modules/common.luac:46>
[C]: in function ‘assert’
…rth/services/server/hydrology/hydrology_service.luac:230: in function ‘merge_water_bodies’
…rth/services/server/hydrology/hydrology_service.luac:263: in function ‘_process_water_queue’
…rth/services/server/hydrology/hydrology_service.luac:260: in function ‘_on_tick’
…rth/services/server/hydrology/hydrology_service.luac:14: in function ‘_fn’
radiant/controllers/timer_controller.luac:33: in function ‘fire’
radiant/controllers/time_tracker_controller.luac:9: in function <radiant/controllers/time_tracker_controller.luac:9>
[C]: in function ‘xpcall’
radiant/controllers/time_tracker_controller.luac:9: in function ‘set_now’
…earth/services/server/calendar/calendar_service.luac:133: in function ‘fn’
radiant/modules/events.luac:97: in function <radiant/modules/events.luac:96>
[C]: in function ‘xpcall’
radiant/modules/events.luac:96: in function ‘trigger’
radiant/modules/events.luac:121: in function ‘_trigger_gameloop’
radiant/modules/events.luac:150: in function ‘_update’
radiant/server.luac:19: in function <radiant/server.luac:17>

Attachment

Notes
Dessert, playing with Rayya’s
You will notice a few water blocks gone on the picture