I'm having a strange issue with Minecraft recently. My friend said that they also experienced it. I'm not sure how to start, so I'll start with how the bug started. I decided that I wanted to generate a new map and build something in a mountain biome. When I spawned, I flew around until I found a mountain, then paused, then changed the render distance to 25. When I unpaused, the chunks on the ground began..glitching? They were like, cycling between random parts of other chunks. So, I paused and quit to the title. The game crashed. I started the game once more, deleted that map. I generated a new one, and it took a really really really long time to get past "Downloading Terrain" When it finally did, the big issue started. The map didn't load, or generate. I was just in an empty void, falling. So I quit, and generated a new map. It crashed at "Downloading Terrain" So, I restarted the game, generated another new map. I was in the void again, but after 50 or so seconds, a few chunks generated. Past that none would generate. The mobs in the chunks didn't move and I couldn't even interact with them. Also, I fell really, really slowly. So, I tried turning on my server and played on my map that had already been working. Everything worked fine with that. Later I tried generating a new map with the server, and I couldn't even join the server. So, I reinstalled all things Minecraft related and tried changing the render distance again. Now. the limit is 16 chunks, but the same thing as before is happening, just now the map will load eventually, just really really really slowly, and mobs wont move while the map generates. I also changed the version to 1.7.10 and the same glitches remained.
Related issues
Comments
migrated
migrated
Looks like a duplicate of MC-62958 for most of it.
For the "keep on crashing" part, it sounds like corrupted files...
Try deleting everything in the Profile Editor tab of the launcher, then create a new one and start a new world and see if it's still happening.
migrated
I reinstalled Minecraft completely, I just now cannot change the render distance past 16. Also changing the render distance (which is now defaulted at 8) causes the whole thing to start over again after a fresh install.
migrated
Also, a lot of the things in that article I didn't experience at all.
migrated
But it starts the same way : Changing the render distance triggers the glitchy biomes event which can be summed up by "Not supported by your computer".
How it will react then depends on your machine, but as it's not supported, crashing (and save corrupting) is an outcome.
I suggest you to first tell us what's your Graphic Card, and add a crash report.
migrated
Well like I said, Its not just me, it happened to two other people when they did the same process I did across 3 completely different machines.
I'll get my graphics stuff in a bit.
migrated
And I don't know if you completely understand my issue. The issue is that when ever I make a new map, it will only load a few chunks, while older saves work fine.And the changing the distance thing. Also, the Render Distance is capped at 16. The crashing/biomes aren't the issue 😛
And of note, I changed it back to 16, where it worked fine before, and the same things still happens.
migrated
The same thing happens to me. I know it's not a hardware issue because Minecraft worked flawlessly in 1.7
kumasasa
Your graphics card cannot handle a higher view distance.
migrated
:\ glad you can magically know the details if my graphics card, setting to 20 shouldn't make te game stop working, AND IT PERSISTED AFTER I SET IT BACK LOWER WHAT IS SO DIFFICULT TO UNDERSTAND
migrated
I mean I can run skyrim on ultra I highly doubt it's my graphics card.
migrated
Well, Thanks for being literally no help at all and closing it for something you assumed and wasn't even what I was asking for help with after 2 other people across completely different computers experienced the same thing. Great. Thanks.
migrated
Being salty is not the best option when asking for help. And you don't seem willing to be helped too. I asked for your graphic card and a crash report and you don't post anything.
As I'm not part of the staff and you act like a jerk, I'm out. Good luck !
migrated
I got pretty offended when it was chalked up as my graphics card not being good enough when there's no way to know that and that suggestion doesn't make sense when 3 different people with 3 different ranging graphics cards all experienced the same thing. No one really seemed to WANT to help, and passed it off is my issue. And I forgot about the graphic card, sorry. I'm out too, thanks for nothing.
A third friend also confirmed experiencing this glitch.