Jarred Hoffmeister
- PreciousRoi
- preciousroi
- America/Chicago
- Yes
- No
MCPE-25452
REALMS-2185What 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.
What I expected to happen:
I expected the Sync/Conversion process to continue uninterrupted no matter wether my controller went to sleep or not.What actually happened was:
My controller went to sleep, and a message appeared on the screen saying "Your controller..." and apparently the conversion process paused while it waited for the controller to reconnectSteps to reproduce:
1. engage the conversion process
2. allow a controller to go to sleep or turn it off manually
3. observe that this stops everything from proceeding normally for no good reason
4. consider that you were the ones who forced the game to read the save from the cloud instead of local storage thereby inviting a longer period of inactivity, hence the thing falling asleep...and why does it matter if the damn controller is connnected or not, you can't DO anything while its converting, just stare at one progress bar or another...
What I expected to happen:
I expected the Sync/Conversion process to continue uninterrupted no matter wether my controller went to sleep or not.What actually happened was:
My controller went to sleep, and a message appeared on the screen saying "Your controller..." and apparently the conversion process paused while it waited for the controller to reconnectSteps to reproduce:
1. engage the conversion process
2. allow a controller to go to sleep or turn it off manually
3. observe that this stops everything from proceeding normally for no good reason
4. consider that you were the ones who forced the game to read the save from the cloud instead of local storage thereby inviting a longer period of inactivity, hence the thing falling asleep...and why does it matter if the damn controller is connnected or not, you can't DO anything while its converting, just stare at one progress bar or another...What I expected to happen:
I expected the Sync/Conversion process to continue uninterrupted no matter wether my controller went to sleep or not.What actually happened was:
My controller went to sleep, and a message appeared on the screen saying "Controller Lost Connection" and apparently the conversion process paused while it waited for the controller to reconnectSteps to reproduce:
1. engage the conversion process
2. allow a controller to go to sleep or turn it off manually
3. observe that this stops everything from proceeding normally for no good reason
4. consider that you were the ones who forced the game to read the save from the cloud instead of local storage thereby inviting a longer period of inactivity, hence the thing falling asleep...and why does it matter if the damn controller is connnected or not, you can't DO anything while its converting, just stare at one progress bar or another...
My main base was obliterated by the update.
Also, I spawned on TOP of the iron farm I was supposed to spawn at the bottom of. (Which was cut in half.)
This happens to my world no matter which version I try to convert. (I had a backup and the "current" version that I'd played on since the backup was made)
I will doublecheck that, I was operating under default settings (which I assumed would be set for "Best Practices" for world conversion, and resetting stuff don't jibe with that, but I guess I best not assume anything.)
Yeah, it is.
I've managed to convert a world (albeit a month old) with an intact Nether (and everything else I looked at) , and the same (default, because I never even looked at them) settings, so its not a setting, its a bug, probably cocurrent with and related to the terrain rewrite bug.
I'm going to try to subvert both of them by going back to the XB1v and saving my current world in the Nether and see what happens, as the one I successfuly converted was saved there.
I was able to successfully convert my world, I went back into XB1v and resaved my "current" world while in the Nether. Tried it because a backup from a month ago that was saved in the Nether appeared to work.
Spawns are still broke, and I found at least one Sponge where a Hopper should be. Bonus?
Beacons...needed to be "reset" and still appear nonfunctional, even after resetting.
I have a massive "Nether Cube" Overworld Zombie Pigman Gold Farm...I went up to the top to see if the Pigmen were spawning in, and my framerate dropped to 1.5...
How is it that the older console version performs so well, but the one that you'd think would be optimized for better performance from weaker machines (phones) gags on stuff the older one handles with no problems (aside from the visual bug of not displaying the portals correctly, which is vastly preferable to it being unplayable as it currently the case.
Possible related to/identical to:
MCPE-24124But as this could be an Xbox specific issue I'm leaving it
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.
Previously successfully converted world was broken by latest update. Save was in the Nether, upon loading I spawned inside Netherrack and all indications were that my Nether had been reset with me in it. Also holding down the right trigger only activated my pickaxe once at a time. And all attempts to reconvert my world have met with failure and overwritten terrain/structures in BOTH the Overworld AND Nether, with no apparent relation between the two as far as coordinates go (the overwritten areas do not correspond to each other).
Dawson, the option to delete is hidden in the poorly designed UI at the bottom of the Game Options.
MCCE on XBox One should be updated until this issue is RESOLVED. Full stop.
got my world provisionally converted...dies every time I try rocket assisted flight to check everything out though.
Latest version? I'd guess not, but frankly I can't be bothered with Bedrock anymore.
Conversion is an issue which should have been sorted before bringing it out of Beta and freezing Xbox One users out of being able to update CE on their consoles. I've only ever had the one Survival world and as recently as a month or two ago ago it STILL wouldn't convert correctly (although if memory serves the Nether, at least, wasn't reset)...
I'd strongly prefer to just be able to play with all updates on CE at this point. I was one of the people saying "don't worry, I'm sure everything will be fine" when Bedrock (and its forced "upgrade") was announced. I was SO wrong. You have basically driven me from the game. CE doesn't get updated with new stuff, and PE/Bedrock not only doesn't convert my world, the one I've put every bit of effort into, its ugly (the trade UI for instance looks like something designed with Visual Basic by a rank amateur circa 1995) and clumsy. I'm mortified I expressed confidence in y'all "getting it right".
I should be playing with my Survival world on Realms right now, I had a few people interested, but how can I play on Realms when my world won't even convert?
SHAME. SHAME ON YOU.
If the "resolution" of this issue means that y'all think that Xbox One version maps are being correctly converted into the Bedrock version, you're sadly mistaken. I had high hopes, but when I tried, yet again, to convert my existing Xbox One version Survival World, once again, it appears the conversion was not a success. Out of 11 Maps on my Map Wall, SIX of them failed...middle far north, middle far west, near SW, and all three Near East maps.
Blank Blank FAIL Blank Blank
Blank GOOD GOOD FAIL Blank
FAIL GOOD GOOD FAIL Blank
Blank FAIL GOOD FAIL Blank
Blank Blank Blank Blank Blank