MC-35363New Chunk Generation unaffected by Render Dist. Setting
Setting the render distance to a high value (16 chunks for example) will not force new chunk generation. If you move towards the empty chunks, they will then generate, and thus render.
I find this a little hard to describe correctly. Please see the screenshot I attached.
The screenshot was taken at a view distance of 16 chunks. I allowed the chunks to load before shooting as well.
I apologize to the moderators if this is an intended feature, duplicate, etc.
(I did search.)
Environment
Ubuntu 13.04, Latest OpenJDK
Linked Issues
Attachments1
Created Issue:
New Chunk Generation unaffected by Render Dist.
Setting the render distance to a high value (16 chunks for example) will not force new chunk generation. If you move towards the empty chunks, they will then generate, and thus render.
I find this a little hard to describe correctly. Please see the screenshot I attached.
The screenshot was taken at a view distance of 16 chunks. I allowed the chunks to load before shooting as well.I apologize to the moderators if this is an intended feature, duplicate, etc.
(I did search.)Environment
Ubuntu 13.04, Latest OpenJDK
Attachments1
New Chunk Generation unaffected by Render Dist. Setting
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
duplicates
That is inteneded. The View distance isn't just how many chunks you see, it tells the generator, how many chunks to generate at a given time. When you move towards an emtpy chunk it should generate while one of your previously loaded chunks will unload.
What the reporter is saying, however, is that increasing the render distance should cause new chunks that were not visible before to generate without you having to move towards them.
Duplicate of
MC-31622- If you have not, please use the search function in the future, to see if your bug has already been submitted. If you could not find the original report, please comment with the keywords you searched for.