When playing in singleplayer with a render distance of over 8 chunks, the game immediately starts to lag as if I were in a server with a terrible connection. After reading through the game log, I discovered that the game is taking too long to do what it needs to do with this render distance. The chunks load slowly, broken blocks re-appear then break again, only giving the item when it breaks after a few tries, mobs will "rubber band" from place to place, the sun will move and then snap back from time to time, and this all happens in singleplayer. The output log is shown below in "latest.log"
Linked issues
duplicates 1
Attachments
Comments 5
Duplicate of MC-131614.
Please use the search function next time.
Yes, I realize this was already shown... However nothing has been done to fix this issue. This has been a problem since version 1.8 of release. It has not been fixed since then. I have no idea if this has something to do with Windows 10 or something else. I have used the search function, I have found multiple complaints of the same issue all being "resolved" however this is not the case. I can add footage if you don't believe me. It is incredibly frustrating when a bug is reported and nothing is done to resolve the issue for real. Considering this has been a major issue since 1.8, it should be first priority. The bug continues to get worse as the updates continue and by 1.17 I will not be able to play the game at 2 chunks, lowest settings if this is not fixed. Not even on a high end Origin PC build will the Java edition be able to run if this trend continues. Yes it may be aggravating to see the same issue be posted time and time again, however neglect is NOT the answer. Not everyone has the most powerful PC in the world. Sorry if this has been a train wreck of a post...😞
can confirm this happens in 1.13 pre3 as well, i have 16 gig of ram and even if i force it to allocate more i get horrible block lag.
I have this problem, too. I don't understand how a local singleplayer game can lag, and how this has been reported numerous times and still isn't fixed after 3-4 years. Especially when this lag didn't exist in some old versions of Minecraft. Newer versions should be better, not worse.
Keep in mind, I have found multiple similar issues, if not exactly the same issues that have been "resolved" that is NOT the case. I think this may be an issue with compatibility with Windows 10. I use the 64 bit version of Java, so it uses all the ram that it can to play games. I can confirm that this does happen in singleplayer. This bug has been present since 1.8 release. PLEASE take this into consideration! I have not had this problem with any version below 1.7 so this has been an issue since 2014 or 2013. I may have to permanently change to using the Bedrock engine version if this does not get fixed within the next few updates. If the bug persists after 1.15, I will no longer be playing or supporting the Java Edition of the game. One final note, since the 1.8 update the bug has become more apparent and more noticeable, increasing in effectiveness as the updates continue.