Low/incorrect chunk load distance on far view setting
Edit: The bug report at https://mojang.atlassian.net/browse/MC-31622 is clearer, and almost certainly the same issue.
In single player, the chunk loading distance appears to be lower than intended. As far as I can tell, they load to the default server distance of 10. This causes the edge of the world to be quite visible, before the fog starts affecting it.
This has been an issue since the LAN update.
Created Issue:
Low chunk load distance on far view setting
In single player, the chunk loading distance appears to be lower than intended. As far as I can tell, they load to the default server distance of 10. This causes the edge of the world to be quite visible, before the fog starts affecting it.
This has been an issue since the LAN update.
(Please do not "fix" this issue by reducing the fog distance! Chunk loading distance needs to be tied to the view distance setting!)
In single player, the chunk loading distance appears to be lower than intended. As far as I can tell, they load to the default server distance of 10. This causes the edge of the world to be quite visible, before the fog starts affecting it.
Edit: The view distance is not properly changing the chunk loading distance, as it did before, and as a result of SP games working as listen servers.
This has been an issue since the LAN update.
(Please do not "fix" this issue by reducing the fog distance! Chunk loading distance needs to be tied to the view distance setting!)
Low/incorrect chunk load distance on far view setting
In single player, the chunk loading distance appears to be lower than intended. As far as I can tell, they load to the default server distance of 10. This causes the edge of the world to be quite visible, before the fog starts affecting it.
Edit: The view distance is not properly changing the chunk loading distance, as it did before, and as a result of SP games working as listen servers.
This has been an issue since the LAN update.
(Please do not "fix" this issue by reducing the fog distance! Chunk loading distance needs to be tied to the view distance setting!)In single player, the chunk loading distance appears to be lower than intended. As far as I can tell, they load to the default server distance of 10. This causes the edge of the world to be quite visible, before the fog starts affecting it.
This has been an issue since the LAN update.
Edit: The view distance is not properly changing the chunk loading distance, as it did before, and as a result of SP games working as listen servers.
In single player, the chunk loading distance appears to be lower than intended. As far as I can tell, they load to the default server distance of 10. This causes the edge of the world to be quite visible, before the fog starts affecting it.
This has been an issue since the LAN update.
Edit:
The view distance is not properly changing the chunk loading distance, as it did before, and as a result of SP games working as listen servers.In single player, the chunk loading distance appears to be lower than intended. As far as I can tell, they load to the default server distance of 10. This causes the edge of the world to be quite visible, before the fog starts affecting it.
This has been an issue since the LAN update.
Edit: I believe the view distance is not properly changing the chunk loading distance, as it did before, and as a result of SP games working as listen servers.
is duplicated by
is duplicated by
relates to
In single player, the chunk loading distance appears to be lower than intended. As far as I can tell, they load to the default server distance of 10. This causes the edge of the world to be quite visible, before the fog starts affecting it.
This has been an issue since the LAN update.
Edit: I believe the view distance is not properly changing the chunk loading distance, as it did before, and as a result of SP games working as listen servers.
In single player, the chunk loading distance appears to be lower than intended. As far as I can tell, they load to the default server distance of 10. This causes the edge of the world to be quite visible, before the fog starts affecting it.
This has been an issue since the LAN update.
Edit: I'm closing this, because the bug report
In single player, the chunk loading distance appears to be lower than intended. As far as I can tell, they load to the default server distance of 10. This causes the edge of the world to be quite visible, before the fog starts affecting it.
This has been an issue since the LAN update.
Edit: I'm closing this, because the bug report
In single player, the chunk loading distance appears to be lower than intended. As far as I can tell, they load to the default server distance of 10. This causes the edge of the world to be quite visible, before the fog starts affecting it.
This has been an issue since the LAN update.
Edit: I'm closing this, because the bug report at https://mojang.atlassian.net/browse/MC-31622 is clearer, and almost certainly the same issue.
In single player, the chunk loading distance appears to be lower than intended. As far as I can tell, they load to the default server distance of 10. This causes the edge of the world to be quite visible, before the fog starts affecting it.
This has been an issue since the LAN update.
Edit: I'm closing this, because the bug report at
https://mojang.atlassian.net/browse/MC-31622 is clearer, and almost certainly the same issue.Edit: The bug report at https://mojang.atlassian.net/browse/MC-31622 is clearer, and almost certainly the same issue.
In single player, the chunk loading distance appears to be lower than intended. As far as I can tell, they load to the default server distance of 10. This causes the edge of the world to be quite visible, before the fog starts affecting it.
This has been an issue since the LAN update.
duplicates
Duplicate of MC-5227, please use the search function to see if your bug has already been submitted. Currently over 58% of tickets are being resolved as duplicate.
Duplicate of MC-5227, please use the search function to see if your bug has already been submitted. Currently over 57% of tickets are being resolved as duplicate.
This is getting ridiculous. Up to 1.2.5 "far" distance worked quite well, with the world almost extending into the fog. Ever since, the integrated server in the client has been stuck at 10 chunks (MC-5227). At least a dedicated server with view-distance=15 is very close if not identical to 1.2.5 (identical in my test). Now the snapshots leading up to 1.7 won't ever do more than 8?
Please just fix this once and for all.
MC-5227 is still there in its original form. That is, the integrated server still uses 10 chunks no matter what. The dedicated server can't be configured to use more than 15 chunks (not enough to disappear in "far" or 16-chunk fog). There is no functional communication of the render distance, and the result of the broken attempt is never used anywhere.
MC-31622 (this one) is that the game will never load anything over 8 chunks or so away. Like the other bug, it appears to be primarily a server-side problem, because chunks will only unload after leaving the server's range. You can check this by walking or flying a few hundred blocks and looking behind you. Once the game has finished updating all chunks, those that were already loaded and are within the server's view-distance will still be there. Interestingly, the area that will load before you move is also mildly affected: view-distance=10 is really 7 (15x15=225 chunks); view-distance=15 is really 9 (19x19=361 chunks, or usually a few more like 363 or 366 in my tests).
The client uses a default render distance of 12 chunks instead of 8 if it's 64-bit. That's all the differentiation you'll find.
The issue [Mod] CubeTheThird is referring to is MC-5227. The lag you're experiencing is probably caused by that issue (which prevented view distances over 9 from working) being fixed.


