Chris
- Chilidad
- chilidad
- Europe/Stockholm
- Yes
- No
MCPE-39981Summary: I use the onscreen touch sensitive controller (herein "navigator") to move around in MCPE. Sometimes when pressing 2 Navigator buttons simultaneously, the game freezes with the message, "Minecraft has stopped responding." Waiting for 10 minutes doesn't change the freeze status. Only remedy is to close the app and restart it.
History: I've used MCPE since 2012. I haven't seen a navigator issue this bad since using a Kindle Fire back in 2015. I use a Galaxy Note 3 now. In fact, I've had no navigator issues since 2015. Now, this issue has been occurring since (12.12.2018) after the last update. I'm on 1.8.0 now.
Expected Result: When pressing 2 navigator buttons simultaneously, one button's output should simply be accepted while the other ignored.
Actual Result: Pressing 2 navigator buttons simultaneously causes game to freeze.
Occurrence Probability: I estimate this issue occurs 25% of the time. It's hard to determine since I don't have a way of knowing when my touch actually translates into a signal. I can only define the issue as "simultaneous button pressing" since it ONLY occurs when quickly going from one navigator button to another... it's a smartphone... and it's fat-thumb syndrome.
Steps to Reproduce Issue:
- Seems to occur more in jungle biomes.
- Running straight forward with forward button (herein "UP").
- Issue occurs when I must slide thumb to another button when something motivates me to turn: a tree, a cliff, a little bastard zombie. Issue more frequantly occurs when having to thumble around on the navigator because of a startling unintended motion. (For example, I sometimes inadvertently climb a vine when trying run through it. Upon scrambling on the navigator to dislodge, I seem to press both the UP and LEFT arrow at the same time, resulting in a freeze.)(Another example is when a little bastard zombie attacks me. When thumbling around to get away, game freezes)
- Also, just prior to the freeze (within 10 minutes), the navigator will behave erratically. For example, pressing dead center in the UP button invoke a wild spin with me ending up looking straight up. When I don't have coordinates, compass or daytime, I lose all sense of direction.
- Issue occurs regardless of navigator size. I usually play with it at the max 100% size.
Just restored world from bare-metal nandroid backup.The world is there, but it's missing complete chunks, and I've lost all my building progress. I wented to an older backup, but same symptoms so I know it's not a corrupt data issue or anything. Also, my purchased skins are missing even though it show my login name ia correct. All was working fine in July 2019, when I last played.
How do I get this latest version of MCPE to load my map correctly and get my purchased skins back? Or is this issue a bug?
Problem: Chunks missing everywhere I've built on a world, but it's not due to corrupt data. It's due to the latest update to v1.14.1
Background:
I created a world using MCPE.
Regularly back up this world by copying it's minecraftWorlds folder to thumbdrive.
After v1.1.14.1 update, this world went from 80Mb down to 2 Mb and large chunks are missing.
Closed out ouf MCPE, deleted the shrunken world folder and copied my world backup back to it.
Opened MCPE again and loaded the world, but same problem exists
To ensure it is NOT a corrupt data issue, I copied that same backup to minecraftWorlds on my desktop (Windows 10). It loads fine and everything is as it should be.
The world has been entirely created in Survival Mode. All my achievement are correct. My sign-in info is correct.
The only other odd symptom is that after the update, MCPE generated a minecraft pillager outpost right in the middle of something I was building. As soon as I start walking toward it, the chunks disappear, and I seem to die from being attacked. After respawning, I'm back at the original default coordinates with all my building progress lost to the default world map.
I also tried loading this on another android phone (which has NOT updated-ed yet) andthe world loads fine on that device. I also loaded it on my son's android phone (which HAS been updated to v1.14.1) and the same problem occurs.
Help Request:
If this issue is due to a configuration change that was forced upon me during the last update, please provide instruction to reverse it.
If it's a bug, please tell me the version that was current in July 2019? And how do I install the older version on my Android phone? And how would I turn off updates until there's an update to fix this issue?
Complete chunks missingin worldComplete chunks missing after update v1.14.1
My son posted this trouble ticket. I will resubmit formally.
-Chris
Forgot to mention... this issue has only been occurring since (12.12.2018) after the last update.
Your issue sounds like mine. I've learned that it's not due to a corrupt world, but rather something to do with the latest update. For example, copying your world to an older version or Windows 10 desktop will likely work fine.
Reference -->
MCPE-60952I have been around and around with Mojang on this ticket. They've confirmed an issue with large maps losing chunks when updating. It has something to do with new mob structures being forced on a map. A temporary solution has been to downgrad to Minecraft - 1.12.1. This temporary fix has worked on all maps which experience the lost chunks. So now the only way to use your large map with the latest version is allegedly to meticulously cut out all the chunks you've edited on your map and paste them into the new version of the map... using a map editor.
I haven't tried the editor yet as it looks quite time intensive, but I will report back when I make progress. It's unfortunately been near impossible to get timely help or non-conflicting information from Mojang.
I have been around and around with Mojang on this ticket. They've confirmed an issue with large maps losing chunks when updating. It has something to do with new mob structures being forced on a map. A temporary solution has been to downgrad to Minecraft - 1.12.1. This temporary fix has worked on all maps which experience the lost chunks. So now the only way to use your large map with the latest version is allegedly to meticulously cut out all the chunks you've edited on your map and paste them into the new version of the map... using a map editor.
I haven't tried the editor yet as it looks quite time intensive, but I will report back when I make progress. It's unfortunately been near impossible to get timely help or non-conflicting information from Mojang.
Idk why mojang won't address this issue. I brought it up last October when it started, and again a few months later, but they have just continually given me the run-around with zero attempt at a solution (see
MCPE-60952that I created).I have many examples, and they all look similar to the screenshots you guys have attached here. And yes, the worlds are all completely vanilla.
What I do know is this:
So, since mojang isn't offerring any kind of recognition or resolution to this specific bug, I propose posting a different question, which is....
Devs, if we have a world that works fine in Windows Bedrock v1.16.10 and MCPE prior to v1.14.1, but anything after MCPE v1.14.1 destroys the world, how do we transfer our currently working world over to MCPE v1.16.10 or higher?
Thank you for your time...
Copied my mcpe world from "/MC/com.mojang/minecraftWorlds" to new phone, and now it has these same chunk bug issues. Copied same world to PC bedrock and it works fine. Saved from PC and put back on phone... missing chunks again. So seems to be a bug tied to mcpe? This bug is a game breaker and extremely old... please fix mojang!
I've noticed this case hasn't progressed much since I opened this issue 2 years ago. Mojang never responded directly to my suggested resolution (or vital evidence), and it's now buried deep in this thread and/or links to mis-closed or mis-merged cases. So, in hopes of directing Mojang to the actual problem... here it is again:
1. The problem occurs when,
-A Mincraft update adds a new mob.
-The new mob spawns in location that the user has previously edited. For example, I built a structure where now (after an update) a piliger tower spawned (a newly added mob at the time). That location then developed a huge missing chunk/s.
2. This issue only happens on my "heavily" edited stock worlds (vanilla with no mods). Since this means the issue only may occur on user's deeply time-invested projects, I believe it should now be Mojang's best critical interest to fix this issue.
3. As an interim solution, I'm again requesting a tutorial on how to stitch in a chunk. If we have this procedure, we all could take the chunk coordinates from a good backup world, and then replace those coordinates in the world after it has been updated, thus overwriting the corruption in the location that the update caused.