I would just be wandering around the Nether, make a portal, and it would pop me out in the middle of an enormous ocean with no land in sight. I would eventually make it to shore, but then this would happen:
Whole pieces of the world just disappear. I try to ender pearl over them, but the pearl disappears and I stay put. How/why does this happen?
Rollback Post to RevisionRollBack
A wild opinion appeared! Everybody freak out and start insulting each other because you don't agree with it!
Those chunks were removed by the gods of minecraft and can only be fixed by conquering the 4 lands of minecraftia. You will need to stop the evil lord Darketh and his minions to resolve the unholy lands surrounding the hidden chunk. Then and only then will the missing lands be returned.
When I've run into that, F3+A rarely worked and I'd have to leave the area (greater than view distance or if MP, greater than servers view distance) to cause the chunk to get dumped from memory and then reloaded as I came back. I run into it all the time in modded Minecraft ... it's really annoying. Minecarts and tracks still seem to work through it though which is kind of amazing.
They are a lot rarer in the more recent updates, but far from gone. I'm also pretty sure the chances of encunterung them depend on your computer, although I have no solid proof to back that claim up.
Well, that's a bit confusing for me, considering I've thought they were gone since some time in beta :L
I would just be wandering around the Nether, make a portal, and it would pop me out in the middle of an enormous ocean with no land in sight. I would eventually make it to shore, but then this would happen:
Whole pieces of the world just disappear. I try to ender pearl over them, but the pearl disappears and I stay put. How/why does this happen?
This are corrupted chunks. U can try this Tool to fix it, or look her for help.
And no, More RAM will not magically repair this. U need a Program to fix it.
Whenever somebody tells you to allocate more memory to fix some issue that tells you that they don't know what they are talking about and are just saying that because everybody else does (where in the world did this meme come from and how did it become so popular? If the game is clearly not using all the RAM allocated (close to 100% used) that is most definitely not the problem; I even see threads like this, where they claim the game is running poorly because it only uses a few percent of the RAM allocated). I have no issues at all playing for hours with less memory allocated than the default; as an experiment I removed the -Xms parameter that I use (100% of max allocated from the start) and it only allocated 200 MB to start with.
That said, this seems to be a common issue in 1.8 and it is likely due to changes in chunk loading (they multithreaded it; in earlier versions, people often had issues with Optifine's multithreaded chunk loading, if not quite the same). I've seen this myself, although it went away after reloading chunks, using any of the various methods suggested.
Note that the "chunk loading" issue that Broccoli_Monkey is likely talking about was a rendering issue (the title and description is misleading since chunks are clearly loaded and present, just not rendering properly); the 1.8 issue appears to be an actual absence of chunks loaded on the client, thus the odd glitches that occur if you try to move into them, which also resembles actual chunk corruption, but if they go away after reloading and there are no other issues such as unexplained lag and crashes I doubt they are actually corrupted.
A similar rendering issue also occurs in 1.8, causing parts of chunks to become invisible with an x-ray effect, but this is highly dependent on viewing angle, very similar to an effect that occurred when using Advanced OpenGL on older versions, due to the occlusion culling being too aggressive in both cases. This is however not what is happening here since those rendering issues don't leave obvious holes in the ground, as if somebody dug out all the blocks, leaving the sides of neighboring chunks visible, but rather causes an x-ray effect that lets you see into neighboring chunks and even deeper into the same chunk.
I would just be wandering around the Nether, make a portal, and it would pop me out in the middle of an enormous ocean with no land in sight. I would eventually make it to shore, but then this would happen:
Whole pieces of the world just disappear. I try to ender pearl over them, but the pearl disappears and I stay put. How/why does this happen?
Those chunks were removed by the gods of minecraft and can only be fixed by conquering the 4 lands of minecraftia. You will need to stop the evil lord Darketh and his minions to resolve the unholy lands surrounding the hidden chunk. Then and only then will the missing lands be returned.
Nothing I could say would be better than what's been said already. But F3+A should help.
Also, I thought they fixed these, I haven't gotten one in a long time. I guess I'm just lucky.
Inactive account. See Bio.
When I've run into that, F3+A rarely worked and I'd have to leave the area (greater than view distance or if MP, greater than servers view distance) to cause the chunk to get dumped from memory and then reloaded as I came back. I run into it all the time in modded Minecraft ... it's really annoying. Minecarts and tracks still seem to work through it though which is kind of amazing.
Well, that's a bit confusing for me, considering I've thought they were gone since some time in beta :L
Inactive account. See Bio.
Chunk error. As suggested press F3+A and make sure you have space on your device.
As for the random Nether teleport: Sync your portals.
Before you even THINK about asking for crash help: Guide to fixing and avoiding crashes
I'm on 1.8.8-snapshot.
As am I, and so far I haven't found any, but I'll get back to you if I do?
If you haven't tried it already, maybe you should allocate some more RAM to Minecraft. If you need to know how to do it, just go here:
http://www.minecraftforum.net/forums/support/unmodified-minecraft-client/tutorials-and-faqs/1871637-tutorial-allocate-more-memory-for-minecraft
Hope this helps, I can't think of much else.
Inactive account. See Bio.
This are corrupted chunks. U can try this Tool to fix it, or look her for help.
And no, More RAM will not magically repair this. U need a Program to fix it.
I've already got one and three quarters of RAM allocated (some of my RAM is shared with my GFX card)(1.768GB) That actually might be the problem.
Whenever somebody tells you to allocate more memory to fix some issue that tells you that they don't know what they are talking about and are just saying that because everybody else does (where in the world did this meme come from and how did it become so popular? If the game is clearly not using all the RAM allocated (close to 100% used) that is most definitely not the problem; I even see threads like this, where they claim the game is running poorly because it only uses a few percent of the RAM allocated). I have no issues at all playing for hours with less memory allocated than the default; as an experiment I removed the -Xms parameter that I use (100% of max allocated from the start) and it only allocated 200 MB to start with.
That said, this seems to be a common issue in 1.8 and it is likely due to changes in chunk loading (they multithreaded it; in earlier versions, people often had issues with Optifine's multithreaded chunk loading, if not quite the same). I've seen this myself, although it went away after reloading chunks, using any of the various methods suggested.
Note that the "chunk loading" issue that Broccoli_Monkey is likely talking about was a rendering issue (the title and description is misleading since chunks are clearly loaded and present, just not rendering properly); the 1.8 issue appears to be an actual absence of chunks loaded on the client, thus the odd glitches that occur if you try to move into them, which also resembles actual chunk corruption, but if they go away after reloading and there are no other issues such as unexplained lag and crashes I doubt they are actually corrupted.
A similar rendering issue also occurs in 1.8, causing parts of chunks to become invisible with an x-ray effect, but this is highly dependent on viewing angle, very similar to an effect that occurred when using Advanced OpenGL on older versions, due to the occlusion culling being too aggressive in both cases. This is however not what is happening here since those rendering issues don't leave obvious holes in the ground, as if somebody dug out all the blocks, leaving the sides of neighboring chunks visible, but rather causes an x-ray effect that lets you see into neighboring chunks and even deeper into the same chunk.
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
I get missing chunks all the time. But I have 225 mods so that explains it.
MasterCaver, speaking of XRAY, I've noticed that the TNT-Minecart Xray glitch is still present in MCPE but suffocates you in the PC version.