Newly generated chunks are very often invisible until I get REAL close to them (literally stand on the edge of them). Sometimes a whole region of the world will be invisible until I travel to each individual chunk.
Attachments
Comments 10
This is similar to what I'm getting too. @Samuael Klumpers, I know the behaviour you are describing, but this is different. Ver 1.7.9 works fine, but with 14w18b snapshot you get this problem.
Here's a screenshot.
http://oi61.tinypic.com/xbydfo.jpg
I've done this in creative, survival and hardcore modes. Basically I approached this location after starting a new world. I'll sit at spawn until the chunk updates drop down to single digits and stay there for an extended period of time. Then I fly up in the air and look around, everything in the sight line of spawn is usually good. Moving away you will consistently run into areas where multiple chunks are not loaded like in the screen shot. This is after chunk updates have dropped down to single digits again.
If you leave the world and join it again everything draws correctly around you, and then exhibits the behaviour again as you travel. As well, if you walk into a chunk it will render.
I'm running linux mint 14, java 7, nvidia gtx660.
This is only in the 14w18b snapshot.
I'm still seeing the same behaviour in 14w20b.
In 1.7.9 I consistently get 59-60 fps on the highest quality settings. With occasional, brief drops to mid 40s when it's generating new chunks in the world. In 14w20b I rarely hit 60 fps unless I stand still and don't look around. I'm usually 30-40, fluctuating quite a bit and even lower when it generates new chunks.
The chunks seems to load differently in the snapshots. It's almost like they don't even start loading until you look in that direction sometimes.
I've been in the habit of starting a new hardcore game every time a snapshot comes out to see how far I can get in it before the next one. I'd say I've done that maybe for the last 25 snapshots, missing maybe only 2 or 3. The last three have been essentially unplayable because of this issue. That's the first time I would say that and the reason I joined the bug tracker.
There does seem to be an issue with chunks loading. There also seems to be a memory leak when this bug happens. In-game Minecraft says it's using 1022mb of memory, but Task Manager says it's using 7.2gb and growing. So there seems to be a discrepancy there. Also, CPU usage keeps spiking to 100% and freezing the game every few seconds.
It isn't working as intended but it's intended in some way, because this is in since Minecraft existed. It kinda depends on your computers speed how much of a problem it is to load the chunks fast enough (or too slow).