Can confirm that this happens on my Nintendo Switch. I either have to wait upwards of 30 seconds or restart my game to correctly load in my skin. Sometimes, it still refuses to do it.
This seems to happen regardless of how I dress my character.
I play on the Nintendo Switch and traveling through my Nether Portal into the Overworld created a new Overworld portal which dumped me out into the middle of the ocean.
I’m not sure if this is the same issue, but on my Switch, my boats and empty minecarts disappear after breaking and take a long time to show up.
I just had a boat (again) disappear after breaking it and after spending a minute swimming around and on land looking for it, I gave up and went inside my nearby house to unload some inventory. When I went back outside, I saw it floating on the water.
I have not observed this issue with any other broken blocks or thrown objects - just boats and empty minecarts.
Same. I play on the Switch and the loading time going in and out of the Nether was upwards of 30 seconds and while I was lucky to not have mobs, my exit into the Overworld:
Opened up a new portal
Dumped me into the ocean
And I took drowning damage while waiting for the loading screen to finish.
I was lucky to have Respiration 3 on my helmet because I likely would have died while drowning.
I’m on the Switch and I have had this issue even before the Nether update, but since the Nether update, the individual item icons and sometimes banners will not load… at all.
To see what the item is, I have to try it on which is a major pain.
This has completely disincentived me from buying anything.
This is an intermittent, but frequent, issue on the Switch as well.
I have a solid connection and Minecraft is on my device and not on a card and my device has plenty of space on it as well.
If it matters any, the issue also persists regardless of joycon use - attached or detached from Switch - and regardless of alternate control use - paired via Bluetooth.
Can confirm on Switch (no Realm), but also with a potential twist.
Got tridented by a drowned yesterday when I didn’t have full armor and thought I was poisoned (I wasn’t) because of how fast my hunger bar suddenly started depleting.
Believe it or not, I was losing half a drumstick and gaining half a heart at a rate of half a second-ish and I had to eat every half a drumstick otherwise I wouldn’t heal.
Eat, replenish drumstick, heal exactly as much of a drumstick I replenished, drumsticks decrease, have to repeat the cycle until full hearts.
I have never eaten so much or so fast in years.
This issue isn’t consistent. Not every mob damage taken triggers it.
You probably already tried this, but I’ll ask anyways:
Have you unpaired the controller, shut down your game, rebooted the device, re-paired the controller, and then restarted Minecraft?
I play on my Switch and after updating the game, I experienced really bad drift up, down, and side to side for no reason at all using a Bluetooth connected Nintendo-approved controller. My joystick seemed to work fine.
I was able to fix it by closing the game, unpairing and re-pairing, restarting my Switch, and re-opening the game.
My situation is the same as above - I'm on a Switch (an earlier model, dockable) and now that I've been playing this version for a bit as both a single player and in local multi-player (both the host / world owner and the joiner) these are my observations:
Note: The two Switches involved are of the same age, have rendering set at the recommended 12, are optimized for performance (no fancy things), and do not have experimental features. Minecraft is loaded on the Switch itself and there is plenty of room on both the Switch (and the SD card).
ridiculously slow chunk loading (stand around for 10 to 30 seconds and sometimes longer at the edge of a chunk, waiting for it to load)
visible framerate lag (the mobs are moving at super slow framerate and then suddenly "run" or swim eg nearby fish, drowned, creepers)
delayed block breaking (you mine and it looks like you did, but the block doesn't break... and suddenly you broke two blocks and not just one)
actions happening but not happening (same with delayed block breaking)
delayed mob actions (you visually smack a creeper away on time and it looks like you have plenty of distance... and then it blow ups, you kill an illager... and after it's already dead, it goes "ow!")
The biggest problem with this is that you pretty much can't do anything "dangerous" without an OVERabundance of caution which... defies the point of Normal or Easy Survival mode.
You have no idea if a mob is 10 blocks away from you (on the same chunk) or right in front of your face. You have no idea if the dark cave you're peeking into is actually THAT deep and dark or if you're having chunk loading issues. You carefully mine a block with an Efficiency pickaxe only to discover you accidentally mined out two and ooops you mined into a hole or there's lava waiting for you.
The game isn't completely unplayable IF you have full armor, Feather Falling, Respiration, and a good sword to counter all the Ooops moments from lag, but even for an experienced Minecraft player (since 1.3) like myself, it's still a major pain and all the chunk lag and general lag in general makes the "improvements" (almost) not worth it at all.
Performance on both single player and local multiplayer on Switches with plenty of device space, playing vanilla, with the game optimized, with no add-ons, and on a new world with almost nothing going on is (still) shot.
Lag is everywhere and in everything I / we do and saving and chunk loading takes forever and it renders - haha - the game almost unplayable at times.
I was looking at the previous related tickets as well that included both freezing AND really bad lag at the same time.
When I had previously experienced those same issues on the same console, it had been a related problem.
That said, how do you know the difference between a pure freeze (gameplay stops) and super slow loading (for example, chunks are stuck in loading and you don’t see any visible changes)?
For sure this last update triggered this issue and I play on vanilla.
A few days before then, I had seen a trader with his llamas and they were fine. A llama got left behind and its texture was fine.
I logged in after the update and the left-behind llama turned red and green and when a new trader spawned in, those llamas were red and green as well.
My survival world was created during the version right before this update. I have 1 Active Resource Packs and it's Global. Default Behavior Pack. Yes to bonus chest. No to friendly fire and No to immediate respawn. Everything else in that list is yes. No experimental anything at all.
For Bedrock, is there any way to program our Eyes of Ender to ONLY locate a stronghold WITH an End Portal and have all the other Strongholds be a fun thing to accidentally discover while exploring?
Given that this is a parity issue created by programming differences and choices made during said programming, I feel like the consequence of these choices should be a "fix" that's just for Bedrock.
After all these years, I still don't understand how Stronholds weren't prioritized to not be overwritten - realism or not.
I've played Minecraft since it's 1.3 days on Java and while I've always appreciated the beauty and improvements in realism, nothing - and I mean NOTHING - has frustrated me more as a Bedrock player than this Stronghold issue that, because of programming differences, is considered as "working as intended" when it's honestly not.
I don't give two hoots about my overgrown caves being randomly bisected by some random structure. I don't care if my villages spawn half on the flat Plain and half on a Mountain. I don't care if I suddenly get a teeny tiny desert next to nothing but Jungle.
And you know, I don't even care about the time I exited a Nether Portal and nearly drowned because my game decided to randomly pop me out over an Ocean through an Overworld Portal who knows how many blocks overhead and in midair.
But I care about this Stronghold issue and with all these new world generation changes, I care a WHOLE LOT.
I don't cheat. At all. No locate command. No chunkbase. No creative. No x-ray mods. No asking a friend to even confirm for me that I'm going in the right direction (aka Stronghold WITH Portal) that my Ender Pearl is suggesting.
Minecraft takes time to explore and discover and few things are more frustrating than to finally get to a Stronghold... And discover that there is no End Portal in sight.
It doesn't matter that there are more to find - what matters is the wasted time. You have to triangulate. You have to dig REALLY deep and who knows where you'll end up and how much of what supplies you'll need. The cost of wasted time is even more important given the expanded X and Y coordinates.
To get to the End - the literal "end" of the game, there is only ONE way - through an End Portal - and this is why I just can't fathom why Strongholds and their proper generation wasn't THE priority from the get-go.
That said, with all the new changes, I feel like it's time re-address this issue... Unless everyone on vanilla Bedrock prefers the possibility of blindly digging from +150 to -50 only to find a Stronghold with no End Portal.
This had been an occasional occurrence already, but after 1.19.20 dropped, it happens every single time and I have to reload the game again and again in hopes of triggering the issue to fix itself.
Bonus points for skin being unavailable during then too!
Sef
MCPE-156288
Can confirm that this happens on my Nintendo Switch. I either have to wait upwards of 30 seconds or restart my game to correctly load in my skin. Sometimes, it still refuses to do it.
This seems to happen regardless of how I dress my character.
This happens to me regardless if I’m online or not.
I play on the Nintendo Switch and traveling through my Nether Portal into the Overworld created a new Overworld portal which dumped me out into the middle of the ocean.
I’m not sure if this is the same issue, but on my Switch, my boats and empty minecarts disappear after breaking and take a long time to show up.
I just had a boat (again) disappear after breaking it and after spending a minute swimming around and on land looking for it, I gave up and went inside my nearby house to unload some inventory. When I went back outside, I saw it floating on the water.
I have not observed this issue with any other broken blocks or thrown objects - just boats and empty minecarts.
Can confirm this happens on the Switch.
Additionally, the player is sometimes stuck in a running position even though they aren’t moving at all.
Same. I play on the Switch and the loading time going in and out of the Nether was upwards of 30 seconds and while I was lucky to not have mobs, my exit into the Overworld:
I was lucky to have Respiration 3 on my helmet because I likely would have died while drowning.
Affects game on Switch, still.
My anvil inconsistently plays the “tink tink tink” sound and has broken without a sound as well.
Voted.
I’m on the Switch and I have had this issue even before the Nether update, but since the Nether update, the individual item icons and sometimes banners will not load… at all.
To see what the item is, I have to try it on which is a major pain.
This has completely disincentived me from buying anything.
This is still happening and I’m playing the latest version on a Switch.
I’ll bucket something - fish, axolotl, plain water, lava - and it will sometimes immediately empty itself again.
I feel like this may or may not be related to how difficult it has become (in my experience) to bucket something after recent updates.
I have experienced this bug on the Switch ever since 1.17 came out.
I will, for no apparent reason, suddenly freeze in place and it can take a few minutes to unfreeze.
Meanwhile, all around me, business continues as usual and mobs will continue to attack if you were in the middle of a fight.
I am seeing a potential correlation with auto-saving because the last few times it happened, I saw the auto-save icon.
I’m not the OP, but I can reproduce this on my Switch running the latest version.
This is an intermittent, but frequent, issue on the Switch as well.
I have a solid connection and Minecraft is on my device and not on a card and my device has plenty of space on it as well.
If it matters any, the issue also persists regardless of joycon use - attached or detached from Switch - and regardless of alternate control use - paired via Bluetooth.
Can confirm on Switch (no Realm), but also with a potential twist.
Got tridented by a drowned yesterday when I didn’t have full armor and thought I was poisoned (I wasn’t) because of how fast my hunger bar suddenly started depleting.
Believe it or not, I was losing half a drumstick and gaining half a heart at a rate of half a second-ish and I had to eat every half a drumstick otherwise I wouldn’t heal.
Eat, replenish drumstick, heal exactly as much of a drumstick I replenished, drumsticks decrease, have to repeat the cycle until full hearts.
I have never eaten so much or so fast in years.
This issue isn’t consistent. Not every mob damage taken triggers it.
Verified on Switch with trapdoors made from oak that supposedly has “holes” in it.
Covered the campfire, tried to collect, got stung. This was an issue in previous editions as well.
You probably already tried this, but I’ll ask anyways:
Have you unpaired the controller, shut down your game, rebooted the device, re-paired the controller, and then restarted Minecraft?
I play on my Switch and after updating the game, I experienced really bad drift up, down, and side to side for no reason at all using a Bluetooth connected Nintendo-approved controller. My joystick seemed to work fine.
I was able to fix it by closing the game, unpairing and re-pairing, restarting my Switch, and re-opening the game.
Confirmed that this definitely did NOT help my Switch, either, and I had previously confirmed this problem before this most recent update.
My situation is the same as above - I'm on a Switch (an earlier model, dockable) and now that I've been playing this version for a bit as both a single player and in local multi-player (both the host / world owner and the joiner) these are my observations:
Note: The two Switches involved are of the same age, have rendering set at the recommended 12, are optimized for performance (no fancy things), and do not have experimental features. Minecraft is loaded on the Switch itself and there is plenty of room on both the Switch (and the SD card).
The biggest problem with this is that you pretty much can't do anything "dangerous" without an OVERabundance of caution which... defies the point of Normal or Easy Survival mode.
You have no idea if a mob is 10 blocks away from you (on the same chunk) or right in front of your face. You have no idea if the dark cave you're peeking into is actually THAT deep and dark or if you're having chunk loading issues. You carefully mine a block with an Efficiency pickaxe only to discover you accidentally mined out two and ooops you mined into a hole or there's lava waiting for you.
The game isn't completely unplayable IF you have full armor, Feather Falling, Respiration, and a good sword to counter all the Ooops moments from lag, but even for an experienced Minecraft player (since 1.3) like myself, it's still a major pain and all the chunk lag and general lag in general makes the "improvements" (almost) not worth it at all.
Happens on my Switch as well and the only way to fix it is to log out and quit the game and come back and the carpet in question will be visible.
When my friend and I play, we can't see each others armor changes, either, without saving and quiting and coming back.
If it helps any, I can see saddles on horses just fine.
IMHO, nothing close to “fixed” on the Switch.
Performance on both single player and local multiplayer on Switches with plenty of device space, playing vanilla, with the game optimized, with no add-ons, and on a new world with almost nothing going on is (still) shot.
Lag is everywhere and in everything I / we do and saving and chunk loading takes forever and it renders - haha - the game almost unplayable at times.
Sorry!
I was looking at the previous related tickets as well that included both freezing AND really bad lag at the same time.
When I had previously experienced those same issues on the same console, it had been a related problem.
That said, how do you know the difference between a pure freeze (gameplay stops) and super slow loading (for example, chunks are stuck in loading and you don’t see any visible changes)?
For sure this last update triggered this issue and I play on vanilla.
A few days before then, I had seen a trader with his llamas and they were fine. A llama got left behind and its texture was fine.
I logged in after the update and the left-behind llama turned red and green and when a new trader spawned in, those llamas were red and green as well.
My survival world was created during the version right before this update. I have 1 Active Resource Packs and it's Global. Default Behavior Pack. Yes to bonus chest. No to friendly fire and No to immediate respawn. Everything else in that list is yes. No experimental anything at all.
For Bedrock, is there any way to program our Eyes of Ender to ONLY locate a stronghold WITH an End Portal and have all the other Strongholds be a fun thing to accidentally discover while exploring?
Given that this is a parity issue created by programming differences and choices made during said programming, I feel like the consequence of these choices should be a "fix" that's just for Bedrock.
After all these years, I still don't understand how Stronholds weren't prioritized to not be overwritten - realism or not.
I've played Minecraft since it's 1.3 days on Java and while I've always appreciated the beauty and improvements in realism, nothing - and I mean NOTHING - has frustrated me more as a Bedrock player than this Stronghold issue that, because of programming differences, is considered as "working as intended" when it's honestly not.
I don't give two hoots about my overgrown caves being randomly bisected by some random structure. I don't care if my villages spawn half on the flat Plain and half on a Mountain. I don't care if I suddenly get a teeny tiny desert next to nothing but Jungle.
And you know, I don't even care about the time I exited a Nether Portal and nearly drowned because my game decided to randomly pop me out over an Ocean through an Overworld Portal who knows how many blocks overhead and in midair.
But I care about this Stronghold issue and with all these new world generation changes, I care a WHOLE LOT.
I don't cheat. At all. No locate command. No chunkbase. No creative. No x-ray mods. No asking a friend to even confirm for me that I'm going in the right direction (aka Stronghold WITH Portal) that my Ender Pearl is suggesting.
Minecraft takes time to explore and discover and few things are more frustrating than to finally get to a Stronghold... And discover that there is no End Portal in sight.
It doesn't matter that there are more to find - what matters is the wasted time. You have to triangulate. You have to dig REALLY deep and who knows where you'll end up and how much of what supplies you'll need. The cost of wasted time is even more important given the expanded X and Y coordinates.
To get to the End - the literal "end" of the game, there is only ONE way - through an End Portal - and this is why I just can't fathom why Strongholds and their proper generation wasn't THE priority from the get-go.
That said, with all the new changes, I feel like it's time re-address this issue... Unless everyone on vanilla Bedrock prefers the possibility of blindly digging from +150 to -50 only to find a Stronghold with no End Portal.
I have this as well on Nintendo Switch.
This had been an occasional occurrence already, but after 1.19.20 dropped, it happens every single time and I have to reload the game again and again in hopes of triggering the issue to fix itself.
Bonus points for skin being unavailable during then too!