• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Poor FPS (HD5870 XFire)

Soldato
Joined
2 Dec 2009
Posts
4,018
Location
Midlands
Just fired up Left4Dead2 for some real eye-candy graphics only to be disappointed.

On a particular Multiplayer campaign (Dark Carnival), once the game loaded level 2 (dark, lights/shadow etc) the FPS seemed very low, laggy and stuttering.

My system is as follows:
i7 920 @ 3.2GHz (stable; stressed maximum temp is 62'C with Corsair H50)
12GB RAM
HD5870 x 2
Asus Rampage Extreme II
2 x SSD (game is on one, Win7 64bit the other)

I am running standard BIOS as shipped with the motherboard and my graphics drivers are standard off-cd drivers (since ive heard that recent drivers are very unstable).
Any ideas as to what the problem might be here? -just the graphics drivers or perhaps something else?

The GPU (only one has stats in CCC) gets to around 70'C after a game, so don't know it's load temperature.
 
Well, it did the same thing in Single Player...

... so I chose 'recommend settings'. End result was that it ramped every setting to maximum (whereas before it was a spread of max/middle), and the FPS issue disappeared - my FPS improved massively !?

My HD5870 in crossfire reached 85'C under load, fan speed was still at 20% too (automatic). CPU was 45'C.
 
Hmmm wired. Just one of them game bugs or glitch I guess?? Glad you got it sorted, but make sure you update thoes drivers tmorrow :D.

Up your fan speeds on ur cards btw, they are really picky with high temps.
 
Set your AA to 2 for some reason the Drivers / Game does not like high AA it makes mouse input it's rather annoying tbh.
 
sounds very much like a lag problem, perhaps there was a stutter in your net connection as they happen to me from time to time.
 
sounds very much like a lag problem, perhaps there was a stutter in your net connection as they happen to me from time to time.

Negatory - my system didn't like the game running at settings which were lower than 'Ultra'. I cannot really explain it, but that was what fixed it.
 
I had a similar experience with my GeForce 8500 GT in Ghost Recon Advanced Warfighter 2. I had it set to high settings and at 1024x768, but I wanted a better fps. So I set all to low, and to 800x600. Oddly, it seemed to be at a worse fps. So i changed it back.
 
Actually the problem has re-manifested itself.
Checking on the L4D2 forums, notably here (clicky) it talks about multi-GPU/SLI/XFires setups have FPS drop after the first level.

This is exactly my problem - level 1 on any campaign = 150+++FPS, level 2 onwards on any campaign = 1-30FPS.

Performance drop for people with Multicore ATI GPUs/SLI Nvidia and 64Bit OS.

Every time the map changes, performance for people with multicore ATI GPUs/Nvidia SLI GPU's and 64-bit OS's drop to unplayable levels

Possible fix : Alt-tab out of game, then back in (original post)
Possible fix 2 : This one is for Nvidia users. If you are running driver 195.xx, try downgrading to 191.07 WHQL. Note this does not mean it will be fixed, but is a possible temporary fix. Thanks to Beowulf_ .
Solved by valve : Unconfirmed.
 
reached 85'C under load, fan speed was still at 20% too (automatic).

What is it with these retarded automatic fan speeds on gfx cards? Companies helping to shorten the lifespan of your card so you buy another? Nvidia exactly the same. My old 8800GT used to hit over 100c with auto fan speed.
 
sounds like your clock settings actuly. had this problem with bfs.

Whats happening is your clocks are reverting to the 2d clock engine rather than the 3d when the game is playing.

This downclocks the gpu to around the 300mhz speed i belive.

This does not happen with the most recent driver ( 9.12 ) but does with all the older ones.

Minimising the game then re-maxamising is tricking the drivers into thinking a 3d app has just launched, hence ramping the clock settings back up to 3d settings
 
Back
Top Bottom