R9 390 + fx 6300 Low Frame rate MSGS : V Phantom Pain

Juan5151

Commendable
Mar 14, 2016
8
0
1,510
Hey guys, I was recently loading up the newest Metal Gear game and noticed that I'm getting tanked in the frame rate department. I'm getting 60 fps in close quarters and hallways but as soon as I look towards the open world I get frames going down to the mid 30's. Other games such as BF4 have also gotten low FPS compared to other peoples benchmarks ( Mine being 40-60 while others are blowing past the 60 FPS cap)

My specs are

Gigabyte r9 390 8 GB
AMD FX(tm)-6300 Six-Core Processor @ 4.4 Ghz
10 GB DDR 3 Ram
WIndows 10

If anyone could give me some guidance that would be excellent! Thanks guys
 


Im currently running amd's 16.5 drivers so I believe I'm as up to date as I can be
 
I7 3770k @4.6GHz, 60Hz 1080p, gtx970, maxed graphics, 2k DSR and I get consistent 55-60fps. That's at 54% cpu and 99% gpu loads. Your issue is the game settings. Lowering things like shadows, detail view distance etc will put less stress on the cpu. Lowering Mxaa, fxaa, AA etc will help too
 


I actually saw that my gpu usage was fluctuating madly. Sometimes 100 sometimes 34 or even sometimes around 3%

Definitely not consistent
 
Which means lower some of the more cpu dependant settings like shadows, AA, viewing distance etc.

And it was meant to be 3k DSR, 2970x1680, not the full 4k, that's a little beyond the capability of the gtx970 on that game, you'd need a gtx980 or 980ti for that.
 
^I know 4k is too much for the 979, I was just querying the 2k dsr comment, I understand now.

I could be very wrong for that game, bur I have never seen cpu isage depend on shadows and AA. These are classic gpu heavy factors and even if they do drop cpu usage slightly, they will significantly drop gpu usage thus putting more onus in the cpu. UNLESS this game is radically different.
 
Every setting, as is, is majority gpu bound, that's a given. However, some settings have a greater degree of cpu usage due to lack of directX input. Shadows especially are affected, not in the sense of actual cleanliness of lines or opacity, but in the way the game interacts with them. Grass is another big cpu hit. The gpu will deal with the level of detail in what's visible, and what's blurry, but it's the cpu that'll determine the sheer numbers of individual blades. Cutting down viewing distance increases the size of the blurred or clouded section, so the cpu only has to account for the smaller number of actual blades left visible. AMD is in worse shape than nvidia with this as any physX details like wild moving grass are dealt with by the cpu as physX is proprietary to nvidia whose gpu handles that aspect. This further adds to the cpu stress.

That's primarily why a 390 is a little overpowering for an fx 6300. The 390 is capable of huge amounts of details and most owners tend to push the maximum amount of details possible thinking 'it's a 390, it'll handle it', not realizing there's also a corresponding amount of raised cpu usage that goes along with the higher settings and fps demands