I had a bit of a further play about with this bug. I started up a brand new world in creative mode and blasted around it with a pair of elytra, and with the exception of a couple of times the rockets lagged a bit (and it was a bit slow but not dramatically slow loading going through nether portals), I didn't have any problems with chunk loading. Total time to save once I exited was 25 seconds. I then went into a very old world with heavily developed chunks, and the problems cropped up within seconds. I teleported to an unexplored part of the world to generate brand new chunks, and the problems still cropped up. Total time to save once I exited was over 2 minutes. Hope this is helpful in some way.
I had this problem a few weeks ago and it mostly went away by itself before coming back with a vengeance this weekend. I've also noticed that when this glitch happens, it can take ages ( >3 minutes) for the game to save in single player.
Your ticket is more detailed. Since there's been no updates on this I'll ask a technical contact at Mojang to take a look at your ticket instead 🙂
Hi, we believe we've ironed out most crashes users were experiencing on our server during tests. We have an in-game bug report function which will gather details and if you give a description of what happened around the time we can look into it for you as well. We'll be in touch with the developers over at mojang too to see if they can give us some insight into the problem 🙂
In any case thank you for the report!
Hey, regarding galaxite we're not quite launched yet. You may be able to occasionally join on evenings when we're testing. We're looking to soon keep it online for extended durations. If you see "coming soon" it just means we're not quite ready yet for you to join. If the message of the day (the text under the server name) changes, we'll either be running a test which you can join or we may be at the point you can finally play 🙂
The issue is still as it is in the above video.
If you have an ender pearl and somewhere to throw it you can free yourself that way.
Ehh... Yep, forgot I'd set it to a silly high speed. Works as intended when set back to the default value.
Still present in 17w18a and 17w18b. Sometimes when you reload a world, the top half of the bed will be visible, but the bottom half won't be. This is only if you've previously made the bed visible by attacking it.
[media]
When trying to ride a tamed horse, I got kicked from the game and told 'flying is not enabled on this server' and sent back to the multiplayer 'looking for servers' screen, which is extra odd as I was playing in single player.
Happens when flying and lowering yourself slowly using shift. Lowest y co-ord I got was about 0.12 before the crash.
I've done a bit of playing around and it seems that if you lit a portal in 1.7 it'll stay lit if you upgrade the world to 1.8, but if the portal was most recently lit in a version earlier than 1.7, it'll be extinguished if you upgrade.
This is happening in my single-player world in the latest snapshot (14w34c). It only seems to affect 2x3-sized portals, though- all other sizes seem unaffected. If I reignite the portals, exit the world then load it back up, the portals remain lit up.
As requested
Related tickets, clearly this is causing confusion:
MCPE-156063
BDS-15545
MCPE-153181
MCPE-28724
It would be useful to get this translated, this will allow 3P servers and opensource software to make use of the string.