MC-64445Render distance above 10 causes render to mess up
When the render distance goes above 10 the chuncks do not render, one of the chucks replicates everywhere and then they all flicker really fast. With 9 chucks or less loaded it is fine but above 10 the same problem happens. Please see: http://youtu.be/EfpwRf9ktd8 to see the video.
Environment
Windows 8, java 64 bit, latest drivers
Linked Issues
Attachments1
Created Issue:
Render distance above 10 causes render to mess up
When the render distance goes above 10 the chuncks do not render, one of the chucks replicates everywhere and then they all flicker really fast. With 9 chucks or less loaded it is fine but above 10 the same problem happens. Please see: http://youtu.be/EfpwRf9ktd8 to see the video.
Environment
Windows 8, java 64 bit, latest drivers
Deleted Comment:
render distance set on 32
Added Attachments:
Added Linked Issues:
duplicates
Added Linked Issues:
duplicates
Removed Linked Issues:
duplicates
Interesting... see MC-64445. Duplicate?
Confirmed
When I set render distance to 32 the chunks get coruppted. See the picture.
The world is newly generated in 14w31a.
Did you guys have the changing texture thing turned on?
It seems to be if you open its in 1.7.2 with a render distance of say 10, you cannot exeed that in the snap shot.
I experience this only when going in the range 28-32 chunks. Note that switching the render distance with the world open seems to cause this issue no matter what the distance... it somehow loses a data structure about what chunks should have been rendered, and not even F3+A will fix it. Only saving the world and reopening it.
Similar problem, began when I switched from Fast to a Fancy graphics and increased render distance to 12 chunks from 8. I noticed flashing in the distance and could see the same images repeated across the entire chunks even as I flew into them in creative mode. Affects 14w32b
I can confirm. I have a decent processor on my newest computer. There is a huge diffrence when loading chuncks with render distance 9 and 10. In 1.7.2+ there is still a diffrence. But it is mutch smaller and still stable.
If you have OpenGL on it may cause it too (it slows down chunck loading a lot for me)
I can confirm:
The bug as I think it occurs: When ligging in Minecraft tries to load all chunks at least once. If the player moves too fast in one direction but the first chunk loading isn't completed yet MC simply doesn't load any more chunks until the load is finished. Minecraft should have to check every time the player goes out of a chunk if the center of the loading area is still somewhere near and if not - reposition the rendering center to keep the chunks around the player always loaded and can not fall out of the world.