I have a pre-update world which I wanted to start using creative mode to add to the buildings I had. Only thing is, there's a particular point in my world that when I go near it, the game freezes and I have to turn the console off. It happens 100% of the time when I try it.
I've been trying to keep up to date with the forums since the update, and have seen plenty of similar posts, but they all relate to multiplayer, or having too many signs.
My world only has about 5 signs all of which are at the opposite side of the map.
The only thing noticeable is that the entire area I am trying to approach used to be a lush green area, but it is now completely snow covered, with a large portion of the surrounding water turned to ice.
Could this have anything to do with the crashing? Are there any other suggestions as to what I could try doing to prevent the crashing?
Sounds like bad chunks. I had the same thing happen to 4 or 5 of my old worlds. Nothing I could do except delete them. people say it's because there are "bad sectors" on your HDD. Whatever it is, I've seemed to avoided it by keeping my worlds stored exclusively on Cloud Storage.
Thanks for the suggestions.
I already have my worlds saved on cloud storage, so I guess that rules out the bad sectors idea.
And I just tried saving the game literally one block away from where it will normally crash, but that didn't seem to help either. I think im convinced it has something to do with the biome change, as it was very widespread. I'll try post some pics.
Have you tried loading the world while you're offline. I don't use the cloud, but I suspect you will have to first transfer a copy of your world to your hard drive. If this is the case, use the main XBox file copy feature, not the rename one which people have been reporting is arbitrarily overwriting worlds.
Then, while the world is loaded offline, see if you can get through that particular area without the game crashing. If so, then manually save. Then, reconnect the XBox and see if the world crashes again when you're back online. If it does, then this probably means that the XBox (with Live connected) is just trying to process too much data at that point. I don't think it has to be signs... it could be biome information, could be chests, could be mobs. To the system, data are data... and too much data are just too much data.
ETA: Just read a post on another thread that indicating loading 2 players in local splitscreen mode helped solve a crashing issue. This seems somewhat counter-intuitive except that the draw/rendering distance in local splitscreen is reduced from what it is when there is a single player on one large screen. Therefore, if the rendering is what's overloading the system, this might also work... worth a try.
I've been trying to keep up to date with the forums since the update, and have seen plenty of similar posts, but they all relate to multiplayer, or having too many signs.
My world only has about 5 signs all of which are at the opposite side of the map.
The only thing noticeable is that the entire area I am trying to approach used to be a lush green area, but it is now completely snow covered, with a large portion of the surrounding water turned to ice.
Could this have anything to do with the crashing? Are there any other suggestions as to what I could try doing to prevent the crashing?
I already have my worlds saved on cloud storage, so I guess that rules out the bad sectors idea.
And I just tried saving the game literally one block away from where it will normally crash, but that didn't seem to help either. I think im convinced it has something to do with the biome change, as it was very widespread. I'll try post some pics.
Then, while the world is loaded offline, see if you can get through that particular area without the game crashing. If so, then manually save. Then, reconnect the XBox and see if the world crashes again when you're back online. If it does, then this probably means that the XBox (with Live connected) is just trying to process too much data at that point. I don't think it has to be signs... it could be biome information, could be chests, could be mobs. To the system, data are data... and too much data are just too much data.
ETA: Just read a post on another thread that indicating loading 2 players in local splitscreen mode helped solve a crashing issue. This seems somewhat counter-intuitive except that the draw/rendering distance in local splitscreen is reduced from what it is when there is a single player on one large screen. Therefore, if the rendering is what's overloading the system, this might also work... worth a try.