Why was this changed to RESOLVED? It has NOT been resolved. The big is still very much present, and there is no pending update for the software on my Switch. You have absolutely NOT FIXED this bug. Item is not resolved.
@hexagon5un @MumblyP
This is clearly directly related, and seems to be 100% consistent across the board in every report I've seen here, as well as around Twitter and numerous reports of the problem on other sites. 15-20 mb isn't a massive save, so these aren't "edge cases" by any means.
Does the testing team not load larger saves? I still don't understand how they missed something that's so blatantly reproducible.
It seems to be related to ANYTHING that can trigger a save, whether it's a mob or otherwise. It seems to be stuck on a repeating pattern of 20-30 seconds of stuttery gameplay, then 60-120 seconds of saving.
Also, now that I can at least get the thing to run even at all, I'm noticing that the pop-in distance is absolutely terrible. Objects I'm facing literally 1-2 blocks away sometimes don't even render after multiple save-freeze loops.
For what help it might be to the people troubleshooting, my save is just under 30mb in size, and I'm currently running 1.18.31 on my Switch. If it's helpful to the devs trying to solve this, I own the game on several platforms and subscribe to realms plus, so I can transfer my world to basically anything but iOS and test/confirm things across platforms online or off with a single consistent world.