I get incredible lags when using the render distance as TINY... but when I set it on FAR the lag goes away, but only for a short while and then I have to turn the fog back down to TINY... and then it starts lagging like hell yet again, and I have to set it back to FAR... rinse lather repeat... what in the hell is going on here?
This sounds like it might be a problem that you're having with your location. Does this happen on multiple saves and or servers? Does it happen while standing still? How about time of day? Is it possible that it is a result of the sun rising or setting? Have you made any extensive terrain modification, such as introducing a forest or other potential source of lag?
Rollback Post to RevisionRollBack
My Grandmother passed away on Sunday, the 7th of August, 2011. I am taking an extended leave of absence in light of this. My apologies.
This sounds like it might be a problem that you're having with your location. Does this happen on multiple saves and or servers? Does it happen while standing still? How about time of day? Is it possible that it is a result of the sun rising or setting? Have you made any extensive terrain modification, such as introducing a forest or other potential source of lag?
This happens on every world I create... it didn't used to do this. I can't remember exactly when it started doing this but it's been a while and I've kinda just dealt with it. The FPS count skyrockets when I'm standing still, looking UP while chopping down wood from a tree (you know how you stand under the tree once you've chopped about 2 blocks, so you can chop the rest?) Happens at all times of the day, but sun rising and setting does seem to make it a little bit worse. No I haven't really made any big structures or any big operations, no forrests. The way I play I pretty much just start new worlds and play for about a week then trash that world and create a new one. I get frustrated with this lag issue having to constantly change my render distance :sad.gif:.
Turn on framerate limiting in your options. This should fix your problem, 'cause it sounds like your computer is too powerful, and tries to calculate unnecessarily huge amounts of frames for a visually simple game like Minecraft. You'll probably still get a little lag every once-in-a-while, but it'll be much less pronounced.
That's your problem right there; your computer is infected with the "Windows 7" virus. Sadly, this virus is immune to all known antivirus software, so the only way to get rid of it is to format your hard drive and install a version of Windows that doesn't blow chunks. I recommend XP Professional.
Rollback Post to RevisionRollBack
416 stone 296 stone slab (150 blocks) 149 stone stairs (228 blocks)
That's your problem right there; your computer is infected with the "Windows 7" virus. Sadly, this virus is immune to all known antivirus software, so the only way to get rid of it is to format your hard drive and install a version of Windows that doesn't blow chunks. I recommend XP Professional.
Rofl.
Mod edit: Please do not post if you don't have anything to add. One-word posts promote bad posting habit.
whats this? you installed 64 bit java at 4:30am? hmm...
-50 internets for lying
but yeah, the problem is due to memory limitations on 32 bit systems. Minecraft fills up the java heap, forcing the garbage collector to cycle constantly, which results in large amounts of lag after any particular render distance has been in use for a while. old, leftover chunks of used memory don't get freed until they get GC'd, and since the memory limit is smaller, things start fighting for space. Then you change the render distance and it re-renders the whole everything, and all [most] of the leftover chunks end up getting freed.
in its current ram-hoggy state, minecraft is rather poorly suited to run on 32 bit systems because of the low memory ceiling, and they typically need reasonably powerful dual or quad core processors in order to help distribute the extra load of GCing.
I have the same problem on my 32 bit laptop, which will run far/fancy fine for about 20 seconds, then slip gradually back down to unplayable.
Seems interesting though.
AngelCraft 64 Texture Pack v2.0.2 (Beta 1.8.1)
Nerd, geek, server admin, guy wearing a rainbow skin (with an office suit of epicness)? That's me.
-dotfortune
I'm using the client. Windows 7 64bit
5/19/13 Expect Us
This happens on every world I create... it didn't used to do this. I can't remember exactly when it started doing this but it's been a while and I've kinda just dealt with it. The FPS count skyrockets when I'm standing still, looking UP while chopping down wood from a tree (you know how you stand under the tree once you've chopped about 2 blocks, so you can chop the rest?) Happens at all times of the day, but sun rising and setting does seem to make it a little bit worse. No I haven't really made any big structures or any big operations, no forrests. The way I play I pretty much just start new worlds and play for about a week then trash that world and create a new one. I get frustrated with this lag issue having to constantly change my render distance :sad.gif:.
I always make sure to play on fast at all times. I don't think I've ever played on fancy.
Mod edit: Please use the edit button.
That's your problem right there; your computer is infected with the "Windows 7" virus. Sadly, this virus is immune to all known antivirus software, so the only way to get rid of it is to format your hard drive and install a version of Windows that doesn't blow chunks. I recommend XP Professional.
416 stone
296 stone slab (150 blocks)
149 stone stairs (228 blocks)
794 total stone
1082 blackstone
174 blackstone slab (87 blocks)
52 blackstone stairs (78 blocks)
1247 total blackstone
(not counting drawbridges and portcullises)
Rofl.
Mod edit: Please do not post if you don't have anything to add. One-word posts promote bad posting habit.
-50 internets for lying
but yeah, the problem is due to memory limitations on 32 bit systems. Minecraft fills up the java heap, forcing the garbage collector to cycle constantly, which results in large amounts of lag after any particular render distance has been in use for a while. old, leftover chunks of used memory don't get freed until they get GC'd, and since the memory limit is smaller, things start fighting for space. Then you change the render distance and it re-renders the whole everything, and all [most] of the leftover chunks end up getting freed.
in its current ram-hoggy state, minecraft is rather poorly suited to run on 32 bit systems because of the low memory ceiling, and they typically need reasonably powerful dual or quad core processors in order to help distribute the extra load of GCing.
I have the same problem on my 32 bit laptop, which will run far/fancy fine for about 20 seconds, then slip gradually back down to unplayable.
[FAQ] Extremely Common Problems
[OFFICIAL] Dragon Cave Thread