Aller au contenu

Photo

Mass Effect 2 FPS drop


  • Veuillez vous connecter pour répondre
18 réponses à ce sujet

#1
FL00D

FL00D
  • Members
  • 8 messages
Hello,

Mass Effect v1.01
Win7x64
Catalyst 10.2

msi 790FX-GD70
AMD Phenom II X4 965BE @3.7GHz
4GB Kingston HyperX 1600MHz
Sapphire HD 5870 1GB Vapour-X
WD: CaviarBlack 640GB
Corsair 750HX

Game Settings:
Everything maxed out, 16xAF, 8xAA (forced in CCC), 1440x900

I've been experiencing serious FPS drops in the game, particularly during conversations. FPS drops from constant 60 to 30, 20 or even 15 and then it crawls back up to 60. First, I thought it was because I forced AA in the graphics driver. After having "googled" a bit I found this: www.pcgameshardware.com/aid,703669/Mass-Effect-2-Galactic-battle-Geforce-versus-Radeon/Practice/ According to this article I should get around 64-92FPS even with 4xAA (I guess 4x instead of 8x would not make much difference). But instead, I get constant 60FPS with random drops... I have no clue what's wrong. I tried to disable Catalyst A.I. but that did not help. I'm pretty sure that with my config ME2 should run a lot better, even with AA applied.

All your answers are greatly appreciated!

Cheers,

PS.: Just one more thing: To enable AA in the game I didn't have to rename the exe etc., all I had to do was set AA to 8x in CCC.

Modifié par FL00D, 15 mars 2010 - 10:34 .


#2
Kronner

Kronner
  • Members
  • 6 249 messages
ME2 is locked at 60 FPS, you would have to edit .ini files to remove this cap (or maybe turning off vertical sync works too, did not try) and there seems to be a problem with the ATi Radeon 5870 series, quite a lot of people report some problems. Fix should come soon, probably from ATi.

Just a thought - try setting affinity for the Mass Effect 2 process to only one core and see if it helps..

#3
Guest_KeeLoGee_*

Guest_KeeLoGee_*
  • Guests
Have you tried the Mass Effect 2 hotfix that is posted on AMD's website? I would try that hotfix first and see if it helps. Otherwise, I'd probably try rolling back to Catalyst 9.12 (and maybe disabling AA).

#4
FL00D

FL00D
  • Members
  • 8 messages
Thanks a lot mate. Then, I might as well wait for a fix from ATi, again... :\\ I don't really want to turn off vsync cos that would mess motion blur up. How can I set affinity? I know there's an app for that but I thought that fixed only the "Normandy issue".

#5
FL00D

FL00D
  • Members
  • 8 messages

KeeLoGee wrote...

Have you tried the Mass Effect 2 hotfix that is posted on AMD's website? I would try that hotfix first and see if it helps. Otherwise, I'd probably try rolling back to Catalyst 9.12 (and maybe disabling AA).

Yes, I tried that one. Did not help at all. :( Anyway, as far as I know that hotfix is only for users with CFX.

#6
Kronner

Kronner
  • Members
  • 6 249 messages

FL00D wrote...

Thanks a lot mate. Then, I might as well wait for a fix from ATi, again... :\\\\ I don't really want to turn off vsync cos that would mess motion blur up. How can I set affinity? I know there's an app for that but I thought that fixed only the "Normandy issue".


CTRL+ALT+DEL


Processes - MassEffec2.exe, right click, affinity, tick only one core
but this is a longshot, the problem is most probably in the graphic card

#7
FL00D

FL00D
  • Members
  • 8 messages

Kronner wrote...

FL00D wrote...

Thanks a lot mate. Then, I might as well wait for a fix from ATi, again... :\\\\\\\\\\\\\\\\ I don't really want to turn off vsync cos that would mess motion blur up. How can I set affinity? I know there's an app for that but I thought that fixed only the "Normandy issue".


CTRL+ALT+DEL


Processes - MassEffec2.exe, right click, affinity, tick only one core
but this is a longshot, the problem is most probably in the graphic card

Just tried this. Unfortunately it did not help at all. :( Even more vexing is that I cannot find anyone with the same issue. The game is supposed to run like hell on my cfg. That's so bloody annoying... Catalyst 10.3 promises performance increases in several games but Mass Effect 2 is not on the list. :( I really don't know what to do/expect. I'd be so glad if someone with a similar cfg could confirm that they have similar issues.

Modifié par FL00D, 16 mars 2010 - 10:12 .


#8
MessAffect2

MessAffect2
  • Members
  • 7 messages
I don't have a similar config (I have a CD2 T8300 2,4 ghz + 8600M GT Win x64) but I have noticed (and reported to EA) a drop of FPS during conversations. Falling from a little above 30 fps to 20 or 15 fps. It seems to me, they wanted to display too many details (compared to normal game sequences) during conversations.

#9
Guest_KeeLoGee_*

Guest_KeeLoGee_*
  • Guests
Looking at your specs again, I would probably try setting your CPU clock speed back to stock. Sometimes overclocking can be a bit of an issue (actually most of the games are built around the "low CPU, high GPU" config).

#10
FL00D

FL00D
  • Members
  • 8 messages

KeeLoGee wrote...

Looking at your specs again, I would probably try setting your CPU clock speed back to stock. Sometimes overclocking can be a bit of an issue (actually most of the games are built around the "low CPU, high GPU" config).

Well yeah I've been also thinking about setting the CPU clock speed back to stock.

Thank you guys for responding! :)

#11
Guest_NewMessageN00b_*

Guest_NewMessageN00b_*
  • Guests
I pale before the craziness of this gaming setup.

Conversations, eh? What about going through volumetrics (i.e. smoke)? If you experience the same issue ther, try lowering AF to lowest, just for the sake of a test.

And you're saying that turning off vsync messes up the game? I smell a hardware issue. Although a distant one. And that might get fixed by some future driver.

#12
FL00D

FL00D
  • Members
  • 8 messages

NewMessageN00b wrote...

I pale before the craziness of this gaming setup.
Conversations, eh? What about going through volumetrics (i.e. smoke)? If you experience the same issue ther, try lowering AF to lowest, just for the sake of a test.
And you're saying that turning off vsync messes up the game? I smell a hardware issue. Although a distant one. And that might get fixed by some future driver.

Going through smoke: still 60FPS (e.g. at the very beginning of the game). I did not mean that I had actually tried to turn vsync off. :) I was told that turning vsync off would cause motion blur not to work properly.

