Brian Tate

We can close this I suppose. Not sure how it occurred to begin with however I was able to restore an older backup from 18w48b upgrade it to a snapshot I never tested 19w08b (if I recall). Due to the amount of loot in this location, I decided it was best to move it all underwater on transparent blocks. I then validated everything worked and performed the upgrade to 19w11b. Everything seems to be in order.

Sorry about that. Hello Neko, it's like the whole world became a different landscape. The last image was when I first noticed it on 19w08 but it was my child's birthday so I let it be. I then tested it again today and found the same result in 19w10b. The first image is what I expected for the most part from the save point where I left off in 18w50. When I migrated to these snapshots, proceeded across the desert and savannah to the 425 71 48 image. If this was 18w50, I'd be standing above the ground. As one can see, everything has been uprooted.

It is. I just opened the same world that has been played in 1.13.2, due to a large amount of progress. I went back to that area and it appears they are still there, perhaps less but still many columns.

See attached.

After additional investigation, this was actually the result of an oak tree near a jungle tree. Not sure why those spawned besides each other and where is the option to close a bug from my end?

https://drive.google.com/file/d/1dcdKdXFLjv9l4myye9bmN8w-m1AqVlvA/view?usp=sharing

This backup should be of 1.12.2 and the same seed

Today checked with latest release 1.13.2 and this issue still persists - with upgrade from 1.12.2 world. This is the same world shown above.

In the images above, the water in this seed is shown. There is also an image of the same view but up higher and at night. Lastly, the other images confirm that it was present even when moving to a fresh release of 1.13.1 and it appears this will also occur with 1.13.2 - I will see if there is a means to get closer telemetry as this is a survival world with no cheats.

Indeed, I actually backdated the backup from the upgrade and the previous file was 1.12.2 - I just upgraded from this same file to 1.13.1 and went to the same area. The issue persists but what are these and where's the corals and seaweed?

Seed is 4630973706159243126 at 618 62 -329

After additional observations, this has some relation to MC-129409. I did also include a screen capture of two blocks that are shown in which I am standing in and can breathe. (Note, somewhat enjoyable however as even with the turtle helmet, one must wait a really long time to be able to fully use most of this update in survival without cheats due to depths).

Seed is 4478000288646156387

/tp 186 63 143

Additional note. I did not observe this behavior in past snapshots to my knowledge. This included 18w10b,c,d, 11a, 14a, 15a and 16a. It was all reset in 19b so I cannot comment on the previous snapshot release.

Hi Team,

I have had this occur now twice, in two different worlds both in survival mode. One I created and have played many snapshots on and the other was a demo world I created long ago that I decided to start playing when the other became corrupted. Due to this specific bug along with performance issues with this release, I will likely choose to wait until GA as this is simply unacceptable that this is still open in JIRA and hasn't moved at all. I'm including two log files from each instance for static testing. Each are on the same test host with no changes from baseline. While not exactly a bug, I may need to file one as performance on macOS 10.12.6 has really been impacted with the additions added in this update. In fact, I had to totally disable any 32 or 64 resource pack and even the low end shaders as well. What is strange is that the FPS in vanilla was still the same but performance seems to be related to large chunks that appear to be attempting to render but do not. This is on macOS 10.12.6, (any beta snapshot so far, including 18w11a), Core i7 2.3Ghz, 16GB DDR3, Intel HD4000. Frankly, my Lenovo Ultrabook does not far much better with Windows 10 1701.

This bug is really difficult to address if anyone expects some serious bug testing from crowdsourcing QA. We have to be able to play the snapshots to report the bugs. We cannot do that at the moment once this is encountered. On a final note, I was at MineCon Earth with my son at Microsoft and I find it disconcerting that these issues still persist and GA should be already a confirmed date. Please address these performance issues and review the logs to address this bizarre bug. Thank you.