Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-250338

Chunk loading is jumbled, apparently can result in a Crash.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 22w16a, 22w16b
    • None
    • Unconfirmed
    • (Unassigned)

      If you fly around in a 22w16a world, especially if teleporting, some chunks begin to get mixed up, resulting on "fake" sections of chunks appearing, like a chunk with parts of spruce trees in a Forest biome, these are visual bugs so the shape of the terrain is not affected, but it looks very confusing, like in Spectator mode if you were to try to go back into creative mode within a cave, you'd suddenly be inside Deepslate, since the cave isn't actually there.

      World updates seem to also affect it, having it cycle through different parts due to Sculk Sensor updates or Lava flowing, using /setblock and even spawning in a 22w16a world also causes this.

      I genuinely thought it was an issue with my hardware possibly running out of storage, but this issue didn't occur in 22w13a, and only began when I loaded the world again in 22w16a, I have a short clip of this bug which I wanted to add but it just goes over the space limit on this site, and during that clip the game crashed as I was showing the bug.

      I do have several screenshots which when together like a slideshow sort of visualize this bug in action as well as the crash log from the MC launcher possibly caused by this issue.

      22w16b does not fix this either, as one of the screenshots below of a Wooded Badlands is what I was greeted by when spawning in a new 22w16b world!

        1. 2022-04-20_18.34.46.png
          2022-04-20_18.34.46.png
          3.52 MB
        2. 2022-04-20_18.34.52.png
          2022-04-20_18.34.52.png
          3.81 MB
        3. 2022-04-20_18.35.19.png
          2022-04-20_18.35.19.png
          3.50 MB
        4. 2022-04-20_18.37.57.png
          2022-04-20_18.37.57.png
          1.64 MB
        5. 2022-04-20_18.37.59.png
          2022-04-20_18.37.59.png
          1.75 MB
        6. 2022-04-20_18.38.01.png
          2022-04-20_18.38.01.png
          1.57 MB
        7. 2022-04-20_18.38.03.png
          2022-04-20_18.38.03.png
          1.57 MB
        8. 2022-04-20_18.38.18.png
          2022-04-20_18.38.18.png
          1.37 MB
        9. 2022-04-20_18.38.23.png
          2022-04-20_18.38.23.png
          977 kB
        10. 2022-04-20_18.38.25.png
          2022-04-20_18.38.25.png
          538 kB
        11. 2022-04-20_18.38.41.png
          2022-04-20_18.38.41.png
          927 kB
        12. 2022-04-20_18.38.44.png
          2022-04-20_18.38.44.png
          858 kB
        13. 2022-04-20_18.55.31.png
          2022-04-20_18.55.31.png
          3.08 MB
        14. 2022-04-20_18.55.34.png
          2022-04-20_18.55.34.png
          3.30 MB
        15. 2022-04-20_18.59.05.png
          2022-04-20_18.59.05.png
          3.53 MB
        16. hs_err_pid6652.log
          76 kB

            Unassigned Unassigned
            kae_verens Jareth The Rad
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: