-
Bug
-
Resolution: Duplicate
-
None
-
Minecraft 1.11
-
None
-
OS: Windows 10 (ver 10.0, arch amd64)
Java: 1.8.0_25 (by Oracle Corporation)
Launcher: Minecraft Launcher 1.6.70 (bootstrap 100)
Minecraft: 1.7.10 (updated Wed Jun 01 06:45:48 CDT 2016)
-
Unconfirmed
I was switching from version 1.11 to version 1.7.10 and tried to load into the game normally (I was using the forge version earlier and found out that it was a problem in the game itself rather than the mods I put together)
Every time I try to load into a world, the game would crash (weird I never saw vanilla crash before and 1.7.10 is very stable) and after a while I found out that my rendering was set to 32 chunks (from my preset I set back around versions 1.8 and up) and the max version 1.7 would allow was 16, so I fixed the amount of chunk by just moving the bar and allowing the game to correct itself.
Steps to Reproduce:
1. Load a version that has a max rendering distance of 32 chunks (I would assume 1.8 and up but I used 1.11 in this problem)
2. Set your rendering distance to 32 chunks
3. Close down the game and load up Minecraft again in version 1.7.10 or below.
4. Attempt to join a world (online or singleplayer it doesn't matter)
The game would (or is supposed to) try to join a game with your preset rendering distance of 32 chunks thus causing the game to freeze or crash*
(I am very upset that such an easy fix caused me to overthink and spend several hours trying to fix it) anyways.. I'm glad to at least try to help the cause.
- duplicates
-
MC-38527 Crash after changing max view distance to 20 chunks in options.txt / Render distance too high in options.txt after downgrading
- Resolved