Low fps in Call of Duty Advanced Warfare

Timdog · 12 Jan 2015 at 10:40

I'm finding while playing my fps occasionally drops from 50+ fps to 1 or 0 fps running at 1080p. It's very intermittent and doesn't happen that often but it normally runs at decent fps. I have the texture details set to v.high and super sampling is off and that's all I can really remember from the video settings.

My system is:
Core i5 4670k @ 4.2GHz (Stable)
AMD R9 285 @ 1010/1500MHz (Also stable)
8 gig ram @ 1600 MHz
500w OCZ psu

I had thought it was my psu may be a bit on the low side but all other games (i.e. ARMA 3 on Ultra) run just fine.

Apart from the fact it's probably just a horrible console port is there any reason why this would be happening?

KingDazza · 12 Jan 2015 at 11:47

Hi,

Not sure about your specific problem. But for me it runs far better and smoother in windowed borderless mode, rather than fullscreen. Not sure if you've tried that yet.

Timdog · 12 Jan 2015 at 13:13

KingDazza said:
Hi,

Not sure about your specific problem. But for me it runs far better and smoother in windowed borderless mode, rather than fullscreen. Not sure if you've tried that yet.

I haven't no, I'll give that a blast when I get home! Thanks.

Chisharpe · 12 Jan 2015 at 16:12

borerless+ 1 here. think it uses windows own Vsync and that helps.

postmanfw · 12 Jan 2015 at 17:03

What drivers are you using?

Runs at 90 FPS constant on mine at 1440p and your 285 beats my 6970 xfire setup.
Certain settings for the graphics in game make a huge difference to performance but very little visual difference.
Really need to list what you have them all set at to know.

Run afterburner to monitor card usage and temps. That will show you if its the card getting too hot and throttling or if the gpu is being maxed out on certain maps.

It can be setup to give an on screen display of usage details so you can see whats going on as it happens.

Some maps are quite a bit more gpu demanding than others even though you wouldn't expect them to be.

Timdog · 13 Jan 2015 at 21:12

I think I found the problem, in the config it was only using 70% of the gpu memory which is only 2GB to begin with and as I had it on very high it was probably running out of vram.

\Call of Duty Advanced Warfare\players2\config.cfg

Mine was set to this.
seta r_videoMemoryScale "0.7"

So I changed it to
seta r_videoMemoryScale "1"

If you go into the video options in game it wil tell you how much video memory it has detected, mine was around 1400 but now shows 2023 as it should!

Now runs with no issues!

postmanfw · 13 Jan 2015 at 21:58

Nice one

Default setting for mine is 0.85 so going to try changing it to 1 also

you can also set game to high priority in there too...helped in bo2

seta r_elevatedPriority "1"

and also max ping for searching

seta cl_maxPing "300"

default is 800!!! i tried lower settings previously but took ages to find a game.

Also make that file read only so it cant get changed via any updates

another one is in the keys_mp file

change so that you just press tab for scores and it goes on release rather than having to push again for off

bind TAB "+scores"

Timdog · 15 Jan 2015 at 11:07

postmanfw said:
Nice one

Default setting for mine is 0.85 so going to try changing it to 1 also

you can also set game to high priority in there too...helped in bo2

seta r_elevatedPriority "1"

and also max ping for searching

seta cl_maxPing "300"

default is 800!!! i tried lower settings previously but took ages to find a game.

Also make that file read only so it cant get changed via any updates

another one is in the keys_mp file

change so that you just press tab for scores and it goes on release rather than having to push again for off

bind TAB "+scores"

While this helped me it actually didn't completely fix it, now my FPS was just dropping to into the 20s occasionally!

I turned vsync off and my fps was normally 120+ fps which confused me greatly so I opened afterburner on a second screen and noticed my core clock wasn't steady and when my fps dropped it was going down.

After a bit more searching around this morning it turns out I probably need to turn off the ultra low power saving mode and this will hopefully fix everything!