I know, it's silly to think that V-Sync is in any way correlated with rendering, but it did work for me. Not only chunks stopped disappearing, disabling it also increased the render speed
I'm not sure what context you are referring to exactly, but this solution worked in all types of single-player worlds, multiplayer servers and Realms. All graphical settings are maxed out; 32 draw distance and 15x15 biome merging included
If you want to give it a try, here is a link to my world: Isteria 2019-05-02
It's already in 1.14, I've played with it for a bit, changing pressure plates and making water elevators, but still. Chunks not loading etc. As it's described. Vsync disabled everywhere, it doesn't matter.
Why I'm giving the link to you? I'm just curious, if it will work fine on your machine.
I haven't tried 1.14 yet but this looks similar to what I've seen happen in older versions (since 1.8) when moving too quickly and it seems to be at least in part due to the occlusion culling misbehaving (the way chunks will suddenly disappear and reappear), and something similar occurred in versions before 1.8 when "Advanced OpenGL" was enabled (MC-129; Optifine fixes this and this is one reason why I used it. You could also disable AOGL but game would have to render everything). I don't see how chunks would flash like that otherwise, while delayed rendering is likely because the game doesn't refresh chunks often enough (that is, it tries to render an unloaded chunk, resulting in nothing to render, then when the chunk does load it doesn't immediately update the renderer, as well as the culling map), and the 1.8+ culling in general seems too aggressive (chunks often stop rendering before they are fully out of view; see MC-63020).
Also, the reason why Vsync would make this issue worse is because the game only updates a certain number of chunks per frame, 1 by default, more if it has the time but that doesn't seem to occur with Vsync; the FPS limit also has an effect since the higher it is the more time the game will try to spend on rendering frames, not chunk updates, and vice-versa (there is an old bug report about this, marked as a duplicate of MC-129, which as mentioned above was the pre-1.8 version of the current issue).
Vsync is just not related enough that I had to try it.
And as a surprise to exactly no one, it doesn't work. At least for me.
I've run with my horse through not loaded chunks. Thanks to my highway system, I can just…run safely.
It seems like I'd have to wait for some future update.
I know, it's silly to think that V-Sync is in any way correlated with rendering, but it did work for me. Not only chunks stopped disappearing, disabling it also increased the render speed
What's the context of that world?
Maybe I'll give it another try.
Yep, this is what fixed it for me, Disable V-Sync make sure it is disabled in the Nvidia control panel and restart your game.
was a 1.13.2 world I started just before the 1.14 update and no mods and not much built just got resources ready for the update.
https://bugs.mojang.com/browse/MC-149178
I'm not sure what context you are referring to exactly, but this solution worked in all types of single-player worlds, multiplayer servers and Realms. All graphical settings are maxed out; 32 draw distance and 15x15 biome merging included
HI YES I AM AFRAID THAT MY WORLD IS HACKED BY HEROBRINE THERE ARE 2 MANY GLITCH IN THIS MINECRAFT WORLD FOR ME. I AM SCARED> WHAT DO I DO!?!?!?
OK, tested again, no luck.
If you want to give it a try, here is a link to my world: Isteria 2019-05-02
It's already in 1.14, I've played with it for a bit, changing pressure plates and making water elevators, but still. Chunks not loading etc. As it's described. Vsync disabled everywhere, it doesn't matter.
Why I'm giving the link to you? I'm just curious, if it will work fine on your machine.
I haven't tried 1.14 yet but this looks similar to what I've seen happen in older versions (since 1.8) when moving too quickly and it seems to be at least in part due to the occlusion culling misbehaving (the way chunks will suddenly disappear and reappear), and something similar occurred in versions before 1.8 when "Advanced OpenGL" was enabled (MC-129; Optifine fixes this and this is one reason why I used it. You could also disable AOGL but game would have to render everything). I don't see how chunks would flash like that otherwise, while delayed rendering is likely because the game doesn't refresh chunks often enough (that is, it tries to render an unloaded chunk, resulting in nothing to render, then when the chunk does load it doesn't immediately update the renderer, as well as the culling map), and the 1.8+ culling in general seems too aggressive (chunks often stop rendering before they are fully out of view; see MC-63020).
Also, the reason why Vsync would make this issue worse is because the game only updates a certain number of chunks per frame, 1 by default, more if it has the time but that doesn't seem to occur with Vsync; the FPS limit also has an effect since the higher it is the more time the game will try to spend on rendering frames, not chunk updates, and vice-versa (there is an old bug report about this, marked as a duplicate of MC-129, which as mentioned above was the pre-1.8 version of the current issue).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?