I think I'm going to have to call 1.8 unplayable. I'm generally running at 2 fps with 0 chunks loading. Changing my render distance doesn't even help - I still get that poor performance at the 2 chunk render setting. I've spent the last 3 hrs experimenting with all the new settings and nothing helps. Occasionally, I'll get a momentary spike of 20+fps, but it only lasts less than a second. I got killed by a spider because I froze in place while the spider was able to attack me unaffected by the freezing. xD In the snapshots, I was able to do stuff as long as I was underground, but that's not even helping today. Also, terrible block lag, I tend to have to break blocks 2-3 times before they're actually broken.
I have experienced a major drop in fps. With default settings I get on average 1-15 fps with giant lag spikes that make the game unplayable in single player. I managed to get my fps up to on average 30-40 fps by altering my settings.
For those who are having problems here's a list of what helped for me:
Launched Visibility - Close launched when game starts (this helped majorly!)
Increased my memory up to 2GB (JVM Arguments: -Xmx2048M -Xms2048M)
Reduced Render Distance to 10 Chunks
Set Particles to Minimal
Turned Clouds Off
Turned VSync Off
Turned Use VBOs Off
Turned 3D Anaglyph Off
Set Max Framerate to Unlimited
Turned Allow Snooper Off
This problem has gotten progressively worse for the last couple of updates and 1.8 became unplayable for me on default settings until I made these changes.
This is 14w29b - when threaded chunk loading was introduced:
Look at the GPU usage percent - this is how it is supposed to be.
Aside from the weird spike in FPS look at how smooth the graph is! The world plays very smooth - like a hot knife going through butter!
Compare again to the 1.8 release:
GPU usage is very low.
Of course Mojang knows all the kids will like to brag "I GHOT 183405 FPS IN TEH MYNEKHRAT NOW!11!!!!!" so it almost seems they rigged something to make it seem the frame rate is high.
I told all of you - FPS DOESN'T MATTER - what matters is the CONSISTENCY of FPS because that affects your perception of how "smooth" the game plays for you.
As an aside look at this screenshot of 14w29b:
Almost 300 chunks updating and it still runs smooth.
This was the best snapshot of all.
What the hell happened between then and now? It has to be the crappy lighting engine update.
You're only showing the GPU performance, while Minecraft relies a lot on the CPU as well. Could you show us CPU charts as well?
Even though I am not affected by these problems, I want to know more about them, and find out what exactly causes them. Then we might be able to provide Mojang with enough information to fix it, or to mod a fix into the game ourselves if that doesn't happen.
From those charts showing that GPU usage is lower in 1.8, I think that was Mojang's intention. Demanding less of the GPU means better performance on GPUs with poor performance. Also, if you look at those frame rates, they're consistently higher, with the occasional spike. In the 1,7 graph, the measurements were all over the place, high, low, spiking ridiculously. Mojang's main goal with this update was to increase performance and efficiency, which they indeed accomplished according to those graphs.
Making the game more efficient means it performs better on low performance equipment and demands less of required systems. This is what Mojang wanted to do, and I think they have.
Also, CPU performance does indeed matter, especially to those with lower performance CPUs and integrated graphics. Minecraft is very GPU and CPU intensive, and when the processing has to be carried out by the same device things can get very slow very quickly. With my AMD dual-core 2.4 GHz processor I consistently hit 100% while playing Minecraft. Actually, it's at 100% most of the time when playing the game.
I'm not trying to defend Mojang and start a big fight. I'm just saying that they accomplished much of what they said they'd do. The FPS drops on some machines probably has to do with hardware and software conflicts that weren't present before, since they basically rewrote the entire game. They will be worked out in time. However, I do agree that the chunk loading issue does absolutely need to be fixed and they should have definitely fixed it before releasing the update. It seems to be a universal issue, no matter the equipment.
I also noticed in places where there are large underground ravines the frame rates and lag become really horrible in the immediate area - it's almost like a cheat to know there is a large hole a few blocks underneath the ground. The absolutely worst thing to do is stand there and turn and look in all directions.
I haven't noticed any issues related to this; in particular, I just modded* the cave generator class to produce several times as many caves as usual (the same number present before 1.7 reduced them) and other than taking a few more seconds to generate a new world (which isn't saying much when it already took over half a minute) there were no issues.
Also, I saw quite a few black spots around lava pools when looking around underground, so the lighting changes mentioned in later posts haven't fixed that issue; indeed, they always say it has been fixed in every release (no mention in the update notes in the launcher though).
*Yes, I actually modded 1.8 to make up for their gross incompetence in not allowing customizable cave (and other structures; see Superflat) generation in the customized world type, only an on/off setting:
Same cave in 1.8, note the different ores and lack of mineshafts (another thing nerfed in 1.7, but generating the same if the chance parameter is adjusted, haven't changed it yet):
When I use VBOs it does well increase my FPS, BUT it introduces lag spikes. The spikes get worse and worse until i turn off VBOs. I don't understand this. I used VBOs in a previous snapshot and i never got anything like this.
Well, the lagg has to come from somewhere, and I see your CPU is pretty much maxed-out. This can mean 2 things:
1) Minecraft is using the CPU to it's full potential (with the added multithreading), or
2) The CPU can't handle everything Minecraft does.
I'm guessing that this may actually be the cause of the problem, especially since the GPU useage is quite low. This again can have multiple causes. The first one is that the CPU is bad, but since previous versions ran at a much better speed, this is unlickely. This must mean that for some reason, Minecraft is updating way more things than it should do. You can try setting the difficulty to peacefull and executing the command '/kill @e[type=!Player]' to get rid of entities (warning: this will also delete stuff like minekarts), and if this improves performance, you know that Minecraft is for some reason spawning to many entities.
But I don't think the entities will be the problem, since they don't rely a lot on the hardware and therefore they should react the same on all computers, yet only some people experience the slowdown. So let's look at what else can cause a big load on the CPU, especially when moving.
First and most obvious, there's generating chunks: people have also reported starting worlds being slow. And in earlier versions, that was all done on a single thread, which should make it react exactely the same on all hardware capable of running java. However, in 1.8, they made the chunk generation threaded, which basically means multiple of them can be generated at once. This should give a speedup, but there will also be an overhead, both of the inner workings of the threading system as how threads sometimes have to wait to avoid conflicts. The latter should again react pretty much the same on all hardware. The former however depends on how the computer handles multitasking/threading, which will depend mostly on the processor and the operating system. To improve the performance of this a bit, you can try to close all other programs (even the ones running in the background that aren't really needed, though don't end processes of which you don't know what they do, that can make your computer very unstable). To have more information about this part, can everyone please post weather they have decreased performance in 1.8 or not, together with their operating system and CPU? (to see if there are similarities between the hardware and OS of people who have problems and people who don't have problems.
The slightly less obvious CPU-intensive process is the one that generates the world mesh. (Since graphics cards can't render voxel-worlds directly (yet?), it has to be converted to a collection of points and triangles, called a 'mesh') So, this basically just goes trough all blocks of a chunk (actually, in a 'cubic' 16x16x16 'chunk') and creates a triangularized version of it whenever a (16x16x16 part of a) chunk gets generated or is changed (a block is placed or broben). This should again be the same on all hardware, or at least it was like that in previous versions. In 1.8 there's the added feature called the "advanced cave culling algorithm", which basically checks if the 16x16x16 parts of chunks are visible or not and rejects them when there not visible, reducing the GPU load. However, if you have any experience with creating 3D graphics yourself, you'll be familliar with a phenomen called 'Z-fighting'. It's not entirely relevant, but it illustrates a possible problem well: a computer doesn't have perfect accuracy, and therefore when it has to see if something is visible or not visible while it's right at the edge, then it can happen that it kinda glitches between being visible and invisible. In Z-fighting, this happens with pixels, but it could possibly happen with the chunk parts in Minecraft as well, and if Minecraft regenerates them every time they become visible (I don't know if this really happens), then it'll be regenerated every few frames. If this is the issue that's slowing down Minecraft for you, try to decrease the view distance.
Off course, almost all of this is mostly speculation, and especially of the 2nd program I'm not entirely sure of if Minecraft 1.8 handles everything in those was. For that I'd have to decompile Minecraft and find out how the obfuscated code works.
Anyway, sorry for the long post, but I think I'm getting closer to finding the cause. And for those willing to give me their specs to see if there are simularities between those having problems and those not having problems: please follow approximately this format:
I don't suffer from a bad performance in Minecraft 1.8.
CPU: dual-core i5 @ 2.6GHz, OS: Linux (Ununtu 14.04 LTS)
Before 1.8, I capped my maximum FPS at 50 or 60, and my game ran totally fine.
When I started up the game today, the first thing that hit me was that my frames dropped all the way to 2 FPS while running around, even just walking for a few steps. I set my maximum FPS to unlimited and saw that it rose all the way to the 300s while standing still. Even going to the default texture pack and dropping all of my graphics barely did anything to help performance while running, maybe staying around 10 frames per second. This issue forced me to stay in 1.7.10 where I can get a constant 30-40 fps at all times. That basically sums up my situation.
Rollback Post to RevisionRollBack
"You tried mercenary work? It might suit you."
"On a scale of one mile to Lord of the Rings, how far did you walk today?"
I have to set the render distance to 2 in order to get an fps above 20.
Rollback Post to RevisionRollBack
Lois: Together we can do anything: face any foe, overcome any obstacle.
Peter: Yeah, climb any mountain, rent any video, dial any phone. And not just our phone, Lois, other people's phones. Decent phones, God-fearing phones, phones that everybody else gave up on, but we knew better because we were a team!
Brian: What the hell are you talking about?
although my mac is not too good,in 1.7 i usually get about 24-30 fps (which for me is perfectly playable) then in 1.8 i get 0-10 fps. and with this kind of fps (both on render distance 5), don't even try playing recourse intensive maps (i wouldn't be surprised if i got negative fps O_o)
I am also experiencing what others are describing. I play on my own Realm, I have never experienced lag and never really paid attention to my fps as it was not necessary. Since this mornings update It is more or less unplayable. 60fps when standing still or looking around , quickly dropping upon walking or running to somewhere between 5 tom 16 fps.