Andre Flory

Ok, I found that toggle off - but I don’t believe I made the change. I guess I’ll see if the next update reverts it back similar to the issue I’m having with Full screen toggle. (See MCPE-224865 )

What doesn’t animate: Yellow splash text. Background image doesn’t spin like it’s supposed to.

Looks like “Future versions” was already removed automatically. This is for 1.21.94 (shown on splash screen).

@Moesh - the title of this ticket is that the Deep dark is not being created in existing worlds. I don't see how this is resolved. See my comment above for my issue.

I updated my 1.18 world and had the problem with no deep dark biome in new unexplored chunks, but I did get ancient cities. I created a new 1.19 world and it has the same problem.

@Lunade Thank you. I had never done that before. I allocated 8GB since my system has 32GB of ram and sure enough the performance issue disappeared. I went back to the world with the massive warm ocean and everything ran smoothly. Java runtime was using 9GB ram and Minecraft showed usage of 2.7-6GB. It would go up to 6 then shift to 2.7 and then go back slowly up to 6gb again and continue this cycle.

I created two worlds and have very similar results where performance turns south to where the game starts pausing/freezing every half a second then gets to the point where the game just completely freezes solid. The best example is the origonal world I created. Seed:  7377209451618990386 Coords of the large warm ocean with coral where the worst performance happens: -28/81/121 (Just south of the spawn area).

See attached screenshots for seed and coords.

Performance is super bad in this world. I'll try creating a new one and seeing if I have similar results.

I was able to escape by switching to spectator and tping out of there as soon as the world loaded. Seems there is a performance issue with warm oceans - this one is massive. I'll update with seed and coords soon.

I tested this on two newly created worlds in 21w40a - I have screenshots of two pillager outposts with no pillagers spawning and no iron golums in cages.

This bug is not resolved in 21w40a

I tried again with the zombie villager being out of a minecart, no rails, with a workstation right next to the curing zombie villager - the villager lost it's trades (I hadn't traded with it yet but rolled the trades to find one I wanted. I think this was the way it worked in 1.17.

@Dhranios - Yes, tested this several times, I wasn't out of air and also as I stated in the ticket it looks like my player received damage but I didn't actually lose hearts.

Minecraft bedrock edition is in a sad state on Nintendo Switch. I can play my realm on PS4 with (a couple hours of play) no issues but on Switch, I have to close Minecraft and REBOOT my switch because Minecraft on switch has some sort of memory leak or major issue causing the wait/loading screen animation to come up and stop my play. I died in the Nether on a nether fortress because of this bug froze up my ability to use my weapons - I tried blocking myself in but a little magma cube found me - I had to close the game and reopened and sure enough I was dead. Thankfully I had a respawn anchor near by. This wait/loading issue has been going on forever on the switch and needs resolved. This bug is realm independent as it's a core issue with the Minecraft bedrock software running on Nintendo Switch.

I tested this on Nintendo Switch 1.16 and I am able to toggle on crouch without issue. 

My enderman also agro then lose interest and start teleporting away from me. It makes it hard to get ender perls early in game.