• Notice regarding image hosts and attachments. See here.

Metro 2033/Last Light Problems

Anyone having any problems with Metro LL?

Using two cards, the game was running perfectly (maxed out / locked to 60fps), but now it's just started running horrifically at around 10fps with ~20% usage on each card in what should be an area with very low gpu demands.
The benchmark runs fine, yet the game is buggered. Restarting the PC or game doesn't affect anything.

All other games run fine.

Is there possibly some hidden physx setting in an ini somewhere? Can't think of what else it could be at the moment...
 
Last edited:
Uncle Petey said:
Anyone having any problems with Metro LL?

Using two cards, the game was running perfectly (maxed out / locked to 60fps), but now it's just started running horrifically at around 10fps with ~20% usage on each card in what should be an area with very low gpu demands.
The benchmark runs fine, yet the game is buggered. Restarting the PC or game doesn't affect anything.

All other games run fine.

Is there possibly some hidden physx setting in an ini somewhere? Can't think of what else it could be at the moment...
Click to expand...

What mission are you playing?
And what cards are you using, in my first post it was recommended to download the seperate Physx drivers, which remedied all my fps drops.
 
Using a pair of 290's and the mission is 'Facility' I believe.
I'll have a go at the physx drivers fwiw, even though I don't use physx for obvious reasons :)
 
I don't know what the FPS was on my 280X, but it (LL) was playable on High settings at 1080p.

I did have to turn Advanced PhysX off, otherwise it stuttered and lurched.

I think I turned AA off also as jaggies don't bother me.
 
Well here's the thing, the game was running perfectly up to this point, so I don't see how it could be a settings related issue.

Look at the gpu usage. That's normally 97-100%:

W3g7UPE.webp
 
I run LL on high settings with a single 670 and see 50 - 60 FPS, so you should definitely be seeing better performance than this.

I just sold my 670 and got a 7970 so now I am concerned. Will test later...
 
I found that the benchmark was a worst case scenario, the game in general was less taxing. I found that the biggest performance killer was SSAA, but even so I played the game totally comfortably (avg 50fps, above 30fps 99% of the time) on a gtx 780, Max settings with SSAA 2x. Dropping SSAA altogether made the game way smoother, but there was a noticeable drop in image quality. Also, the tessellation performance is highly dependent on the scene. Where there are lots of characters, there is a heavy performance penalty.

In any case, this is a slow paced game, relatively low frame rates are tolerable.
 
Sorted!

Turns out that even though I had physx disabled in the menu, it was still enabled in the user cfg file for some reason :confused:
Figured it was something to do with phsyx as it looked just like what happens in Mirror's Edge when you have AMD with physx enabled and all the windows get shot out.

Now, with vsync:

N8BOBWn.webp
 
Ah, good find. The cfg file is also the only way you can defeat auto-aim when using a gamepad too. The auto-aim is really, really aggressive, and will move your screen all over the place, actually making it harder to hit things, not easier.

Feel sorry for console folks who have no option to turn of auto-aim at all.
 
You must log in or register to reply here.
Back
Top Bottom