So I've noticed some insane chunk lags in 1.7 now. In 1.6.4 I was OK, a little lag on 'Far' render, but in 1.7 it's just ridiculous. This isn't a hardware issue; My computer is plenty fast, and with max render distance, AA levels of 8, max lighting, fancy graphics and Mipmap set to 2, I can get 60 FPS no problem with Vsync. However, those are wasted FPS when my goddamn chunks won't even appear in front of me!!!
I've defragged my HDD, allocated more RAM, moved Java up on the priority list in Task manager, almost everything. Chunks still slow!
Seems as if the chunk proiority is also messed up. I can see chunks as far away as possible loading before the one right in front of me. I thought the 1.7 code rewrite was supposed to "optimize" Minecraft?
For example, here's a big error:
Or this:
I stood there for 5 minutes and they never loaded. Ever. I flew into them (this in creative). Didn't load for a few seconds, then slowly began to appear one by one. Like I said before, This isn't hardware. My computer is plenty fast. And I DO have 64 bit java, if you are wondering.
F3+A helps bunches. It reloads all the chunks visible, but I still need to do it pretty often. I guess it's a small price to pay for not dying in a chunk error
If your world got corrupted you can try to repair it with MCEdit. Open the offending world in MCEdit, press 'ctrl-i' and select 'Repair regions' in the dialogue which pops up. Once this has completed, save your world and exit MCEdit.
To download MCEdit, go to http://www.mcedit.net/ and choose the version appropriate for your OS.
If your world got corrupted you can try to repair it with MCEdit. Open the offending world in MCEdit, press 'ctrl-i' and select 'Repair regions' in the dialogue which pops up. Once this has completed, save your world and exit MCEdit.
To download MCEdit, go to http://www.mcedit.net/ and choose the version appropriate for your OS.
Well, it happens across ALL my worlds, regardless. I'm in doubt that it's a corrupted world, unless something buggered up when I was transferring my worlds form the old computer and it screwed with all of them. Like I said, this didn't happen with 1.6.4.
I'm downloading MCedit right this second and will have it up in a minute. As long as the repair feature doesn't take too long, I might as well do it on all the worlds. Can't hurt, right?
UPDATE: Just did the ctrl-i and repair thing. Worked great! The world I had the most lag on now is seamless.
I've defragged my HDD, allocated more RAM, moved Java up on the priority list in Task manager, almost everything. Chunks still slow!
Seems as if the chunk proiority is also messed up. I can see chunks as far away as possible loading before the one right in front of me. I thought the 1.7 code rewrite was supposed to "optimize" Minecraft?
For example, here's a big error:
Or this:
I stood there for 5 minutes and they never loaded. Ever. I flew into them (this in creative). Didn't load for a few seconds, then slowly began to appear one by one. Like I said before, This isn't hardware. My computer is plenty fast. And I DO have 64 bit java, if you are wondering.
This totally ruins the experience!
1.7 was not made specifically for "optimization", that was dealt with ~1.4 - 1.6.
That is unrelated, but judging from your issue, it seems to simply be a client-side misfunction.
You can usually fix those by holding F3+A at the same time, if not, try to relog into the server.
F3+A helps bunches. It reloads all the chunks visible, but I still need to do it pretty often. I guess it's a small price to pay for not dying in a chunk error
-
View User Profile
-
View Posts
-
Send Message
Retired StaffIf your world got corrupted you can try to repair it with MCEdit. Open the offending world in MCEdit, press 'ctrl-i' and select 'Repair regions' in the dialogue which pops up. Once this has completed, save your world and exit MCEdit.
To download MCEdit, go to http://www.mcedit.net/ and choose the version appropriate for your OS.
Well, it happens across ALL my worlds, regardless. I'm in doubt that it's a corrupted world, unless something buggered up when I was transferring my worlds form the old computer and it screwed with all of them. Like I said, this didn't happen with 1.6.4.
I'm downloading MCedit right this second and will have it up in a minute. As long as the repair feature doesn't take too long, I might as well do it on all the worlds. Can't hurt, right?
UPDATE: Just did the ctrl-i and repair thing. Worked great! The world I had the most lag on now is seamless.
Edit: My maps work great when I load them in 1.6.4, but I would really like to create new maps with the latest version.