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

Blocks Disappearing by Updating 1.7.10 to 1.8 or 1.9

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • None
    • Minecraft 1.9.2
    • None
    • Windows 7 (64bit) / Windows 10 (64bit) , actual Java-Version
    • Unconfirmed

      A Time ago to the release of Version 1.8 I updating my 1.7.4 (no use of snapshots before) and then many blocks and many sorts of blocks (dirt, sandstone, stone for example) disappeared during the update and leave only shadows (non interpretable blocks, I think) in the world.

      This only affects blocks set in a specific construction phase (minecraft version); blocks of the same sort, that set earlier oder later are not affected. So the half of a building is normal, but the other half is disappeared.

      The same error, I think, responsible for ensuring that stone blocks were replaced by andesite, so I think there is a ID-Problem.

      I have waited to see, if update my 1.7.4 backup directly to 1.9 can walk around the problem but it is still there.

      I need help to fix it, i have lost two entire cities with much buildings through this.

      Edit:
      -----------------------
      A little correcture. My latest Backup has the latest version of 1.7 (1.7.10, i think) so its a update from this version to 1.8 or 1.9

      I've made the screenshots with my Netbook (Win10) but the problem is the same what i have with my pc. Another addition: There are a lot of performance issues in regions where are blocks that have been corrupted by the update; on both systems. Only my PC can handle this better, because it has more power.

      I tried to make screenshots on which the buildings can be seen from different construction phases together, so that you may realize that there is no general error of chunks.

        1. crash-2016-04-06_16.45.46-client-pre-update.txt
          16 kB
        2. crash-2016-04-07_14.24.01-client-post-update.txt
          33 kB
        3. logfile.log
          21 kB
        4. post-update-1.png
          post-update-1.png
          202 kB
        5. post-update-10.png
          post-update-10.png
          418 kB
        6. post-update-11.png
          post-update-11.png
          433 kB
        7. post-update-12.png
          post-update-12.png
          204 kB
        8. post-update-13.png
          post-update-13.png
          289 kB
        9. post-update-2.png
          post-update-2.png
          320 kB
        10. post-update-3.png
          post-update-3.png
          225 kB
        11. post-update-4.png
          post-update-4.png
          306 kB
        12. post-update-5.png
          post-update-5.png
          279 kB
        13. post-update-6.png
          post-update-6.png
          374 kB
        14. post-update-7.png
          post-update-7.png
          432 kB
        15. post-update-8.png
          post-update-8.png
          313 kB
        16. post-update-9.png
          post-update-9.png
          342 kB
        17. pre-update-1.png
          pre-update-1.png
          236 kB
        18. pre-update-10.png
          pre-update-10.png
          449 kB
        19. pre-update-11.png
          pre-update-11.png
          458 kB
        20. pre-update-12.png
          pre-update-12.png
          250 kB
        21. pre-update-2.png
          pre-update-2.png
          251 kB
        22. pre-update-3.png
          pre-update-3.png
          279 kB
        23. pre-update-4.png
          pre-update-4.png
          148 kB
        24. pre-update-5.png
          pre-update-5.png
          319 kB
        25. pre-update-6.png
          pre-update-6.png
          331 kB
        26. pre-update-7.png
          pre-update-7.png
          396 kB
        27. pre-update-8.png
          pre-update-8.png
          389 kB
        28. pre-update-9.png
          pre-update-9.png
          375 kB

            Unassigned Unassigned
            KingPaddy Patrick K.
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: