Like bug MC-129 I have a chunk that does not display properly (See screenshot). See bug MC-129 comment 25701 why this is not a duplicate.
Attached are two screenshots I can reproduce both views repeatedly by moving one tile forwards/backwards. So the chunk appears/disappears depending on my position. (It may be necessary to keep the crosshair on the blocks right in front on the same ledge)
This is reproduceable on SMP even after quiting and reopening the world. I have a savegame if someone is interested
This is with advanced OpenGL On, turning that of also toggles the bug
Linked issues
is duplicated by 13
Attachments
Comments 18
The description that an entire chunk doesn't display is not completely accurate. The screenshots of this bug that look down at the ground and can see through to caves make it look as though an entire chunk isn't rendering. If you look at the screenshots I provided in MC-10846 you can see that sometimes it's just a portion of a chunk that disappears. The top of the tree goes away but the trunk and everything below the top that is all part of the same chunk are still drawn.
Perhaps the game further subdivides chunks? Possibly into 16x16x16 cubes?
Also, this bug is not dependant on moving your position. It's easiest to trigger moving back and forth but you can also trigger it by standing in a single location an moving your view.
Reloading chunks with F3 + a has no effect on the bug.
I suspect this bug is probably a failure in z-ordering and occlusion / culling of backfaces of an algorithm such as "Painter's Algorithm": https://en.wikipedia.org/wiki/Painter%27s_algorithm
This bug might just be an edge case in the algorithm where it incorrectly removes or incorrectly orders the drawing of regions because getting the z-ordering correct is difficult?
Added screenshot where tree top in back left has disappeared. The trunk of the tree is still visible implying that at least some of the chunk is still being rendered.
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.
Is this still a concern in the current Minecraft version 1.7.4 / Launcher version 1.3.8 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Yes I saw https://twitter.com/Dinnerbone/status/491953005776748544 this morning "We'll release a 'b' snapshot soon to fix the chunk-vanishing issue (and some crashes)". I will test and report back in a day or two.
This ticket got superseeded by MC-63020
Try holding F3 and pressing "a." That reloads your chunks. It works for me.