Jan Reimer
Assigned
Reported
Comments
I can confirm this bug, however, I made tests in multiple versions. This bug for me is present in all versions starting from 1.9.4 up to the latest snapshots even with standard worlds. 1.8.6 only seems to be affected at the beginning, when the world is created, but then it runs fine. I tested Java 8 Update 25 (the one that comes with the launcher) and also the Update 151, all the same result. I also tried assigning more or less RAM to Java, but that also didn't help. I also tried the Optifine mod, and even there the bug is present, but depending on what settings I use, I can kind of work around it.
Beside the block respawning lag, the game runs fine with high FPS (100+)
In Creative mode the blocks don't spawn back, but even there I get a lot of messages about lag:
[20:41:15] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2278ms behind, skipping 45 tick(s)
[20:41:46] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 14693ms behind, skipping 293 tick(s)
[20:41:56] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 6639ms behind, skipping 132 tick(s)
All I did was running around punching a few blocks.
I am using Windows 10 (build 15063). Could this bug be related to Win10, as the initial reporter also uses Win10 and also the reporter of the duplicate?
Here's my system specs:
CPU: Intel i7-6700k
GPU: NVidia GTX 1080
RAM: 32GB
There has been an improvement on the issue, but it's definitely not resolved: It now works well up to a render distance of 23, however, if I set it to 24 or higher, the issue will be present again.
Here are more detailed system specs:
CPU: Intel i7-6700k @4,4GHz
GPU: NVidia GeForce GTX 1080 (Driver 397.31)
RAM: 32GB DDR4 @3200
MainBoard: ASRock Z170 Gaming K4 (BIOS version 7.30)
Hard Drive: Samsung Evo 850
OS: Windows 10 64-Bit Version 10.0.17134.81
Since I noticed that the bug reporter and I both have a Samsung Evo, I tested it on another drive (older 1GB HDD by Seagate), however the issue is also present there.