This is a feature suggestion, not a bug. Please resolve.
This is not a feature suggestion. The view distance is not properly changing the chunk loading distance, as it did before, and as a result of SP games working as listen servers.
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.
Updated, the issue is still present in 1.5.
Still present in 1.5.1 and 13w16a.
Reproduced in 1.6.2
I'm surprised so few people have noticed this. But then I didn't report it for the longest time, either.
It seems the server tries to take into account the render distance, but misinterprets the value. The client sends far=0, normal=1, short=2, tiny=3. The server calculates distance=256>>value, which becomes far=256, normal=128, short=64, tiny=32. So far, so good. But at that point it interprets it as a number of chunks, only applying it if it's in the range (3, 15), i.e. never. So the server always uses 10 chunks, or whatever is in its configuration file. It's odd that there's a setting at all when it should really be irrelevant, had the extant code to use the client's value worked properly. What did Mojang really want to do?
You can work around it by running a dedicated server with view-distance=15. You can still easily see the edges, but at least there are more chunks. The integrated server can't be persuaded without modding it.
This is still an issue in 13w38c, even with the new "render distance" slider. Any option beyond 10 chunks remains at 10.
I can confirm that this is still an issue in 1.6.4
It is here for new version
MC-31622Thank you @Dranitsin
MC-31622has been linked as related due to chunk render distance changes in recent snapshots... technically no "Far" render distance anymore, just a count now.I can confirm in 13w41b.
This is still a problem in 1.7.4.