The bug
This bug happens in two different circumstances. Nonetheless, it appears to be the same bug, and I didn't want to duplicate my own bug. If you believe these are different issues, let me know and I can make a new one.
If you increase your FOV, the chunks that were previously out of your view do not come into view until you move your player's head slightly. (This is a very old issue which was once fixed but has returned (this part was in 1.16.5); I don't know the original ticket number.)
When the world first loads, chunks, usually 4 or more away, occasionally do not render until the player shifts their head slightly. (This is a new issue which did not happen previously, since one of the 1.17 snapshots.)
Steps to reproduce
Stand on a platform ~15 blocks up in the sky. (This is just so you can see the chunks better.)
Set your FOV to 30
Look around a bit
Crank your FOV all the way up, but don't move your mouse once your game is unpaused.
--> ❌ Notice that the chunks do not come into view properly.
Linked issues
is duplicated by 5
MC-221002
Client doesn't load every chunk sent to it by server
Resolved
MC-226726
Chunks Not Loading
Resolved
MC-227279
Chunks near the player unload randomly.
Resolved
MC-227830
Подзорная труба и F5
Resolved
MC-228449
when you put your fov to 30, unpause and then put it to quake pro, most of the chunks unload
Resolved
Attachments
Comments 9
Dupe of MC-220541
I don't get it. This is not a duplicate of MC-220541. This has nothing to do with the nausea effect. This is about moving your head and chunks popping into view when they weren't rendering before.
If this truly is a duplicate, then the information in this bug should be added to MC-220541, as the said bug only mentions nausea and says nothing about changing your FOV or when the world first loads.
Yes, the first part is closely related. The second part is not as closely related. I've posted on Reddit for this bug to be reopened, but I am considering splitting the bug into two reports by creating a new one only regarding the second part of the issue, as I am not sure whether they are the same or not. Being that this bug was resolved as a duplicate of MC-220541, I really doubt that the two different parts are the same bug, seeing as I've seen the first half of the bug in the game a long time, but the second one I have not noticed before.
Not the same issue as MC-220541.
Would definitely relate to MC-220541.
Felix Jones
Related to MC-220541.