-
Bug
-
Resolution: Cannot Reproduce
-
None
-
1.12.0
-
None
-
Unconfirmed
-
Nintendo Switch
So I was going to play Minecraft the other day. I turned on my Switch, which wa on sleep mode and had minecraft running in the background, and resumed Minecraft. When I entered the world, some textures were glitched. I took a video captrue and poasted it to Twitter (https://mobile.twitter.com/chienm1/status/1153788818182422528). I restarted my world and the texture was fine. Today, I was going to play Minecraft again and went to check the News on the Switch first. (Note that Minecraft was running in the background with my world loaded). When I resumed Minecraft, the texture was glitched again. I restarted my world again and everything was fine. Two hours after I put my Switch to sleep. I repeated the same step that I did last time with the news and resume Minecraft, and my textures was glitch again. I went through each block and item and place down every block that was glitched (except lava and trapped chest. The lava was not glitched this time and I forgot to place down the trapped chest, but it was in my inventory second slot). I recorded a video and placed it on YouTube (https://m.youtube.com/watch?v=SbRwedXDKcs) because it was 20 times larger than 10 mb. I also did a video capture during the recording which I post it on Twitter (https://mobile.twitter.com/chienm1/status/1154205846412247041).
One hypothesis I have is that this only happens when the Switch is turned off for hours. I tried replicating this in minutes and it did not work. But every time it happened, my Switch was off for more than an hour. It's just a hypothesis though.
Basic.y texture is Brocken when Switch is turned off for a long time and resuming Minecraft through the home screen when turned on.
This isn't a big glitch but it is annoying to close the world and open it back up each time.
Update: the glitch happened again after I redownload Minecraft on the Switch. Again, I turned on the Switch, went and check the news, and then resumed Minecraft and the glitch was happening again. I have taken pictures of the blocks that are affected, which are attached to this issue, and an updated video (which can be found here: https://m.youtube.com/watch?v=fImKCQ4psW8)