Huge chunks rendered invisible after leaving the nether

Have also seen this issue on PC.

I also experienced this bug.

I also experienced this as well as I opened up a report but I didn't know this existed. Thank you because this has been driving me crazy ever since I discovered it myself. I thought my world was going to be corrupted. And unfortunately I decided not to go to bedrock until this issue has been resolved. 

It seems like a lot of people have had this issue. I may have a clue? I'm not sure. I was looking into the difference between an infinite world and the old school? Maybe this is just a rendering issue? I know I've done a lot of stuff with the nether, and that was the only area that has had this issue for me so far.

Was everybody else on an infinite world that they had done a lot of things to?

I've done a lot of things in the overworld, i don't really like going to the Nether unless I need blaze rods for my brewing stand. But I have a friend who just joined my world build some things and we also found the stronghold. As far as I know, he never goes to the Nether until recently to make sure that I wasn't crazy about seeing chunks invisible. 

I just looked at your original issue thread, and yours looks like the same as mine in reverse. Your going from the Nether to your well developed Overworld and it's having trouble rendering? I have been building huge rooms in the Nether, from bedrock to bedrock, top to bottom, 10 long, 10 wide. Maybe 13-14 of these rooms, in a row.

The entire reason I am starting to think this is because I Googled how big an infinite world was exactly, and it's HUGE. So huge maybe it just won't ever render right? IDK. I'm not good with this sort of thing, that's why these help things exist, lol. I could be so off base it's not even funny, IDK. 🙂

I'm actually glad this thread exists or else I wouldn't know exactly what's going on with my world. There's a lot of reasons why it could be happening, infinite worlds can be one of the reasons why it's failing to render. This is also a legacy console edition map that has been stretched out from the basic small to the large world especially after the village and pillage update. I'm also told that every single update to the game might have a 50% chance of either making it better or worse. Most of the time it might get worse as things get added more and more. I'm honestly afraid to even have the nether update on my world, but if that's the case then I'll just work on another new world and making sure I'll have backups just in case if things go wrong. 

Mine is similar but its not invicible it was just dark. That time im using nether to travel so i decide to fix my village perimeter and when i enter the portal to my village its loads long i have to push buttons on my controller weird but it works then the black thing pops up. Then decide to go back to my overworld base but there was no issue.

I am also experiencing this issue. It happens every time I come back from the nether, and only to me. It's not missing, it's just invisible. You don't fall though, my animals don't fall though, and where a wall is you are stopped like normal. I play on a world with friends (not yet a realm) and I am the only one experiencing this issue. It's particularly bad as the chunk goes right through my house, yard, and farm. So I'm unable to do much of anything until the person who's profile has the save resets the game. We use a nether hub to travel in between our bases, so this really sucks.

I too have been dealing with this recently on PS4

im having this issue too...

Update: It's beginning to happen to everyone else too. It's also the same chunks every time. We've also discovered that if you go in/out of the nether enough times the chunks eventually come back. Exiting the world and then coming back also works to make the chunks visible again.

Unfortunately this also happens to me (on xbox) Right where my base is, i have to write down co-ords to know where to go in the overworld because of this bug.

Add me to the list on ps4. Started in 1.14.20 for me. It happens maybe half of the time I leave the nether but EVERYTIME I leave the end. It's always in the same areas too. I have spots I know to "check" every time I come from the nether. If I see a missing mountain or some missing terrain, I either reload the world or go back and forth thru the nether portal until it fixes itself. It looks exactly like the screenshots others have already posted. Creeps me OUT! 

So it happens after leaving the End portal too? I'm wondering if it has to do with how old the world is itself or maybe it affects new worlds too? All I know is that my world is 3 years old before this transition to bedrock and I've never had any issues with it before until now. Hopefully this is a render issue on Mojang's end. And yes it creeps me out too especially since seeing how worlds can get corrupted slowly from every update. I wasn't too sure about what's happening, that's why I have been asking around and seeing if it's happening to anyone else. Apparently it is randomly. 

Happen to me Android official ver. not playing on beta so its really weird! But it only happens when i use the portal to travel on my villager base the rest of my base was okay.

It just started happening to me on the Switch. I think its due to the 14.3 update cause wasn't happening before that.

Yes, always after leaving the end. Leaving the nether does it too just not 100% like leaving the end. The world is 1.04GB if that helps. 

Apparently I'm still having this issue regarding the chunks not rendering properly. 

