Since the 1.16 update has been implemented, severe problems have been noted with the automatic autosave of worlds, a problem that stands out especially on olg gen consoles (Switch, Playstation 4 and Xbox One). Once the autosave is executed, the world tends to freeze for a certain amount of seconds in all its senses while in process, leaving the world unplayable during this time, unable to interact with any block or mob, generating crashes of music/sounds and terrain generation. It also affects processes such as crop growth, day/night cycle, mob generation, etc.
In addition, it is a problem that becomes exponentially more frustrating as the world gets larger, since more data must be stored. So, in some worlds just started, it can be a problem that lasts app 15 to 20 sec, but with some worlds over 200mb of weight can last over 60 sec and even reaching 3 minutes of freezing, and this is not the worst, since the world tends to autosave for almost every move we make, so this happens more often everytime, until it reaches a point that the worlds become totally unplayable.
I am not an expert in programming to say this, and I understand that it must not be easy to fix such a big problem, but I really believe that this problem must be fixed, we have had this problem for more than three years and it only gets worse and worse with every update. And even if it is too complex to fix as soon as possible, an option to disable the autosave would be really appreciated, leaving this option as something manual that the player must use as it was in Minecraft Legacy Edition (Versions developed by 4J Studios).
I will leave a video that I found on Youtube in my little investigation of the problem. It is difficult for me to send you a video taking into account that I play from my Ps4, but my case is not far from what you see in this video:
[Credits to SantyEagle for uploading the video]
Related issues
Comments
Arisa Bot
migrated
Not the same problem lol, the issue in MCPE-155469 is about losing progress in the world cause autosave stops working.
In the case I have detailed, the autosave process occurs as normal and there are no problems with the progress being saved at the time the autosave is executed, but it interferes with the gameplay during the process, making the game unplayable while running. It does not get stuck in autosave, it is the gameplay that freezes.
I hope this comment helps, and it is understood that they have been confused because they are linked to the same thing, but they are not the same.
migrated
We’ve had this problem as well on PS4. We tried deleting as many worlds as we can and it helped a little but it’s still glitchy as hell making it very difficult to play. This is separate from a related issue
MCPE-155469 where it doesn’t save at all when I’m multiplayer. You lose all progress.
Even though it’s glitchy you can still save it in single player
v-baslod
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Is this still an issue in the latest version? If yes, can you please add it to the affected versions (or mention it if you are not the reporter)?
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📓 Project Summary – 📧 Suggestions – 📖 Minecraft Wiki
migrated
2024 and this is STILL a huge problem on the latest version of bedrock on PS4. Most definitely NOT resolved!
Thank you for your report!
We're tracking this issue in MCPE-155469, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.