Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-53895

Chunks not loading correctly (offline and online)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • None
    • 1.12.1
    • Creative
    • Unconfirmed
    • Windows

       

      Since a couple of days I've had issues with chunks being broken/invisible more than usual on my offline creative map (literally every few minutes, always after a teleport).

      A quick teleport -1000 and 1000 back will trigger loading the chunks, but it is quite cumbersome.

      I have seen this behavior on our REALM, but never offline.

      Things I've tried:

      • reinstalled graphic drivers
      • uninstalled and reinstalled minecraft (MCPE Win10)
      • with or without texture packs
      • I tried using previously published (and working, played by hundreds) versions of this map and there the problem also miraculously appeared.
      • I also tried on a seperate computer (laptop), which gave the exact same result, leading me to believe this is an issue with the current iteration of Minecraft itself
      • I tried looking for logfiles, but it looks like there are non for this version?

       EDIT:

      I tried using longer render distance (48, 64 and 80) and at higher settings the "some chunks not loading" error went away. Probably because you are now teleporting between 2 points within render distance of eachother. 

      So for now it looks the bug appear when teleporting outside of render distance.

       

      EDIT2: I have tested and tested and tested on 2 different computers and I believe there is a bug with render distance. It looks as if the renderer stops to draw too quickly when the drawing distance is set to 16, 32 or 48....

      If I teleport between 2 seperate far apart destination with render distance 60 or higher, I never get failed chunks, but on 16 and 32 it happens almost instantly. I also have a powerful PC with 8700K and 1080 GTX.

       

      EDIT3: well, it appears the bug was fixed with the release of 1.3.0 - I will keep an eye open incase anyone every sees this bug report

            belkov78 Marco Bergsma
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: