Massive Visual Glitching with VBOs off and Chunk distance over a level the graphics card cannot handle (Caused by outdated AMD drivers)
Update to AMD Catalyst Omega (14.12) (Or later)
Both drivers can be downloaded here.
If you're receiving this crash after updating to the drivers listed above, then you're experiencing MC-297, and will have to downgrade to the old drivers. Follow the instructions there on how to do so.
There are multiple workarounds that can fix this issue.
You can do any of the following listed below. These might've fixed the issue for some, but not all, people who have this bug.
Recommended:
Turn VBOs ON (Options -> Video Settings -> Use VBOs: ON)
Turn down render distance to an acceptable setting (where it doesn't produce the glitching)
Not Recommended:
Adding -d64 to the JVM arguments for Minecraft
(Example: -d64 -Xmx4G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M)
Assigning more memory (One user has said that they still experience it at about 3.5 GB)
I am unsure of the exact reproduction, however I was exploring a new area of the current seed I am using (-1421103864573832176) and in the upper right corner unexpected chunks started appearing (Repeating).
I can provide my save game if you wish (~50 megs uncompressed).
What I do know:
Appeared in definitely new chunks; however not in all new chunks.
All appear to be at the same height
. Chunks appear to be all the exact same from outside;
Definitely not of existing chunks (they are Savanah, however there is no actual Savanah in my world generated yet).
If I am not 'in' the unusual chunks, it shows the correct biome, and it appears like it is simply generating polygons along a certain line of site (I can sail below and if my view angle is offset enough, the chunks disappear.
If I am 'in' the unusual chunks, things get weirder:
- I can only walk a handful of blocks
- Biomes reported in the logging are very small (in what is otherwise I single chunk may contain 2 or three biomes)
- The grass, sky, etc. in the weird chunk will reflect the biome stated in logging, not the actual biome, nor the biome that the weird chunk otherwise appears to be.
My suspicion is it is loading corrupted data. It also wouldn't surprise me if it had some connection to a recent issue I have been seeing where chunks completely fail to generate geometry (I can walk in them fine, however nothing is drawn to screen); or more recently fail to update quickly (e.g. I can mine a few blocks, but it may take a noticable fraction of a second, to several seconds before the change is visually updated).
2014-07-23, 08:35 AM
2024-04-23, 04:43 PM
2014-11-19, 10:28 PM
121
43