I am a father of 3 boys and we all love minecraft and often play it together in a local game using 3 switch lites and one normal switch. As a professional software developer I know that the switch itself is not a high performant console and that game studios have to make a lot of compromises in order to port their games to this platform.
Long story short: We are facing exactly this issue described by @Ismael, but only for a short time. It seems as if the last patches make things worse and had increased the lagging, respectively the hanging.
Here is a short description about the things that I have noticed (maybe they are helpful):
few weeks ago I had downloaded some free texture packs from the market place. This was the moment as the problem started on the normal switch. Maybe this was a random circumstance, but when I removed them and cleared the market place cache, the period of the lagging significantly decreased. Also clearing of the market place cache on the switch lites decreases the lagging period
We are facing the issue not only in our older save games (~65MB) as @@unknown described too, but also in new ones that are used as local multiplayer games.
The issue that new local player games are hanging and lagging is new to us. At the beginning of this year I would suppose that everything worked fine. So it seems to me that one of the last patches of 1.19 (currently we have version 1.19.62) make things more worse
We are great fans of this game. And we have spent a lot of time and have build many cool worlds that mean a lot to us and which are currently unplayable ... unfortunately 😞
When all issues relates to the low performance of the switch platform in addition with the auto-save function, would it not be the easiest first workarround to add a switch for activating/deactivating the auto-save function to the bedrock version too? Let the users make the decision to take the risk to loose their last made effort when not saving manually instead of realizing well-saved but unplayable worlds 😞
Sandmann
Hi,
I am a father of 3 boys and we all love minecraft and often play it together in a local game using 3 switch lites and one normal switch. As a professional software developer I know that the switch itself is not a high performant console and that game studios have to make a lot of compromises in order to port their games to this platform.
Long story short: We are facing exactly this issue described by @Ismael, but only for a short time. It seems as if the last patches make things worse and had increased the lagging, respectively the hanging.
Here is a short description about the things that I have noticed (maybe they are helpful):
few weeks ago I had downloaded some free texture packs from the market place. This was the moment as the problem started on the normal switch. Maybe this was a random circumstance, but when I removed them and cleared the market place cache, the period of the lagging significantly decreased. Also clearing of the market place cache on the switch lites decreases the lagging period
We are facing the issue not only in our older save games (~65MB) as @@unknown described too, but also in new ones that are used as local multiplayer games.
The issue that new local player games are hanging and lagging is new to us. At the beginning of this year I would suppose that everything worked fine. So it seems to me that one of the last patches of 1.19 (currently we have version 1.19.62) make things more worse
We are great fans of this game. And we have spent a lot of time and have build many cool worlds that mean a lot to us and which are currently unplayable ... unfortunately 😞
When all issues relates to the low performance of the switch platform in addition with the auto-save function, would it not be the easiest first workarround to add a switch for activating/deactivating the auto-save function to the bedrock version too? Let the users make the decision to take the risk to loose their last made effort when not saving manually instead of realizing well-saved but unplayable worlds 😞