This has occurred in the official release, and the most recent snapshot updates. I'll walk into a specific area of my map, and my framerate will drop to zero for a few seconds. The bug seems infinitely reproduceable, I can walk into and out of the same map space and have the exact same problem. There's many areas like this on my map, some with differing lengths of LSOD's, occasionally some which require minecraft to be restarted to clear.
This is a new windows install on a computer which has been used to play minecraft before, with absolutely no problems. Intel Core i7 920, 4 GB RAM (On a 32 bit system) with an admittedly outdated Nvidia GeForce 9800 graphics card.
Any ideas? I've tried updating Java and the Graphics card; they're both up-to-date. Tried the increased memory technique for minecraft, no real effect. Playing around with graphics options also had no effect, fancy and fast graphics both have the same problem.
the chunk is most likely to be the issue.
you can try using a region fixer like this https://github.com/F...ft-Region-Fixer
or open the map in mcedit and delete the chunk in question (chunk will regenerate when back in game)
make sure you backup your world before doing any of the above
the chunk is most likely to be the issue.
you can try using a region fixer like this https://github.com/F...ft-Region-Fixer
or open the map in mcedit and delete the chunk in question (chunk will regenerate when back in game)
make sure you backup your world before doing any of the above
Region-Fixer shows no corrupt chunks.
Welcome to Region Fixer!
Scanning directory...
There are 36 region files and 1 player files in the world directory.
#################### Scanning level.dat ####################
'level.dat'\ is redable
################## Scanning player files ###################
All player files are readable.
Well, I'm assuming it's due to your computer having a problem with rendering a specific biome for some reason. Have you tried reinstalling Minecraft?
It seems to happen randomly, in any given biome. I haven't reinstalled minecraft as this was a fresh install of minecraft to begin with, but I'll give it a go.
So, continuing with this bug; with the fresh install, I stopped my player in one of the LSOD areas in my usual savefile. I then exited that save file, opened a second savefile, and the LSOD persisted in that savefile as well. It appeared that chunks were loading slowly. I exited that savefile, closed minecraft, restarted minecraft and reentered the second savefile, and the LSOD was gone.
So, basically, the LSOD seems to persist between save files, once it's been 'activated'; but can be 'deactivated' by restarting minecraft.
This is a new windows install on a computer which has been used to play minecraft before, with absolutely no problems. Intel Core i7 920, 4 GB RAM (On a 32 bit system) with an admittedly outdated Nvidia GeForce 9800 graphics card.
Any ideas? I've tried updating Java and the Graphics card; they're both up-to-date. Tried the increased memory technique for minecraft, no real effect. Playing around with graphics options also had no effect, fancy and fast graphics both have the same problem.
-
View User Profile
-
View Posts
-
Send Message
Moderatoryou can try using a region fixer like this https://github.com/F...ft-Region-Fixer
or open the map in mcedit and delete the chunk in question (chunk will regenerate when back in game)
make sure you backup your world before doing any of the above
Region-Fixer shows no corrupt chunks.
Welcome to Region Fixer!
Scanning directory...
There are 36 region files and 1 player files in the world directory.
#################### Scanning level.dat ####################
'level.dat'\ is redable
################## Scanning player files ###################
All player files are readable.
################## Scanning region files ###################
Scanning: 36 / 36 100% [#######################################] Time: 00:00:27
Found 0 corrupted and 0 wrong located chunks of a total of 18916
It seems to happen randomly, in any given biome. I haven't reinstalled minecraft as this was a fresh install of minecraft to begin with, but I'll give it a go.
EDIT: Fresh reinstall had no effect.
So, basically, the LSOD seems to persist between save files, once it's been 'activated'; but can be 'deactivated' by restarting minecraft.