Adam Clark

I have noticed that if I set my Render Distance to 20(20 and above would cause the issue) and reload the world, then 20 and below would be ok and everything above would cause the issue. So I set my distance to 32 and reloaded..... Now everything works fine, I'll be sure to post here if the issue shows up again.

EDIT #1: Just loaded my world up on 32 distance, no chunks loaded at all except for the ones that were within a 2 chunk radius of me. I will experiment with VBOs and post back here.

EDIT #2: Ok, so I turned the distance down to 20 and reloaded again. Now everything works perfectly, with VBOs on and off. Seems like this is just a bug with older worlds, none of my worlds created on the snapshot have this issue.

EDIT #3: Ruh roh.... Now that all of my chunks load fine, none of the entities in my game will function... Mobs don't move and I can't interact with them, can't pick up items, can't open chests, etc.

Just in case someone wanted to see how bad it is: http://youtu.be/Jh4TyCFAeQA ( Epilepsy warning!)

EDIT: Watch the video in HD, I compressed it to hell so that it would upload quickly)

I'm having the same issue, except that 16 is ok for me. Anything above that and it creates an epileptic nightmare of flashing chunks and deformed mob/player models. Will try and upload a video to show exactly how bad it is. And it seems that the closer I get to 32, the worse it gets.

Yes. Confirmed for me in the 1.7 pre-release. This is NOT fixed. Maybe they are fixing it for good in the Official 1.7 release. If not, then I probably wont be playing Minecraft for a while, considering all I play now is multiplayer.

Problem still persists on snapshot 13w43a. I hope they fix this before 1.7 is released.

""EDIT: As seen on this post, it generally happens for people with worse connections, though I never got this error in previous versions."
No, this is not correct. I'm running my server at home, and my PC I play the client is connected via 100Mbs Ethernet, not over the Internet. And I get this error often."

Yes I have confirmed that even when connected through just an Ethernet wire, the issue still happens.

Anyway, even when I'm playing on my 10Mb\s Wireless Connection, (which has never had any trouble with any servers.) this issue is just as bad as when connected directly via Ethernet.

Yes 13w42b is a lot worse than 14w42a or 14w41a/b. I have resorted to playing on 1.6.4 servers instead of snapshot servers.. Oh well, maybe they will fix it in the pre-release.

One other thing not mentioned here. It will get stuck on the Logging in..... and if you are lucky, you will get past that into the server. It usually throws the ReadTimeoutException, and sometimes it will sit on Logging in.... forever.

Still happening on 13w42b. Go to this link for the only open instance of this bug. https://mojang.atlassian.net/browse/MC-34947 Please support it so that Mojang will see it.

The original bug page has been reopened! Here is the link. https://mojang.atlassian.net/browse/MC-34947

Please go follow it, and vote on it!

This is confirmed for snapshot 13w42b.

There is a bug that was closed for being a duplicate of this, when it is a totally different error. Here it is: https://mojang.atlassian.net/browse/MC-34947
Please reopen this so that it will be noticed and hopefully fixed.

I am having this issue, on 13w42b. I have not found any fix or explanation for this. All of my servers rarely get past the "Pinging.." part of the status check. And when they do, even with snapshot 13w42b servers, I get this error. I found if you keep trying, you can eventually connect.

I really don't know what is wrong either nothing was wrong.

Sent from ADAM's IPad

Ok so what has to be in it? What information

Sent from ADAM's IPad

That wasn't very helpful

Sent from ADAM's IPad