Lots of freezing with removing and placing blocks
I get a good 5 - 10 second freeze every time I Use a shovel to pick up anything.
any more information ? like where the server is in the world and where you are ? / ping ? is this happening on every server you visit ?
It seems to be fine when I am in windowed mode.
could you provide me with some OS and hardware specs? dxDiag file preferred
I had this same issue, to fix it I usually just disconnected and reconnected. I play on the main server that ranges in ping from 190- the highest I've seen it at around 400. Just speculation (I know nothing of computers) but could this be linked to the memory leak?
This same thing happens over time on my own server that I'm running on the same pc. I do like Nomad suggested, picks right back up.
Yeah it does seem like there is a memory leak or something in the game atm where after 30-60 minutes you just gotta relog and it all seems to iron outlast edited by
In darkness there is light and in light there is darkness.
possible fixet in 4.2 but needs testing .. also if its still in 4.2 please check also your memory issue ( no release date for 4.2 yet !) https://github.com/StrangeLoopGames/EcoIssues/issues/392
this problem still exists in 4.2
OS:Win 10 64bit Build 14393
Server: Everland Gaming
CPU: i7 4790k
GPU: EVGA GTX 970 ACX 2.0 4GB DDR5
RAM usage at the begin: 2GB
CPU usage at the begin: 30%
RAM usage while freezes: 2.5GB - 2.7GB
CPU usage while freezes: 31.1% - 35%
will upload dxdiag and memory usage asap
Got new max RAM usage with 3.61GB while CPU runs with 31%.
This should be fixed in alpha 5.
Can't wait for this to be fixed. Lag when picking up a block or also not being able to pull a cart if you walked to far from it. Both can be fixed by relogging
I can confirm that reconnecting to the server alleviates the issue.
I can also confirm that the longer you wait to reconnect, the worse it gets (I was waiting around 20s to move dirt at one stage thinking "It's alpha, they're still very early in the dev process!", but as it turns out, it was a memory leak that I didn't know about.