Game crashes when trying to convert world over to new update

Moved to correct location.

Moved to correct location.

I have the same issue with one of my (originally) XB360 worlds ported to XB1. It gets to 11% or 14% converted, before crashing "better together" on XB1. 😞

I have the same issue with one of my (originally) XB360 worlds ported to XB1. It gets to 11% or 14% converted, before crashing "better together" on XB1. 😞

I have the same issue with one of my (originally) XB360 worlds ported to XB1. It gets to 11% or 14% converted, before crashing "better together" on XB1. 😞

I have the same issue with one of my (originally) XB360 worlds ported to XB1. It gets to 11% or 14% converted, before crashing "better together" on XB1. 😞

So I'm not the only one then. I started my world back on 360 during version 1.12 back when saddles were made of cobblestone. When I try to convert it syncs the old data then tried to convert, gets to 2%, freezes, tries to sync old data a second time then crashes and sends me back to the Xbox home screen.

So I'm not the only one then. I started my world back on 360 during version 1.12 back when saddles were made of cobblestone. When I try to convert it syncs the old data then tried to convert, gets to 2%, freezes, tries to sync old data a second time then crashes and sends me back to the Xbox home screen.

So I'm not the only one then. I started my world back on 360 during version 1.12 back when saddles were made of cobblestone. When I try to convert it syncs the old data then tried to convert, gets to 2%, freezes, tries to sync old data a second time then crashes and sends me back to the Xbox home screen.

So I'm not the only one then. I started my world back on 360 during version 1.12 back when saddles were made of cobblestone. When I try to convert it syncs the old data then tried to convert, gets to 2%, freezes, tries to sync old data a second time then crashes and sends me back to the Xbox home screen.

I don't know exactly how old my non-importing 360 world is; probably around TU31. However my super-flat world made at the same time, imported just fine. I wonder what might be a common thread between our problematic worlds... Mine has lots of redstone that likely won't work in the new version, but I still want the build(s). I also have enough redstone and moving "things" going on, that my render distance on 360 is significantly choked.

Finally, I've somehow broken a block on this world: in the midst of many redstone repeaters, one simply stopped working. When I removed the repeater from the block space, I found I could no longer place anything in that space. I can stand in it, but cannot place anything there. Additionally, water & lava will not 'pour' into the space. I got to thinking that maybe this 'broken block' has something to do with the import failing... Does any of this sound like your troubled world?

I don't know exactly how old my non-importing 360 world is; probably around TU31. However my super-flat world made at the same time, imported just fine. I wonder what might be a common thread between our problematic worlds... Mine has lots of redstone that likely won't work in the new version, but I still want the build(s). I also have enough redstone and moving "things" going on, that my render distance on 360 is significantly choked.

Finally, I've somehow broken a block on this world: in the midst of many redstone repeaters, one simply stopped working. When I removed the repeater from the block space, I found I could no longer place anything in that space. I can stand in it, but cannot place anything there. Additionally, water & lava will not 'pour' into the space. I got to thinking that maybe this 'broken block' has something to do with the import failing... Does any of this sound like your troubled world?

I don't know exactly how old my non-importing 360 world is; probably around TU31. However my super-flat world made at the same time, imported just fine. I wonder what might be a common thread between our problematic worlds... Mine has lots of redstone that likely won't work in the new version, but I still want the build(s). I also have enough redstone and moving "things" going on, that my render distance on 360 is significantly choked.

Finally, I've somehow broken a block on this world: in the midst of many redstone repeaters, one simply stopped working. When I removed the repeater from the block space, I found I could no longer place anything in that space. I can stand in it, but cannot place anything there. Additionally, water & lava will not 'pour' into the space. I got to thinking that maybe this 'broken block' has something to do with the import failing... Does any of this sound like your troubled world?

I don't know exactly how old my non-importing 360 world is; probably around TU31. However my super-flat world made at the same time, imported just fine. I wonder what might be a common thread between our problematic worlds... Mine has lots of redstone that likely won't work in the new version, but I still want the build(s). I also have enough redstone and moving "things" going on, that my render distance on 360 is significantly choked.

Finally, I've somehow broken a block on this world: in the midst of many redstone repeaters, one simply stopped working. When I removed the repeater from the block space, I found I could no longer place anything in that space. I can stand in it, but cannot place anything there. Additionally, water & lava will not 'pour' into the space. I got to thinking that maybe this 'broken block' has something to do with the import failing... Does any of this sound like your troubled world?