In which version? 1.14.30 or 1.15.0.54?

1.14.30. I thought this was the actual fix but there's some reports that this update or patch has some Playstation 4 systems crashing. Not on my system though but the render chunk issue is still there for me. 

The chunk render issue is supposedly fixed in the current 1.15 beta (1.15.0.54). We will have to wait for that one to be fully released. 

Yes sadly I thought it was the actual fix until I looked at the version. 1.15 can't come soon enough. 

Hear you. I'm waiting for some crucial fixes that are supposed to be in there. 😺

Any word from a moderator on what was caising this? Why is it always in the same or nearly the same spots? Just curious. 

That's exactly what I want to know, except I made a copy of my survival world and made it creative just to test things out by putting nether portals in different areas and of course the glitch is in a different spot each time. I really hope that 1.5 would come out very soon as I can't play bedrock until then.

IDK if it helps or not, but off the assumption that it's mainly a rendering issue, I lowered the simulation distance from 8 chunks to 4. I haven't had any issues since. 

I can't play with 4 chunks. 10 chunk minimum or half of my farms/redstone stops working correctly. I also run an active despawn system for mobs that mimics the Java despawn mechanic. It requires more than 128 block away to be loaded or mobs won't despawn. If I modify the commands to work with a smaller sim distance then I start to despawn mobs that are too close to the players. So yeah, I need at least 10 chunks. 

The chunks affected by this bug in my world are not within simulation distance of my nether portal, but they are within the render distance. That means that the block data is being loaded when I exit the nether, but the chunks are not active (nothing is being ticked). Also, nothing in my affected chunks would normally be visible when I first exit the nether because there is a hill in between the portal and the affected chunks. So, it seems that the chunks are loaded but none of the textures need to be rendered until I walk over there, and when I do walk over there the texture rendering does not update.

One very curious thing is that most of the invisible chunks in my world are ocean, and when the oceans are invisible, some of the fish in them are do their suffocation animation (flopping back and forth), but they don't die.

Wow that's a huge area, mine happens to be next in between the desert and the little river plus the area that used to be a desert but I took all of the sand out and replaced it with dirt. But the glitch when you turn facing my base has literally split the hill in half making it look like it's disappeared

I'm having a similar issue but it's even worse. Once the chunks stop loading properly and the blocks start appearing invisible I can't do anything at all. I can't interact with blocks (loaded or invisible), and as soon as I try to open my inventory or the pause menu it gives me a loading bar, but it will never actually load. The only way to fix it is to reset the app. I've noticed that this sometimes happens when the game is auto-saving, and it happens most when I enter or leave the Nether. It's entirely random when it happens and you have zero control over it.

As a workaround, you could try lowering your render distance (in video settings) to 10 or 8. That resolved MCPE-44815 for me in a test world.

I have this issue in my world too, version 1.14.30, Win10 platform.

The losing chunks are not exactly the same each time I come back from Nether to OW. The invisible zone usually has an extension of about 20/30 chunks and it seems to be always between the coordinates x:50-350 and z:50-350. My friends who join this world are often affected by the same problem, maybe one or two of us can see the chunks correctly and others can't.

Sometimes returning to the Nether portal and entering the OW again can help re-loading these chunks. If it doesn't work, we have to exit the game and reconnect.

I have just created a new single-player infinite world from random seed to test this issue, with render distance 8 chunks. The problem persists in another area with different coordinates.

We're aware that this is a problem in the current stable version of the game (1.14.x) - what we'd really like to know is whether the issue is fixed for players in the beta version (1.16+).

I updated to 1.16.0.51 and from what I've seen, the bug seems to have been fixed.

What platform are you using? I thought it was supposed to be 1.15? I'm on the ps4 console by the way. 

@crystal ann shell 1.15 is being skipped as a release version, the beta process has moved from 1.15 to 1.16. The beta program is not available on PS4, so you should be on 1.14.41.

Oh ok thank you @GoldenHelmet, I didn't realize that 1.15 was skipped. I wish the beta would be on console maybe someday soon. 

I’m glad to see that this is not a local issue on my console. I am currently on the Xbox One X & experiencing this huge problem. I have to ‘save and quit’ then reload to restore the blocks & textures. From what they’ve said - they’re actively working on a fix, so that’s good news. Fingers crossed it comes quickly.

