Hello.
I recently built a new gaming rig and have been playing with it for little over a week. Running everything at Very High with DX11 I usually hold a steady 60 FPS, but go no higher, with minor drops if I quickly pan to a long distance before returning to 60 FPS.
This can all change however if there is steam/exhaust on the map. What I mean is mechs getting close to overheating release steam at these visual settings, and it cuts down my FPS to near 30 or sometimes lower.
I have v-sync and PostAA enabled as well. I am wondering why this is occurring with something as simple as steam, and if there is anyone else who has dealt with this before and found a way to fix it?
Details of rig:
i5-4570 3.2 ghz
Powercolor Radeon R9 280X OC edition
8 gigs ram
ASUS Z87M-PLUS mobo
Samsung SSD


Stuck At 60 Fps Unless There Is Steam?
Started by HBizzle, May 19 2014 10:11 PM
4 replies to this topic
#1
Posted 19 May 2014 - 10:11 PM
#2
Posted 19 May 2014 - 10:20 PM
Teh Particles Slider is a trap!
Always set it to Medium … Or less.

#3
Posted 20 May 2014 - 01:55 AM
HBizzle, on 19 May 2014 - 10:11 PM, said:
Hello.
I recently built a new gaming rig and have been playing with it for little over a week. Running everything at Very High with DX11 I usually hold a steady 60 FPS, but go no higher, with minor drops if I quickly pan to a long distance before returning to 60 FPS.
This can all change however if there is steam/exhaust on the map. What I mean is mechs getting close to overheating release steam at these visual settings, and it cuts down my FPS to near 30 or sometimes lower.
I have v-sync and PostAA enabled as well. I am wondering why this is occurring with something as simple as steam, and if there is anyone else who has dealt with this before and found a way to fix it?
Details of rig:
i5-4570 3.2 ghz
Powercolor Radeon R9 280X OC edition
8 gigs ram
ASUS Z87M-PLUS mobo
Samsung SSD
I recently built a new gaming rig and have been playing with it for little over a week. Running everything at Very High with DX11 I usually hold a steady 60 FPS, but go no higher, with minor drops if I quickly pan to a long distance before returning to 60 FPS.
This can all change however if there is steam/exhaust on the map. What I mean is mechs getting close to overheating release steam at these visual settings, and it cuts down my FPS to near 30 or sometimes lower.
I have v-sync and PostAA enabled as well. I am wondering why this is occurring with something as simple as steam, and if there is anyone else who has dealt with this before and found a way to fix it?
Details of rig:
i5-4570 3.2 ghz
Powercolor Radeon R9 280X OC edition
8 gigs ram
ASUS Z87M-PLUS mobo
Samsung SSD
Buddy, you CAN'T have V-sync on; it caps your frames per second at 60! Turn it off!
It's usually for users who are getting more than 60FPS and getting screen tearing, though it's shunned by almost any competitive player because it causes input lag.
Nevertheless, this game is poorly optimized compared to Battlefield or CS:GO (old engine however). You could probably pull 200+ in BF4 if not 300+ in CSGO.
I would suggest more FPS to turn off AA and lower some of the graphical options to HIGH or even turn some useless effects to LOW per your decisions (shadows and AA are generally known to eat FPS)
Also, I believe it's general consensus that DX9 will NET more FPS as-well.
Edited by 3N3RGY, 20 May 2014 - 01:55 AM.
#4
Posted 20 May 2014 - 03:05 AM

PostAA is soooo light-weight on a system that it's a gimmie for anyone whom isn't hyper-sensitive to the ghosting it introduces.
I don't know if ATI cards have an adaptive v-sync, but if they do, it means you turn it off in-game, but on in the driver for it to work. Also, you'll need triplebuffering for DX up and running, and that can be done with
d3d10_TripleBuffering = 1 d3d11_TripleBuffering = 1 d3d9_TripleBuffering = 1in your user.cfg
You might also want to set a framerate limit equal to your monitors refresh: It's known to bring up ones' minimum fps …
sys_budget_fps = 60 sys_MaxFPS = 60
#5
Posted 21 May 2014 - 01:10 PM
I turned off V-Sync and almost everything was fixed. Thanks!
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users