Eddie Federmeyer

@ijustbiel Glad to hear it! Fingers crossed sooner than later!

I got a response after a couple days with Twitch support. They said to contact Microsoft/Mojang. But it appears @ijustbiel was told to contact Twitch.

I would love to upload my save, however I don’t know who’s I would do so since this is from PlayStation and it doesn’t support saving the world to a usb. Are there any ways I can do this easily without realms? 

(Note - my world is bigger than 900mb)

I've had issues with my world since 1.17.41:

In 1.17.41 (Experimental caves and cliffs on), my world would occasionally give an error on the PS5 saying "Out of storage" with the pink and black null texture as the screen background when there's clearly storage left still. My resolution to this issue was to avoid exploring into new terrain generation. As long as I stayed within already generated chunks it seemed alright for the most part.

In the new 1.18, my world has a variety of different results. If I try loading a the world directly from an old nonupdated backup and update it, it loads without textures and eventually crashes simply stating "There was an issue loading this world". After I restart the game itself and try loading the previously crashed world, it loads this time with some textures (chests, entities, some other 3D blocks) but then shortly crashes with the message "I'm out of storage" (Similarly to in 1.17.41). Upon testing with the world a couple different ways to load it (never able to actually play for more than 10 seconds), I also encountered a scenario when the game crashes in it's entirety. (Not sure how to replicate that I'm afraid). My personal fix for 1.17.41 doesn't work at all.

Note, my world is 900~mb and grew a small amount (30~mb) upon updating it.

I'm having the same issues on my PS5. I've seen some people be able to successfully load their worlds after having this issue by copying it to a PS4 and playing it on there. I'll try this for myself later. It's infuriating that this is an issue that's persisted since 1.17. Hopefully they can pay attention to console issues. Any statement by Mojang about this issue would be appreciated, but I doubt we'd get one since this is primarily a console issue.