I struggle with this too. I have an old world of 4.5 years that will not import. It hits 80% and then crashes my game or sometimes my entire console.

I struggle with this too. I have an old world of 4.5 years that will not import. It hits 80% and then crashes my game or sometimes my entire console.

I struggle with this too. I have an old world of 4.5 years that will not import. It hits 80% and then crashes my game or sometimes my entire console.

I struggle with this too. I have an old world of 4.5 years that will not import. It hits 80% and then crashes my game or sometimes my entire console.

No Mitchell that is not the problem I'm having. I think there may be an issue in the coding of my world. I have been working on the same world for 5ish years now. It has been back and forth between the Xbox 360 and the java version of minecraft multiple times using OpryzeLP's Minecraft converter. I have edited the world a couple times using MCEdit. Over the weekend I tried to simply copy and paste the entirety of my world into a new world with the same seed using MCEdit. Even though it messed up in copying some of the chunks, the "new world" converted and opened with no further issues. Another one of my worlds which is a Planetoid/Skyblock Map that I downloaded off of the internet. It transfers fine and I know that it is a modded map made by a third party program on the computer.

No Mitchell that is not the problem I'm having. I think there may be an issue in the coding of my world. I have been working on the same world for 5ish years now. It has been back and forth between the Xbox 360 and the java version of minecraft multiple times using OpryzeLP's Minecraft converter. I have edited the world a couple times using MCEdit. Over the weekend I tried to simply copy and paste the entirety of my world into a new world with the same seed using MCEdit. Even though it messed up in copying some of the chunks, the "new world" converted and opened with no further issues. Another one of my worlds which is a Planetoid/Skyblock Map that I downloaded off of the internet. It transfers fine and I know that it is a modded map made by a third party program on the computer.

No Mitchell that is not the problem I'm having. I think there may be an issue in the coding of my world. I have been working on the same world for 5ish years now. It has been back and forth between the Xbox 360 and the java version of minecraft multiple times using OpryzeLP's Minecraft converter. I have edited the world a couple times using MCEdit. Over the weekend I tried to simply copy and paste the entirety of my world into a new world with the same seed using MCEdit. Even though it messed up in copying some of the chunks, the "new world" converted and opened with no further issues. Another one of my worlds which is a Planetoid/Skyblock Map that I downloaded off of the internet. It transfers fine and I know that it is a modded map made by a third party program on the computer.

No Mitchell that is not the problem I'm having. I think there may be an issue in the coding of my world. I have been working on the same world for 5ish years now. It has been back and forth between the Xbox 360 and the java version of minecraft multiple times using OpryzeLP's Minecraft converter. I have edited the world a couple times using MCEdit. Over the weekend I tried to simply copy and paste the entirety of my world into a new world with the same seed using MCEdit. Even though it messed up in copying some of the chunks, the "new world" converted and opened with no further issues. Another one of my worlds which is a Planetoid/Skyblock Map that I downloaded off of the internet. It transfers fine and I know that it is a modded map made by a third party program on the computer.

Mine gets to 99% and doesn't go any further. Then it just says error

Mine gets to 99% and doesn't go any further. Then it just says error

Mine gets to 99% and doesn't go any further. Then it just says error

Mine gets to 99% and doesn't go any further. Then it just says error

Not fixed for me in 1.2.1 😞

Not fixed for me in 1.2.1 😞

Not fixed for me in 1.2.1 😞

Not fixed for me in 1.2.1 😞

Not fixed for me in 1.2.2 😞

Not fixed for me in 1.2.2 😞

Not fixed for me in 1.2.2 😞

Not fixed for me in 1.2.2 😞

Still not fixed with the 1.2.3.3 beta build.

Still not fixed with the 1.2.3.3 beta build.

Still not fixed with the 1.2.3.3 beta build.

Still not fixed with the 1.2.3.3 beta build.

Not fixed with the 1.2.3 official release.

Not fixed with the 1.2.3 official release.

Not fixed with the 1.2.3 official release.

Not fixed with the 1.2.3 official release.

Don't know what the 321MB update was for on 10/21/2017 as minecraft did not say what's new, but the update did not solve the problem. Will admit, a lot smoother when fetching old saves though.

Don't know what the 321MB update was for on 10/21/2017 as minecraft did not say what's new, but the update did not solve the problem. Will admit, a lot smoother when fetching old saves though.

Don't know what the 321MB update was for on 10/21/2017 as minecraft did not say what's new, but the update did not solve the problem. Will admit, a lot smoother when fetching old saves though.