Massive FPS drop due to new graphics engine (assuming new since it now has antialiasing).
See attached Screen Shots. FPS goes from 67 in 13w37b to 6 in 13w38a. And actually make my client unplayable... Will revert back to 13w37b until I can get to my good PC and see if the issue is still present.
Unfortunately turning Antialiasing, Mipmaping, and Post Processing off, does not fix this issue
NOTE: I'm sure this is a duplicate by now of something but due to it being the new engine I figured it may stay on its own.
Linked issues
is duplicated by 6
Attachments
Comments 45
If you disable the shader (restart your client) does the fps return to normal?
What shader? And why would it be on by default?
I see the shader but where is that accessed from I'm not seeing it in the video options. I don't play with mods so this shader is minecraft vanilla (snapshot) related.
Shaders are enabled when pressing the "super secret settings" button. You can see it listed as activated in the debug menu (shaders minecraft:shaders/post/fxaa.json). These should not be enabled by default.
I shut the shaders off and there's no change... see new screen shot (2013-09-20_07.51.10.png)
Noting: When I hit play in the console and the Mojang screen comes up, its blurry and pixelated... don't know if thats related to this as its not in the previous snapshot
Does this occur when using the default textures?
It does... but if I quit to menu and go back into my world FPS goes back to normal... wondering if there's something getting hung up in the renderer or the engine on initial startup of Minecraft.
same over here
Same problem 😞
the problem is, it sitll occurs when I turn off anti aliasing and mipmaping and all the other new stuff.
And for some reason I now have fps drops in 13w37 as well. Which worked fine before.
Another thing to note: when I start minecraft, everything works fine. But the longer I play it, the more fps drops I get.
I found something that might has to do something with this bug, when I hit F3 and watch the used memory in the top right corner it starts at around 100MB and it is counting upwards. After a few seconds it gets set back to around 100MB. however, after a while the amount of times it gets set back to a lower number become less and the amount it gets set back to is higher. So after a while it is 1500MB and counting and it gets set back to 500MB
seems to be fixed in 13w39a everything works way smoother
I seem to still be getting this problem in the new snapshot (MC-31916)
New snapshot don't fix this bug... 😞
Can confirm.. I'm still getting this FPS issue. Again loading the world, quiting to menu and reloading the world seems to fix the problem which doesn't make sense, unless there is a start up opteration getting hung up somewhere and when I quite back to the main menu, it clears it.
ok it's back now for some reason. And it doesn't happen in a normally generated world. but when I use flatlands whit just air it does. I don't think it has anything to do with anti aliasing because I have that turned off.
Gone for me in this version. Don't know if maybe it's something secondary causing it now.
hmm interesting, so it's either you or me...
-I just installed java and used the -Xms4G Xmx4G parameters (advice from [MC-16791]) but I'm still having memory lag after leaving minecraft on for a few minutes without doing anything it said it was using 2000MB ram. This is a really annoying bug but it's hard to find the actual issue here because this issue is probably about anti aliasing whereas mine is more about a memory leak any advice?
ok never mind, I just realized MC-11834 this is my problem
New snapshot 13w41b don't fix this bug... 😞
I'm having huge FPS(dipping to 1-2 FPS...rarely getting above 10 FPS) problems with 13w41b as well. I have an Intel HD2000 chipset and wondered if the "fix" for the Intel chipsets had been broken. Even 1.6.4 is running badly. I can launch 1.5.2 with the old .exe and it seems to run fine. 20-25FPS.
Still not resolved in 13w42a. Game now unplayable.
Confirmed as still present in 13w42b. This needs to be resolved.
Issue Never came back for me, even in this update... What PC specs does everyone have... it may be related
I have dual AMD HD 6750 running Java 7.40 for 64 bit OP with 16GB ram on Windows 8 with 6 Core 3.30GHz processor
My computer specs have not changed between the last version that did not have the FPS drop and the 4 latest snapshots where the FPS drop occurs. I have, however, updated Java and my video card drivers to the latest available versions. In the 4 latest snapshots, still have massive FPS drop to where the game is unplayable. If I go back to 13w39b, the FPS drop is not there.
Perhaps a setting in my video card software needs changed, but I don't know which one could be the culprit.
I also want to mention that I have minecraft set to use 3G of RAM, should I add the same parameters to JAVA itself?
edit: adding the parameters to JAVA did nothing to alleviate the issue either.
I was asking for computer specs as we've already found that having your graphics card for Force AntiAliasing now that minecraft has it in program, messes with some graphical things. and I'm sure they've been tweaking the in game anti-aliasing between snapshots that it could have caused this issue.
See if yours is turnned on to force it and if it is, turn it off and see if that does anything.
It may be unlrelated but it doesn't hurt to check
In my graphics card settings I have anti-aliasing set to be application managed. I've also tried 2x and 4x anti-ailasing and neither of those options make any difference either. I also have anisotropic filtering to be application managed as well. Haven't tried any of the other settings on that.
Thanks for the help so far. It's much appreciated. If it helps, I am using ATI Raedon HD 3200 Graphics.
@all having this issue:
Please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report ([minecraft|http://hopper.minecraft.net/help/finding-minecraft-data-folder]/crash-reports/crash-<DATE>-client.txt) here.
Here's the forced crash using 13w42b
@Bill Robertson
OpenGL: ATI Radeon HD 3200 Graphics GL version 3.3.11672 Compatibility Profile Context, ATI Technologies Inc.
Update to Catalyst 13.9 http://support.amd.com/en-us/download/desktop/legacy?product=legacy2&os=Windows%207%20-%2064 and report if the FPS issue is still there. If so, please attach a new forced crash report.
Problem persists after updating to Catalyst 13.9 so here's the new debug crash report.
Thanks
Hm, the driver signature did not update:
OpenGL: ATI Radeon HD 3200 Graphics GL version 3.3.11672 Compatibility Profile Context, ATI Technologies Inc.
Sure that the driver did correctly install ? (ATI was replaced by AMD years ago)
Current signature (for my graphics card) is:
OpenGL: AMD Radeon HD 6700 Series GL version 4.3.12443 Compatibility Profile Context 13.200.11.0, ATI Technologies Inc.
Ah, something must have gone wrong when updating, then. Didn't notice it wasn't changed. Trying again.
Looks like the driver signature is not updating even after an uninstall of all AMD related files (using their clean install tool) and reinstall of Catalyst 13.9. In device manager, the driver is listed as 8.970.100.1100 provided by Advanced Micro Devices, Inc with a date of 4-29-2013
Looks like my report(MC-36105) was classified a duplicate of this one, but I'm not sure that it is the same problem as this one.
What I can report is that with Intel Integrated graphics(HD2000 in my case), Full screen mode now causes terrible performance(unplayable 3-10FPS). When you hit F11 to go to "Windowed" mode, the performance comes back and is playable(20-24 FPS). Even when maximized, the performance is much better than what Full screen mode does.
I do not see this problem on my Geforce GTX 550Ti machine. Performance is the same(50-75FPS) for both "Windowed" and "Fullscreen". More details in my bug report if needed along with machine specs.
Some progress made, I am now able to get consistently 4FPS instead of 0-3. Max I've been able to hit is 6. When paused, FPS goes up to my normal amount.
Confirming that this bug is still present in 13w43a
FPS issue still present in the 1.7 prerelease. Attached new forced crash report.
Java version is the latest (just updated yesterday) Video card driver is the latest available.
Last playable version of the game (in my case at least) was 13w39b.
Please advise
Really hope someone can help on this issue. I first reported it and am no longer having the issue as of a few snapshots back now.
Edit: If anyone else is having this issue, please post your specs and forced crash report so we can get information that Mojang can use to trouble shoot this
Just for clarification, since this report is talking about Anti-aliasing, are those who have this issue referring specifically fpd drops while anti-aliasing is on (via shaders), or just in general?
For me it was only when Anti-aliasing was on. It now no longer affects me whether its on or off. I'm assuming its anti-alaising for the others since they haven't stated otherwise.
Minecraft doesn't antialias anything. We also didn't get a 'new engine' since 1.6. We did however request FBO support from your videocard and if it claims to support it we're using it.
We'll be continue using this from this moment. So if for some reason your videocard is either lying about supporting it, supporting it in software (slow) or just doing it really slow after claiming support, you might want to consider upgrading to a more recent videocard/drivers.
Thanks Grum... good to know. So it is requesting the support from the card. When I updated my drivers the antialiase issue went away which makes sense now. Hope everyone is finding this useful
Grum, could you please clarify what you mean. I'm not very tech savvy when it comes to video cards and what FBO means. Just because this isn't happening to other people doesn't mean that the issue is invalid. This is an unacceptable resolution to this issue. I don't believe that my issue pertains to any kind of anti-aliasing by either the videocard or by the game, but this is where one of the mods moved my original report (which can be found here https://mojang.atlassian.net/browse/MC-35664). 13w39b worked as normal and every snapshot since then and the current pre-release of 1.7 has had this issue. Upgrading video card is not an option on this laptop.
Erik Broes
You have a shader enabled, which it says on the menu