#13
MaaZeus

MaaZeus
  • Members
  • 1 851 messages

KeeLoGee wrote...

Looking at your specs again, I would probably try setting your CPU clock speed back to stock. Sometimes overclocking can be a bit of an issue (actually most of the games are built around the "low CPU, high GPU" config).


If you do overclocking properly, it doesnt make sense why it would slow down when infact your CPU is working faster than before? And apparently ME2, and all UE3 engine games in general, are actually quite CPU dependant if I understood correctly.



Just for kicks, experiment with dropping down Number Of Cinematic Lights in ME2 Config Utility. Latter is known to cause major perfomance crashes when combined with AntiAliasing, (Unreal Engine doesnt handle AA well anyway) especially during conversations.

#14
Cortyman

Cortyman
  • Members
  • 192 messages
I actually also have the same problem but only with a few conversation pieces, notably on Miranda's loyalty mission when she is talking to her friend at the end it drops to 15 FPS. I also have the 5870 graphics card.

#15
MaaZeus

MaaZeus
  • Members
  • 1 851 messages

FL00D wrote...

NewMessageN00b wrote...

I pale before the craziness of this gaming setup.
Conversations, eh? What about going through volumetrics (i.e. smoke)? If you experience the same issue ther, try lowering AF to lowest, just for the sake of a test.
And you're saying that turning off vsync messes up the game? I smell a hardware issue. Although a distant one. And that might get fixed by some future driver.

Going through smoke: still 60FPS (e.g. at the very beginning of the game). I did not mean that I had actually tried to turn vsync off. :) I was told that turning vsync off would cause motion blur not to work properly.



Why would Vsync mess with motionblur that is post processing effect? They are not related at all. Vsync is a thing that keeps your monitors and GPUs frames on synch. Disabling VSync only makes your GPU and monitor go out of synch here and there and this shows as horizontal tearing effect.

Downside of VSync is that if your FPS ever drops below what it should be, like below 60FPS in case of ME2, it automatically HALVES your FPS to 30Fps. This might be what you are experiencing. Your rig is unable to keep 60FPS up here and there and it automatically drops down to 30FPS.

Now, there is a nifty thing called Triple Buffering. With this enabled instead of halving your FPS it splits the available FPS rates to thirds IIRC, in case of 60FPS and 30FPS you get 60, 40 and 20. Or perhaps it was on one fourths. Dont remember. However, in ATI drivers you can only force triple buffering on OpenGL, and have to use 3rd party program to force it on Direct3d, like D3DOverrider that comes with Rivatuner.
Downside of triplebuffering is that it adds some input lag. Stil, try it. Will make FPS drops less annoying.

Modifié par MaaZeus, 16 mars 2010 - 11:31 .


#16
FL00D

FL00D
  • Members
  • 8 messages

MaaZeus wrote...

KeeLoGee wrote...

Looking at your specs again, I would probably try setting your CPU clock speed back to stock. Sometimes overclocking can be a bit of an issue (actually most of the games are built around the "low CPU, high GPU" config).


If you do overclocking properly, it doesnt make sense why it would slow down when infact your CPU is working faster than before? And apparently ME2, and all UE3 engine games in general, are actually quite CPU dependant if I understood correctly.



Just for kicks, experiment with dropping down Number Of Cinematic Lights in ME2 Config Utility. Latter is known to cause major perfomance crashes when combined with AntiAliasing, (Unreal Engine doesnt handle AA well anyway) especially during conversations.

I see. So I'll either have to turn AA off or decrease the number of cinematic lights. *sigh*

#17
FL00D

FL00D
  • Members
  • 8 messages
Finally I managed to edit the coalesced.ini file and turn vsync off. Indeed, that seems to have fixed the issue! :) http://www.giantbomb...me-2/35-385239/ according to a guy on that forum, motion blur depends on vsync. Hence turning vsync off may mess up motion blur. So that's rubbish?


#18
BeresaadSoldier

BeresaadSoldier
  • Members
  • 169 messages
Grab Rivatuner, install it, go to Tools, open D3DOverrider, run it while playing the game with Force Tripple Buffering and Force Vsync on and voila, you have the best of both worlds - no screen tearing and wonderful motion blur. Hope that helps.

#19
MaaZeus

MaaZeus
  • Members
  • 1 851 messages

FL00D wrote...

Finally I managed to edit the coalesced.ini file and turn vsync off. Indeed, that seems to have fixed the issue! :) http://www.giantbomb...me-2/35-385239/ according to a guy on that forum, motion blur depends on vsync. Hence turning vsync off may mess up motion blur. So that's rubbish?



Heh, I have no idea what the deal is with vsync and motionblur. They really have nothing to do with each other.
Moionblur is done in the GPU where Vsync times framebuffers.