MCPE-25452Xbox One Beta "Conversion" Process Deeply Flawed
What I expected to happen:
According to the FAQ:
"Q: I really like the worlds that I’ve built in the old version of Minecraft. Can I play them in Minecraft?
A: Yes, worlds from Minecraft: Xbox One Edition will already be there waiting for you in the play screen, so that you can continue playing."
I expected my LOCAL (XB1v) saves to be readable by the new Beta version of Bedrock Minecraft.
What actually happened was:
Apparently not only are the saves NOT READABLE as is by the new Beta version of Minecraft (requiring conversion) but it doesn't want to read the LOCAL save at all and insists on SYNCING from the cloud, which is very time consuming AND a failure point in the operation (failure to sync).
I don't get it, the CLEAR implication from the FAQ was that our Xbox One version saves would be easily and readily useable by the new version, now I find that this implication was a lie both in the ease and readiness aspects. Not only is there a conversion process, but this conversion process is limited by and affected by access to fast, reliable Internet access (and presumably your own cloud server's reliability)
Why can't I just convert my LOCAL save? Why force me to download and convert the version on the Cloud when all that does is make the process unneccesarily time-consuming AND far more failure-prone? This is especially frustrating given that we're forced to do this multiple times to get a result at all, and then more to get one that isn't borked.
Attachments6
Created Issue:
"Conversion" Process Deeply Flawed
What I expected to happen:
According to the FAQ, I expected my LOCAL saves to be readable by the new Beta version of Bedrock Minecraft.What actually happened was:
Apparently not only are the saves NOT READABLE as is by the new Beta version of Minecraft (requiring conversion) but it doesn't want to read the LOCAL save at all and insists on SYNCING from the cloud, which is very time consuming AND a failure point in the operation (failure to sync).I don't get it, the CLEAR implication from the FAQ was that our saves would be easily and readily useable by the new version, now I find that this implication was a lie both in the ease and readiness aspects. Not only is there a conversion process, but this conversion process is limited by and affected by access to fast, reliable Internet access (and presumably your own cloud server's reliability)
Why can't I just convert my LOCAL save? Why force me to use the version on the Cloud when all that does is make the process unneccesarily time-consuming AND far more failure-prone?
- Unresolved
- Open
- Unconfirmed
- Xbox
- Latest Insider Build
- 1.2.0.22
What I expected to happen:
According to the FAQ, I expected my LOCAL (XB1v) saves to be readable by the new Beta version of Bedrock Minecraft.What actually happened was:
Apparently not only are the saves NOT READABLE as is by the new Beta version of Minecraft (requiring conversion) but it doesn't want to read the LOCAL save at all and insists on SYNCING from the cloud, which is very time consuming AND a failure point in the operation (failure to sync).I don't get it, the CLEAR implication from the FAQ was that our Xbox One version saves would be easily and readily useable by the new version, now I find that this implication was a lie both in the ease and readiness aspects. Not only is there a conversion process, but this conversion process is limited by and affected by access to fast, reliable Internet access (and presumably your own cloud server's reliability)
Why can't I just convert my LOCAL save? Why force me to use the version on the Cloud when all that does is make the process unneccesarily time-consuming AND far more failure-prone?
What I expected to happen:
According to the FAQ, I expected my LOCAL (XB1v) saves to be readable by the new Beta version of Bedrock Minecraft.What actually happened was:
Apparently not only are the saves NOT READABLE as is by the new Beta version of Minecraft (requiring conversion) but it doesn't want to read the LOCAL save at all and insists on SYNCING from the cloud, which is very time consuming AND a failure point in the operation (failure to sync).I don't get it, the CLEAR implication from the FAQ was that our Xbox One version saves would be easily and readily useable by the new version, now I find that this implication was a lie both in the ease and readiness aspects. Not only is there a conversion process, but this conversion process is limited by and affected by access to fast, reliable Internet access (and presumably your own cloud server's reliability)
Why can't I just convert my LOCAL save? Why force me to
usethe version on the Cloud when all that does is make the process unneccesarily time-consuming AND far more failure-prone?What I expected to happen:
According to the FAQ, I expected my LOCAL (XB1v) saves to be readable by the new Beta version of Bedrock Minecraft.What actually happened was:
Apparently not only are the saves NOT READABLE as is by the new Beta version of Minecraft (requiring conversion) but it doesn't want to read the LOCAL save at all and insists on SYNCING from the cloud, which is very time consuming AND a failure point in the operation (failure to sync).I don't get it, the CLEAR implication from the FAQ was that our Xbox One version saves would be easily and readily useable by the new version, now I find that this implication was a lie both in the ease and readiness aspects. Not only is there a conversion process, but this conversion process is limited by and affected by access to fast, reliable Internet access (and presumably your own cloud server's reliability)
Why can't I just convert my LOCAL save? Why force me to download and convert the version on the Cloud when all that does is make the process unneccesarily time-consuming AND far more failure-prone?
Xbox One Beta "Conversion" Process Deeply Flawed
What I expected to happen:
According to the FAQ, I expected my LOCAL (XB1v) saves to be readable by the new Beta version of Bedrock Minecraft.What actually happened was:
Apparently not only are the saves NOT READABLE as is by the new Beta version of Minecraft (requiring conversion) but it doesn't want to read the LOCAL save at all and insists on SYNCING from the cloud, which is very time consuming AND a failure point in the operation (failure to sync).I don't get it, the CLEAR implication from the FAQ was that our Xbox One version saves would be easily and readily useable by the new version, now I find that this implication was a lie both in the ease and readiness aspects. Not only is there a conversion process, but this conversion process is limited by and affected by access to fast, reliable Internet access (and presumably your own cloud server's reliability)
Why can't I just convert my LOCAL save? Why force me to download and convert the version on the Cloud when all that does is make the process unneccesarily time-consuming AND far more failure-prone?
What I expected to happen:
According to the FAQ:"Q: I really like the worlds that I’ve built in the old version of Minecraft. Can I play them in Minecraft?
A: Yes, worlds from Minecraft: Xbox One Edition will already be there waiting for you in the play screen, so that you can continue playing."
I expected my LOCAL (XB1v) saves to be readable by the new Beta version of Bedrock Minecraft.
What actually happened was:
Apparently not only are the saves NOT READABLE as is by the new Beta version of Minecraft (requiring conversion) but it doesn't want to read the LOCAL save at all and insists on SYNCING from the cloud, which is very time consuming AND a failure point in the operation (failure to sync).I don't get it, the CLEAR implication from the FAQ was that our Xbox One version saves would be easily and readily useable by the new version, now I find that this implication was a lie both in the ease and readiness aspects. Not only is there a conversion process, but this conversion process is limited by and affected by access to fast, reliable Internet access (and presumably your own cloud server's reliability)
Why can't I just convert my LOCAL save? Why force me to download and convert the version on the Cloud when all that does is make the process unneccesarily time-consuming AND far more failure-prone?
What I expected to happen:
According to the FAQ:"Q: I really like the worlds that I’ve built in the old version of Minecraft. Can I play them in Minecraft?
A: Yes, worlds from Minecraft: Xbox One Edition will already be there waiting for you in the play screen, so that you can continue playing."
I expected my LOCAL (XB1v) saves to be readable by the new Beta version of Bedrock Minecraft.
What actually happened was:
Apparently not only are the saves NOT READABLE as is by the new Beta version of Minecraft (requiring conversion) but it doesn't want to read the LOCAL save at all and insists on SYNCING from the cloud, which is very time consuming AND a failure point in the operation (failure to sync).I don't get it, the CLEAR implication from the FAQ was that our Xbox One version saves would be easily and readily useable by the new version, now I find that this implication was a lie both in the ease and readiness aspects. Not only is there a conversion process, but this conversion process is limited by and affected by access to fast, reliable Internet access (and presumably your own cloud server's reliability)
Why can't I just convert my LOCAL save? Why force me to download and convert the version on the Cloud when all that does is make the process unneccesarily time-consuming AND far more failure-prone? This is especially frustrating given that we're forced to do this multiple times to get a result at all, and then more to get one that isn't borked.
10-29-2017_1-50-56_AM.png
A
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
This isn’t so much a bug. More of a complaint. As much as I agree with this, I don’t think it belongs on the bug tracker. I think you should repost this on the forums.
Seems like this MAY have been fixed, doesn't seem like it Syncs anymore, rather it seems as though it uses local saves, although the information dispayed (date) is not...current? (A save I had just saved on Console Edition shows up as being from the 28th of last month, seems like that is old cache data or something)EDIT:OK, from what I'm seeing, maybe it isn't fixed at all...it seems as though its using an OLD existing cached version of my save file and NOT reading from the current LOCAL savegame at all, making it impossible to convert my current world. Gonna look at the game management thing and see how much disk space MC(B) is using for gamesaves without actually having any. There was ~500MB of saved data, I deleted it, and when I went back into the game, it showed the correct date on my "Current" gamesave, but failed to show a copy of "Current" I had named "Conversion Fodder"...so I don't know what's up...Aaaaand its doing that thing where it has to sync from the cloud before it will convert again. Laaame.
My old world after conversion (several pictures and videos attached...)
Thank you for your report!
However, this issue has been closed as Invalid.
For suggestions, please visit the Minecraft Feedback Site or choose a link below.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki