MC-261495Loaded chunks sometimes don't render for a while
Sometimes when I fly with elytra in the new 1.20 snapshots, (This seems worse in 23w13a than 23w12a as well.) the chunks will be loaded and stuff there but they are completely invisible for a really long time before they render. You can tell the chunks are loaded because you can interact with the chunks like walk around and stuff
Additionally, if you go into one of the invisible chunks, sometimes it will make all of the other chunks that were previously visible go invisible.
Linked Issues
Normal
Created Issue:
Loaded chunks somethimes don't render for a while
Sometimes when I fly with elytra in the new 1.20 snapshots, the chunks will be loaded and stuff there but they are completely invisible for a really long time before they render.
Sometimes when I fly with elytra in the new 1.20 snapshots, the chunks will be loaded and stuff there but they are completely invisible for a really long time before they render. You can tell the chunks are loaded because you can interact with the chunks like walk around and stuff
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
Loaded chunks somethimes don't render for a while
Sometimes when I fly with elytra in the new 1.20 snapshots, (This seems worse in 23w13a than 23w12a as well.) the chunks will be loaded and stuff there but they are completely invisible for a really long time before they render. You can tell the chunks are loaded because you can interact with the chunks like walk around and stuff
Sometimes when I fly with elytra in the new 1.20 snapshots, (This seems worse in 23w13a than 23w12a as well.) the chunks will be loaded and stuff there but they are completely invisible for a really long time before they render. You can tell the chunks are loaded because you can interact with the chunks like walk around and stuff
Additionally, if you go into one of the invisible chunks, sometimes it will make all of the other chunks that were previously visible go invisible.
![[Mojang] Moesh](../../../data/avatars/users/10122.svg){kind=small}
relates to
Important![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
is duplicated by
![[Mojang] Rebecca](../../../data/avatars/users/18936.svg){kind=small}
Sometimes north-south chunk borders are visible in water.
Has anything with rendering changed since the 1.20 snapshots?
Also I want to make note of the fact that it doesn't happen all of the time, it's only like maybe once or twice a day when I'm playing Minecraft for probably 8 hours a day (and it doesn't last long either, usually only a minute or so and it eventually fixes itself; I don't have to reload or F3+A or anything like that)
Also, I noticed that this seems to be tied to MC-261495. Like once the chunks render, this usually happens. It's like the game doesn't realise those chunks are adjacent or something. Sometimes it happens without MC-261495, but they seem to be related somehow. I have also only experienced this while travelling east or west, so that supports my theory.
Thank you for your report!
We're tracking this issue in MC-261495, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Do you also experience this in 1.19.4?
This is also an issue in 1.19.4. I think this might be a case of, or at the very least related to, MC-238823.
For me this doesn't seem to happen in 1.19.4, it's all 1.20, and I have to press F3+A to reload constantly when I'm flying with an elytra
Yeah I did not have this issue prior to the 1.20 snapshots.
Can confirm in 1.21.1.
Seems happened since 1.16 or earlier.
Are you still able to reproduce this issue on the latest version?