[MC-5227] Low/incorrect chunk load distance on far view setting Created: 22/Dec/12 Updated: 03/Jun/17 Resolved: 05/Dec/13 |
|
| Status: | Resolved |
| Project: | Minecraft: Java Edition |
| Component/s: | None |
| Affects Version/s: | Minecraft 1.4.6, Minecraft 1.5.1, Snapshot 13w16a, Minecraft 1.5.2, Minecraft 1.6.1, Minecraft 1.6.2, Minecraft 13w38c |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Sturmkrahe | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 7 |
| Labels: | None | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| CHK: | |||||||||||||||||
| Confirmation Status: | Community Consensus | ||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Zachary Joseph Sommer [ 22/Feb/14 ] |
|
This is still a problem in 1.7.4. |
| Comment by Marios [ 14/Oct/13 ] |
|
I can confirm in 13w41b. |
| Comment by Talven81 [ 23/Sep/13 ] |
|
Thank you @Dranitsin |
| Comment by Dranitsin Roman [ 23/Sep/13 ] |
|
It is here for new version |
| Comment by Gareth Hills [ 21/Sep/13 ] |
|
I can confirm that this is still an issue in 1.6.4 |
| Comment by Sturmkrahe [ 21/Sep/13 ] |
|
This is still an issue in 13w38c, even with the new "render distance" slider. Any option beyond 10 chunks remains at 10. |
| Comment by jonathan2520 [ 15/Aug/13 ] |
|
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. |
| Comment by crazyman [ 26/Jul/13 ] |
|
Reproduced in 1.6.2 |
| Comment by Sturmkrahe [ 20/Apr/13 ] |
|
Still present in 1.5.1 and 13w16a. |
| Comment by Sturmkrahe [ 17/Mar/13 ] |
|
Updated, the issue is still present in 1.5. |
| Comment by Tails [ 17/Mar/13 ] |
|
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. |
| Comment by Sturmkrahe [ 22/Dec/12 ] |
|
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. |
| Comment by Anon Ymus [ 22/Dec/12 ] |
|
This is a feature suggestion, not a bug. Please resolve. |