6.4.5 creates regular "can't keep up" lag and blocks are hard to break.
lymem opened this issue ยท 11 comments
With buildcraft 6.4.5 on minecraft 1.7.10, forge-1.7.10-10.13.2.1277 on the server, my server: AMD FX(tm)-4100 Quad-Core Processor, with 10 out of 20GB allocated to minecraft. There are regular "can't keep up" events on the console, and you have to break a block 3-4 times before it actually is broken. This issue is not present in buildcraft 6.4.3
Builders? Fillers? Are you using any of these?
Also, never allocate more than 2-3GB to Minecraft or you're just asking for trouble and lower performance.
This is very weird. I didn't touch any quarry code. You'd need to provide a sampling, from either Opis, Player's Sampler or something else.
No builders or fillers in use, a number of quarries though.
My server is currently using just shy of 6gb for minecraft, which happens when you have a lot of chunkloaded areas.
For the past few versions, quarries have been very laggy if pressed up against a wall in a cave, the tps drops massively. I think this is the same issue
http://prntscr.com/6lqj94
If you would like some more info, as I've found out from logblocker, it seems to spam loads of block requests, roughly 70k in 5 seconds, and the quarry frame never ends up building, almost like it gets stuck.
Aaaaaaaah. So it is the builder code at fault... And it does get stuck... What size is the quarry?
Going off to sleep. Remember that grief prevention mods might cause the frame not to be built. Anyway, good night,
Area was completely unprotected, and the quarry was default size. This issue doesn't happen on the surface, just when it;s facing a wall, which can be mostly done in caves.
At a side note, the last good working version for the quarry was 6.3.4, this issue was not present. I don't about previous versions of 6.4, but I tried both 6.4.3 and 6.4.5, both of them have this issue.
I'll get something together for you, or working on it at least.. It will be tomorrow pst when I get time to put it together.