On my dual core laptop, many aspects of the game that are multi-threaded
froze and malfunctioned when I raised my graphical settings, my game was still rendering frames despite the issues.
When I boosted my render distance from 8 chunks to 32 chunks, I expected very short term framerate drop.
But, instead the mobs froze, physics failed, the chunk loading slowed down significantly, and textures were not loading on recently changed blocks.
1. Start single-player world
2. Spawn various mobs
3. Go to video settings
4. Boost render distance to max
5. Resume game
6. Notice how gravel and sand don't fall, mobs can't move(or move smoothly), TNT ignites but takes significant time to explode, chunks load significantly slower(or not at all), and newly placed blocks don't load their textures for a bit of time.
Watch screen recording: http://www.youtube.com/watch?v=gKRUAkBZX5A
Related issues
duplicates
Comments
galaxy_2alex
migrated
Yes this still does happen in 1.8.1 release
galaxy_2alex
migrated
No it does (my cpu is more powerful than the Intel Pentium D, you cant compare by the GHz they are different designs) here are public benchmark results from geekbench: http://browser.primatelabs.com/processor-benchmarks (if you click 32bit multicore, you will see the celeron 1007u 1.5GHz scored 1980 and the pentium 805 2.66 GHz scored 1092) As you can see here mine did a little bit better: http://browser.primatelabs.com/geekbench3/1568877 at 2093. Don't forget that the Pentium D is a 32 bit CPU and my Celeron 1007u is a 64 bit CPU . As you can see, MY CPU IS NOT TOO WEAK! at least comparing that to what you say the minimum requirements are: https://help.mojang.com/customer/portal/articles/325948-minecraft-system-requirements?b_id=5408
galaxy_2alex
Does it also happen in a completely new world?
migrated
yes, it does. It happens on all single player maps
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.