HELP! 40-50 fps w/ r9 290 bf4?

Oct 8, 2013
714
0
10,990
So I am incredibly confused. I am recording using dxtory lossless lagarith codec, i am recording on a separate HDD 7200 rpm caviar black and the game is running on 1tb caviar blue. I have a 750w psu, 2x4gb ram, i5 4670k Z87-HD3.
I havent touched the bios since installing and bouilding the pc myself, infact i never edited anything.
I am recording @ 30 fps and my games fps drops all the way down to 40fps!? How is this happening! A r9 290 should be getting 80+ fps on ultra.
I have a benq 144hz monitor.
Can someone please help me, I''ve spent so much on this pc and its working like a pile of s**t!?
 
Solution
An i5 haswell at 4.5ghz is only good for around 60FPS minimums in BF4 MP on an AMD GPU in DX11 mode. ( http://pclab.pl/art55318-3.html ). Expecting 80FPS from your stock clocked i5 WHILE running a compute intensive encoder is unrealistic.

Dropping to 40FPS sounds almost exactly like what SHOULD be happening.

Should have gone E3/i7 for what you are trying to do here, hyper-threading would have been helpful in this application.

Try using Mantle, if you haven't already, that's probably the best bet here, as that will cut down on the compute overhead and possible free up some execution resources to get some better FPS. An nvidia card with NV's proprietary DX11 drivers would have been better suited to this application as well.
An i5 haswell at 4.5ghz is only good for around 60FPS minimums in BF4 MP on an AMD GPU in DX11 mode. ( http://pclab.pl/art55318-3.html ). Expecting 80FPS from your stock clocked i5 WHILE running a compute intensive encoder is unrealistic.

Dropping to 40FPS sounds almost exactly like what SHOULD be happening.

Should have gone E3/i7 for what you are trying to do here, hyper-threading would have been helpful in this application.

Try using Mantle, if you haven't already, that's probably the best bet here, as that will cut down on the compute overhead and possible free up some execution resources to get some better FPS. An nvidia card with NV's proprietary DX11 drivers would have been better suited to this application as well.
 
Solution