I initially suspected that the world might be corrupted because some older areas of the world experienced unusual biome changes after a Minecraft update. However, I am no longer sure that this is related to the Realms upload failure.
The world is approximately 370–380 MB, and the Realms upload usually fails at around 120 MB, before the entire world has been uploaded.
According to the information posted on REALMS-474, Realms first uploads the complete MCWorld file and only after that does the server unpack it and check it for errors. Because my upload fails long before the full file has been transferred, this seems more consistent with the Realms upload/transfer problem than with Realms rejecting a corrupted world.
Additional information:
Platform: Minecraft for PS5
World size: approximately 370–380 MB
Smaller/new worlds upload to the same Realm successfully
Approximately 372 GB of free storage on the PS5
Internet connection: 500/500 Mbps
PS5 upload test: approximately 140 Mbps
I have also previously tried limiting upload speed to approximately 15 Mbps, without solving the problem
The large world plays normally locally on the PS5
The world may still contain some damaged or incorrectly upgraded biome/chunk data, but there is currently no evidence that this is what causes the Realms upload to fail.
This appears very similar to REALMS-474, particularly the issue described with long uploads of larger worlds. The planned Realms Storage V2 system, which uploads files in pieces rather than as one long transfer, sounds like it could directly address this type of failure.
RussAnd01
Additional information / clarification
I initially suspected that the world might be corrupted because some older areas of the world experienced unusual biome changes after a Minecraft update. However, I am no longer sure that this is related to the Realms upload failure.
The world is approximately 370–380 MB, and the Realms upload usually fails at around 120 MB, before the entire world has been uploaded.
According to the information posted on REALMS-474, Realms first uploads the complete MCWorld file and only after that does the server unpack it and check it for errors. Because my upload fails long before the full file has been transferred, this seems more consistent with the Realms upload/transfer problem than with Realms rejecting a corrupted world.
Additional information:
Platform: Minecraft for PS5
World size: approximately 370–380 MB
Smaller/new worlds upload to the same Realm successfully
Approximately 372 GB of free storage on the PS5
Internet connection: 500/500 Mbps
PS5 upload test: approximately 140 Mbps
I have also previously tried limiting upload speed to approximately 15 Mbps, without solving the problem
The large world plays normally locally on the PS5
The world may still contain some damaged or incorrectly upgraded biome/chunk data, but there is currently no evidence that this is what causes the Realms upload to fail.
This appears very similar to REALMS-474, particularly the issue described with long uploads of larger worlds. The planned Realms Storage V2 system, which uploads files in pieces rather than as one long transfer, sounds like it could directly address this type of failure.
But I don’t know.