mojira.dev
MC-250331

Chunk rendering is glitchy / incorrect when redrawing

After switching between creative and spectator modes, I tp'ed to a mangrove swamp and noticed that some chunks were rendered weirdly.

I then placed blocks in surrounding chunks which made them render weirdly as well.

Here's the stream where I saw this happen: https://youtu.be/M6EHUQSn4eE?t=2870

Linked issues

MC-250338 Chunk loading is jumbled, apparently can result in a Crash. Resolved MC-250345 World Generation Glitch Resolved MC-250347 When i destroy a block on the the ground I can see through the entire world through the hole whenever I am in creative mode Resolved MC-250348 Minecraft chunks "fall apart" in 22w16a/b Resolved MC-250378 Whenever I mine a block somewhere (not sure exactly what causes it) - me and the shield swap places Resolved

Attachments

Comments 10

Video showing the effect and hopefully shows the chunk redraws and how it's using the cache.
https://youtu.be/2s79ejwjcGY
To clarify this was done in a 22w15a world that I upgraded to 22w16a

Can we give this bug report a better title, since its not related to teleporting

Teleporting into an ancient city shows this really well, with all the chunk updates from the lava

Found this in 22w16b immediately on spawning in a new world, twice.

I am running minecraft 22w16b on my opensuse Leap 15.3 Linux box, or trying to. I have tried all the normal stuff, rebooting with nothing else running and rebooting and starting everything normally and the results are the same. I normally start a new world with each snapshot. It keeps life interesting though I do not have the hoards of accumulated stuff other have. Because of this when I saw the new 22w16b show up I created a new world which I named 22w16b. It started me off on the top of a tree. Great, I can get some wood first thing. As soon as I broke the first block strange things started to happen. Holes appeared to open up but I discovered that blocks had become transparent. I tried deleting the newly created world and recreating it but got the same symptoms with a variety of terrains. The desert terrain lasted the longest as I had to hike a while to find a tree on top of a mesa. As soon as I punched the tree, mayhem in the form of transparent blocks showed up again. 

I am running a Ryzen 5 1600+ with 32Gig of Ram and a soft raid 5 3 disk array for my home directory and a single drive for my boot drive. I tried second life and it worked ok with no glitches that I could see. I wanted to rule out video card issues. Everything except minecraft is working normally. 

I noticed the description listed Windows 10 so I thought I better let you know it is happening on Linux as well. 

I dropped a photo, photo_2022-04-20_19-55-49.jpg, in the bucket. It was taken in the desert terrain after I punched a tree.

Some block like bells, pistons and banners were acting very weird with their rendering

Experienced in both 22w1a and 22w16b. Game crashes whenever I /locate and /teleport to an ancient city, usually without a launcher crash message. If in spectator while teleporting, the launcher returns a crash message:

[media]

Advanced crash log here:

[media]

Hope this helps.

this error occurs to me when having the chunk builder set to "semi block" and "full blocking"

this happens with RX 580 and GTX 1660

I fixed this - change ur chunk builder to threaded, reload the game, and it will be fixed

Siravid Chit-Arkhah

gegy

Confirmed

Very Important

Rendering

22w16a, 22w16b

22w17a

Retrieved