[MCPE-23345] When I load a specific Minecraft pe 1.1.4 World, after syncing pack with server and It starts to generate the world, it crashes. Created: 11/Jul/17 Updated: 14/Apr/18 Resolved: 24/Jul/17 |
|
| Status: | Resolved |
| Project: | Minecraft (Bedrock codebase) |
| Component/s: | None |
| Affects Version/s: | 1.1.3.52, 1.1.4.51 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Nolan _ Smith | ||
| Resolution: | Invalid | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
|
| Confirmation Status: | Unconfirmed |
| Platform: | Tablet - iOS - iPad Air 2 |
| Description |
|
I still have this problem after 1.1.4 I have gotten Update 1.1.4 from the updates section of the App Store. Not a beta version. When I try to load my red stone testing world, "Testing 2," It says Syncing pack with server, (I don't have any texture packs though) then it says generating/loading world. The green line is about 1 fifth of the way across (without moving) then it crashes, returning me to the home screen. And when I open it again, by double tapping home and clicking on the tab, or clicking the app, it decides to put me on a blank white screen for a while, then finally the menu screen. Half of the time it detects a crash. |
| Comments |
| Comment by Nolan _ Smith [ 25/Jul/17 ] |
|
I still can't open the world though. |
| Comment by Nolan _ Smith [ 25/Jul/17 ] |
|
It doesn't even say it detected a crash, but it doesn't seem to have happened again yet. *It may have been a very fast pulsing redstone clock, that was a very long comparator pulse extender, that I failed at making. *I had it built so when the pulse ran out it would refresh the pulse, but I somehow turned it into a vey fast clock where it kept flashing. I didn't think that could be the case though, because I had done that before. I did figure out how to make a very like 5-10 minute clock though, a chest #1 on hopper pointed into a chest #2, the chest #2 gets filled with items from chest #1, then chest #2 is pushed by sticky pistons onto a hopper that puts them back into chest #1. Then chest #2 gets put back where it started, and begins to fill up again. There's probably a better design that takes longer. |
| Comment by [Mojang] Mega_Spud (Jay Wells) [ 24/Jul/17 ] |
|
Thank you for your report! Crashes such as these are now logged automatically, so will be investigated further by the development team internally. (This means it sends an anonymous crash report when you crash, so you don't have to report it.) If you need help or support, you might like to follow a link below. Quick Links: |
| Comment by Nolan _ Smith [ 24/Jul/17 ] |
|
What does "logged automatically" mean? |
| Comment by Jonathan Hanzel [ 20/Jul/17 ] |
|
|
| Comment by Nolan _ Smith [ 11/Jul/17 ] |
|
Before you ask why all my worlds are named "cool world _" And there are only 9 v2, 10 and 11, it's because I tried to download a shaders "Resource pack" when it was around 0.16.0ish. And my app would open and then crash. I had worlds 1-9. I used the same seed always. "8747" I had to rebuild 1 weeks worth of hours (added up to a week) to rebuild a castle, using only screenshots and memory. And painstakingly counting blocks from screenshots. To build it exactly where it was how it was. And I have no backups. Not even iCloud or a simple 1 gigabyte flashdrive. I swear minecraft worlds take not even a full megabyte. |