Again I was hoping for the official release of 1.16 to fix this issue but once again it's only small patches. How long must we wait for 1.16 to fully release on console and pc? And is it possible that it might be released with the nether update as well or will it be a separate thing? 

1.16 IS the nether update. Unless it was in today's hotfix (not in the changelog) or unless they do another hotfix then the fix for this bug will be in 1.16 the nether update. The hotfix that came out today was (I think) mostly for MCPE-32501 which was a critical error, or serious game breaking bug, that needed an immediate fix. 

Hmm I'm still on the 1.14 I believe on Playstation 4 and this was pretty much the hot fixes for game crashes and freezes but it's not for this major issue of chunks appearing invisible. I'm really hoping that it comes out soon, it makes the game or my world become nonplayable. I also have an iron golem glitch as well that just suddenly happened on the same map. Hoping there's a bug report on that as well. 

You should be on 1.14.60 as of today. Yeah I don't know why more of the 1.15 fixes weren't included but the one I mentioned was the real big issue that was causing file corruption. Altho every issue is important to someone, this is not a gamebreaking issue compared to bugs like MCPE-32501 and MCPE-55137. Those bugs can destroy your world file. Comparatively, this bug is a very annoying inconvenience. 

I'm still on the 1.14.60 sorry for not clarifying that. I'm just wondering when the actual full release of 1.16 will come out soon? I feel like since I'm on console and I don't have access to the snapshots that's on PC it's pretty much a very long time to be worked out on unless there's still more issues that are ongoing. 

We are not able to give a release date for any versions or bug fixes. Any release dates Mojang announces would likely be in the “news” section of Minecraft.net.

Why did a bot just change the affected versions to 1.16? I saw that Onesie had to fix it.

happened to me on realms 1.14.60

duplicate of mcpe-73646

^ Other way around. The person that made that report didn't search first. Happens constantly on this site. 

Happened to me today on 1.14.60 Bedrock Server via Windows 10 version.

I have the issue that whenever i go to the nether and come back to the overworld 10 to 15 chunks don't load. I can resolve that by restarting the world but its hell of anoying to restart each and every time i go to the nether. This problem happens even to people that play on my world the need to go out and come back to resolve the issue.

This issue is also present in the current nether update beta. If you leave the end through the end gate and come back to your respawn anchor in the nether, large portions of the nether do not visibly generate. The same can be said for coming back from the nether to the overworld, as your post states.

It also happens in the 14.6 hotfix thing also

This problem makes the game unplayable on the XBox One X, 3 months and still no patch. this must be the buggiest selling game ever, not the biggest selling game ever.

 A massive problem in my world.  Please fix this issue! Such a pain close the game and restarting it!

Issue occurs on the Nintendo Switch as well. reduced the chunk distance to 10 from 14 and seems to have solved it. In my opinion this is not a solution. The Game size is only 10megs so not a game size issue either.

A possible workaround could be changing your render distance or you can relog back into your world again. Occasionally, these chunks seem to render after about 30 seconds. 

I play in Xbox One and this also happens to me!! Please fix it, it's really annoying.

Happens in Windows 10 as well. Always seems to be the same chunk. There's SUPPOSED to be a wall there. Render distance is only 6, so that doesn't seem to help.

The same thing happened to me, except now I’m basically stuck in the Nether. I can’t interact with blocks, and I can’t return to the main menu without force closing the app. 

@@unknown you could try going into the world, moving some distance, waiting 30s or so, and then closing the app, to see if the auto save will put you in a position that loads better. If you can recover that way, destroy the nether portal and build a new one in a different location to prevent the issue from happening again. You could also try lowering your render distance to minimum and lowering the sim distance on the world if possible, at least temporarily to get in to it where you can then move the portal.

The only soultion at the moment is every time someone enters ore lefts the nethe the render distance must be turnt down to the lowest possible and after leaving each side turn it up again. The chunks shouldnt dissapear anymore. Its anoying i know but at the moment its the only way without closing the application every time. Be aweare that if you play with low render distance elytra flying could be realy dangerous so look out my fellow miners xD

Hi, just wanted to update that this has been resolved on my world. I have been going through the nether and coming back to the overworld without any issues. Great job Mojang and thank you!

This issue was fixed in the 1.16.0 release. We have received a few comments since then describing different problems. Such comments will be hidden to avoid confusion.

This report was about specific chunks never rendering after exiting nether portals in specific locations. Chunks in general rendering too slowly, especially when moving quickly (e.g. flying with elytra) is a different issue.