Basically, my game feels like its running @ 30FPS when in reality I get about 200 FPS in pubs with occasional drops to 150 during action. It's recently gotten worse, and come to the point where its messing with my tracking. I track to hit airshots and even groundshots, but now I'm forced to flick as soldier so I can't hit anything. Halp!
net_graph 4:
Show Content
Config(s):
Show Content
- (Comanglias)
http://pastebin.com/LbvUNtdp
- (My Personal Settings)
http://pastebin.com/VhiJjHCE
- Launch Options: -dxlevel 80 -full -w 1920 -h 1080 -console -novid -heapsize 4194304 -high -noforcemspd -noforcemaccel -nocrashdialog
Custom Folder:
Show Content
- Configs, FlameHUD, Hitsound, No Soundscape, My Training Maps, and the No Explosions Smoke Script combined with removed Muzzleflash.
Optimizations:
Show Content
-
http://www.teamfortress.tv/29140/massive-fps-boost-for-amd-catalyst-users
-
https://steamcommunity.com/sharedfiles/filedetails/?id=483257164
- Enabled RadeonPro Settings: Force Triple-Buffering (OpenGL), Anisotropic Optimization, Trilinear Optimization, Enable Surface Format Optimization, Flip Queue Size (0), Disable Aero, Force Process High Priority, CPU Affinity on CPU 0 and CPU 1, Enable Graphics Overdrive, Always use highest performance clocks while gaming, High Performance GPU clock 975, High Performance Memory clock 1400.
Important Specs:
Show Content
- Intel Pentium G3258 OC'd to 4.3 GHz
- AMD Radeon R9 270
- 128GB SSD
- 1TB HDD (My TF2 is on here)
- Zowie FK1
- Controller I never use that's always plugged in (idk how important this is)
- ASUS VG236H 2ms Response Time Monitor (OC'd to 74.5 Hz W/ patched HDMI frequency)
- Windows 10
Benchmark:
Show Content
- Benchmark1.dem from
http://www.teamfortress.tv/7598/tf2-benchmarks
- 2639 frames 18.783 seconds 140.50 fps ( 7.12 ms/f) 10.297 fps variability
Basically, my game feels like its running @ 30FPS when in reality I get about 200 FPS in pubs with occasional drops to 150 during action. It's recently gotten worse, and come to the point where its messing with my tracking. I track to hit airshots and even groundshots, but now I'm forced to flick as soldier so I can't hit anything. Halp!
net_graph 4:
[spoiler]- http://imgur.com/a/YHAqx[/spoiler]
Config(s):
[spoiler]- (Comanglias) http://pastebin.com/LbvUNtdp
- (My Personal Settings) http://pastebin.com/VhiJjHCE
- Launch Options: -dxlevel 80 -full -w 1920 -h 1080 -console -novid -heapsize 4194304 -high -noforcemspd -noforcemaccel -nocrashdialog[/spoiler]
Custom Folder:
[spoiler]- Configs, FlameHUD, Hitsound, No Soundscape, My Training Maps, and the No Explosions Smoke Script combined with removed Muzzleflash.[/spoiler]
Optimizations:
[spoiler]- http://www.teamfortress.tv/29140/massive-fps-boost-for-amd-catalyst-users
- https://steamcommunity.com/sharedfiles/filedetails/?id=483257164
- Enabled RadeonPro Settings: Force Triple-Buffering (OpenGL), Anisotropic Optimization, Trilinear Optimization, Enable Surface Format Optimization, Flip Queue Size (0), Disable Aero, Force Process High Priority, CPU Affinity on CPU 0 and CPU 1, Enable Graphics Overdrive, Always use highest performance clocks while gaming, High Performance GPU clock 975, High Performance Memory clock 1400.[/spoiler]
Important Specs:
[spoiler]- Intel Pentium G3258 OC'd to 4.3 GHz
- AMD Radeon R9 270
- 128GB SSD
- 1TB HDD (My TF2 is on here)
- Zowie FK1
- Controller I never use that's always plugged in (idk how important this is)
- ASUS VG236H 2ms Response Time Monitor (OC'd to 74.5 Hz W/ patched HDMI frequency)
- Windows 10[/spoiler]
Benchmark:
[spoiler]- Benchmark1.dem from http://www.teamfortress.tv/7598/tf2-benchmarks
- 2639 frames 18.783 seconds 140.50 fps ( 7.12 ms/f) 10.297 fps variability[/spoiler]
now THIS is how you ask for help
now THIS is how you ask for help
I think trying -autoexec would be a good start to see if one of your configs is a problem
I think trying -autoexec would be a good start to see if one of your configs is a problem
also after the first launch you remove -dxlevel from launch options it makes minimizing a pain
also after the first launch you remove -dxlevel from launch options it makes minimizing a pain
are you on hdmi ? cause u shouldnt ..
are you on hdmi ? cause u shouldnt ..
griffalso after the first launch you remove -dxlevel from launch options it makes minimizing a pain
does this affect framerate at all? i have dxlevel 81 set and without it, I get terrible frames ingame, but with it, alt-tabbing takes up to 5 minutes.
does removing the option after the game has been launched remove the fps drop of using dxlevel 9?
[quote=griff]also after the first launch you remove -dxlevel from launch options it makes minimizing a pain[/quote]
does this affect framerate at all? i have dxlevel 81 set and without it, I get terrible frames ingame, but with it, alt-tabbing takes up to 5 minutes.
does removing the option after the game has been launched remove the fps drop of using dxlevel 9?
spammyI think trying -autoexec would be a good start to see if one of your configs is a problem
I believe you're thinking of -autoconfig.
Also, you can just put +mat_dxlevel 81 on the command line instead of -dxlevel 81. Using -dxlevel is kind of like using -autoconfig.
[quote=spammy]I think trying -autoexec would be a good start to see if one of your configs is a problem[/quote]
I believe you're thinking of -autoconfig.
Also, you can just put +mat_dxlevel 81 on the command line instead of -dxlevel 81. Using -dxlevel is kind of like using -autoconfig.
mousiopeare you on hdmi ? cause u shouldnt ..
Why not?
spammyI think trying -autoexec would be a good start to see if one of your configs is a problem
I did autoconfig and autoexec (in case you weren't wrong and autoexec actually did something), and right off the bat it felt a tad bit smoother, and that's with the occasional dipping below my refresh rate.
Any recommendations for another config?
pazerAlso, you can just put +mat_dxlevel 81 on the command line instead of -dxlevel 81. Using -dxlevel is kind of like using -autoconfig.
Okay, I just compared the two in-game to see what happens with both of them, and they actually look REALLY different in the game. I did do a benchmark (and didn't think of copy and pasting), but the numbers were both very even. But why?
[quote=mousiope]are you on hdmi ? cause u shouldnt ..[/quote]
Why not?
[quote=spammy]I think trying -autoexec would be a good start to see if one of your configs is a problem[/quote]
I did autoconfig and autoexec (in case you weren't wrong and autoexec actually did something), and right off the bat it felt a tad bit smoother, and that's with the occasional dipping below my refresh rate.
Any recommendations for another config?
[quote=pazer]Also, you can just put +mat_dxlevel 81 on the command line instead of -dxlevel 81. Using -dxlevel is kind of like using -autoconfig.[/quote]
Okay, I just compared the two in-game to see what happens with both of them, and they actually look REALLY different in the game. I did do a benchmark (and didn't think of copy and pasting), but the numbers were both very even. But why?
have you tried capping your fps at a lower value? could be that you're dipping below your cap too frequently and that's what's making it feel laggy
have you tried capping your fps at a lower value? could be that you're dipping below your cap too frequently and that's what's making it feel laggy
bearodactylhave you tried capping your fps at a lower value? could be that you're dipping below your cap too frequently and that's what's making it feel laggy
No, tried it and it didn't help.
[quote=bearodactyl]have you tried capping your fps at a lower value? could be that you're dipping below your cap too frequently and that's what's making it feel laggy[/quote]
No, tried it and it didn't help.
I searched around for some other configs, and tried Rhapsody's and m0re's. m0re's made mine feel a bit smoother, but TF2 is still nowhere near as smooth as Quake Live for me. Going from 1920 x 1080 → 1280 x 720 REALLY helped with the smoothness, and the game is now 'playable' for me, but I liked having 1920 x 1080, and it's still not 'Quake Live' smooth yet.
edit: my game now for some reason crashes w/ m0re's or comanglia's
m0re's: http://pastebin.com/3LdQAixb
I searched around for some other configs, and tried Rhapsody's and m0re's. m0re's made mine feel a bit smoother, but TF2 is still nowhere near as smooth as Quake Live for me. Going from 1920 x 1080 → 1280 x 720 REALLY helped with the smoothness, and the game is now 'playable' for me, but I liked having 1920 x 1080, and it's still not 'Quake Live' smooth yet.
edit: my game now for some reason crashes w/ m0re's or comanglia's
m0re's: http://pastebin.com/3LdQAixb
If you want your game to be smoother you shouldn't be using m0res high fps. You should be using comanglias config. Also I don't really think it's possible to tf2 to run as smoothly as Quake. Quake has way less going on and way less things to rape your frames. Also going to a 4:3 res will probably give you a decent fps boost if you can deal with the res.
If you want your game to be smoother you shouldn't be using m0res high fps. You should be using comanglias config. Also I don't really think it's possible to tf2 to run as smoothly as Quake. Quake has way less going on and way less things to rape your frames. Also going to a 4:3 res will probably give you a decent fps boost if you can deal with the res.
meyymousiopeare you on hdmi ? cause u shouldnt ..
Why is hdmi bad? I use it...just curious if I could get a couple frames or something
hdmi has an fps cap which varies on the resolution iirc. at some high resolutions it can only do 24hz or something.
[quote=meyy][quote=mousiope]are you on hdmi ? cause u shouldnt ..[/quote]
Why is hdmi bad? I use it...just curious if I could get a couple frames or something[/quote]
hdmi has an fps cap which varies on the resolution iirc. at some high resolutions it can only do 24hz or something.
Props for the clear explanation of what you have/need.
First off your build is fairly decent so maybe the problem is your pc throtlling? Your OC'd CPU and high priority/performance settings is probably increasing your hardware's heat hence system throttling itself and limiting the game's performance but tf2's netgraph isn't affected, or maybe it has to do with your monitor, I'm not sure, check if your heatsink is dusty or broken, and download AIDA64 to check for temps and throttling.
Props for the clear explanation of what you have/need.
First off your build is fairly decent so maybe the problem is your pc throtlling? Your OC'd CPU and high priority/performance settings is probably increasing your hardware's heat hence system throttling itself and limiting the game's performance but tf2's netgraph isn't affected, or maybe it has to do with your monitor, I'm not sure, check if your heatsink is dusty or broken, and download AIDA64 to check for temps and throttling.
Twitchgriffalso after the first launch you remove -dxlevel from launch options it makes minimizing a pain
does this affect framerate at all? i have dxlevel 81 set and without it, I get terrible frames ingame, but with it, alt-tabbing takes up to 5 minutes.
does removing the option after the game has been launched remove the fps drop of using dxlevel 9?
You should do this
1) put -dxlevel 81 in your launch options
2) Launch the game
3) Exit the game
4) Remove -dxlevel 81 from your launch options
It remembers the setting and it makes alt tabbing extremely fast
[quote=Twitch][quote=griff]also after the first launch you remove -dxlevel from launch options it makes minimizing a pain[/quote]
does this affect framerate at all? i have dxlevel 81 set and without it, I get terrible frames ingame, but with it, alt-tabbing takes up to 5 minutes.
does removing the option after the game has been launched remove the fps drop of using dxlevel 9?[/quote]
You should do this
1) put -dxlevel 81 in your launch options
2) Launch the game
3) Exit the game
4) Remove -dxlevel 81 from your launch options
It remembers the setting and it makes alt tabbing extremely fast
I switched to R4ndom's config and now my game is just as smooth as it is when I play Quake, with the lower resolution. The only problem is that my game is STILL crashing. I'm very sure that R4ndom's config has at least parts of m0re's config in it, because I see some of the commands that are in m0re's config but not others. (ex: mat_maxframelatency)
autoexec: http://pastebin.com/8yt8uQjc
HatimProps for the clear explanation of what you have/need.
First off your build is fairly decent so maybe the problem is your pc throtlling? Your OC'd CPU and high priority/performance settings is probably increasing your hardware's heat hence system throttling itself and limiting the game's performance but tf2's netgraph isn't affected, or maybe it has to do with your monitor, I'm not sure, check if your heatsink is dusty or broken, and download AIDA64 to check for temps and throttling.
I did the stress test for ~10 minutes or so, the temps stuck around 74 - 76, and I'm not throttling.
I switched to R4ndom's config and now my game is just as smooth as it is when I play Quake, with the lower resolution. The only problem is that my game is STILL crashing. I'm very sure that R4ndom's config has at least parts of m0re's config in it, because I see some of the commands that are in m0re's config but not others. (ex: mat_maxframelatency)
autoexec: http://pastebin.com/8yt8uQjc
[quote=Hatim]Props for the clear explanation of what you have/need.
First off your build is fairly decent so maybe the problem is your pc throtlling? Your OC'd CPU and high priority/performance settings is probably increasing your hardware's heat hence system throttling itself and limiting the game's performance but tf2's netgraph isn't affected, or maybe it has to do with your monitor, I'm not sure, check if your heatsink is dusty or broken, and download AIDA64 to check for temps and throttling.[/quote]
I did the stress test for ~10 minutes or so, the temps stuck around 74 - 76, and I'm not throttling.
128TB SSD
[quote]128TB SSD[/quote]
MightypazerAlso, you can just put +mat_dxlevel 81 on the command line instead of -dxlevel 81. Using -dxlevel is kind of like using -autoconfig.
Okay, I just compared the two in-game to see what happens with both of them, and they actually look REALLY different in the game. I did do a benchmark (and didn't think of copy and pasting), but the numbers were both very even. But why?
I updated the valve developer wiki with a bit more information on what exactly -dxlevel does that +mat_dxlevel does not: https://developer.valvesoftware.com/wiki/Mat_dxlevel
This can also be specified with Launch Options, use +mat_dxlevel [DirectX version] on the launch options of any Source game to do so. Alternatively, you can use -dxlevel [DirectX version], however this specifies a number of extra presets, including but not limited to:- Resolution
- Windowed/Fullscreen status
- MSAA quality (mat_aaquality) and sample count (mat_antialias)
- Motion blur (mat_motion_blur_*)
- Shadow depth textures (flashlight)
- Gamma (mat_monitorgamma)
[quote=Mighty][quote=pazer]Also, you can just put +mat_dxlevel 81 on the command line instead of -dxlevel 81. Using -dxlevel is kind of like using -autoconfig.[/quote]
Okay, I just compared the two in-game to see what happens with both of them, and they actually look REALLY different in the game. I did do a benchmark (and didn't think of copy and pasting), but the numbers were both very even. But why?[/quote]
I updated the valve developer wiki with a bit more information on what exactly -dxlevel does that +mat_dxlevel does not: https://developer.valvesoftware.com/wiki/Mat_dxlevel
[quote]
This can also be specified with Launch Options, use +mat_dxlevel [DirectX version] on the launch options of any Source game to do so. Alternatively, you can use -dxlevel [DirectX version], however this specifies a number of extra presets, including but not limited to:
[list]
[*]Resolution
[*]Windowed/Fullscreen status
[*]MSAA quality (mat_aaquality) and sample count (mat_antialias)
[*]Motion blur (mat_motion_blur_*)
[*]Shadow depth textures (flashlight)
[*]Gamma (mat_monitorgamma)
[/list]
[/quote]
pazerMightypazerAlso, you can just put +mat_dxlevel 81 on the command line instead of -dxlevel 81. Using -dxlevel is kind of like using -autoconfig.
Okay, I just compared the two in-game to see what happens with both of them, and they actually look REALLY different in the game. I did do a benchmark (and didn't think of copy and pasting), but the numbers were both very even. But why?
I updated the valve developer wiki with a bit more information on what exactly -dxlevel does that +mat_dxlevel does not: https://developer.valvesoftware.com/wiki/Mat_dxlevel
This can also be specified with Launch Options, use +mat_dxlevel [DirectX version] on the launch options of any Source game to do so. Alternatively, you can use -dxlevel [DirectX version], however this specifies a number of extra presets, including but not limited to:- Resolution
- Windowed/Fullscreen status
- MSAA quality (mat_aaquality) and sample count (mat_antialias)
- Motion blur (mat_motion_blur_*)
- Shadow depth textures (flashlight)
- Gamma (mat_monitorgamma)
Wait a moment...
If dxlevel_81 forces motion blur off, and +mat_dxlevel 81 doesn't, then with +mat_dxlevel 81, wouldn't it be possible to have transparent viewmodels?
[quote=pazer][quote=Mighty][quote=pazer]Also, you can just put +mat_dxlevel 81 on the command line instead of -dxlevel 81. Using -dxlevel is kind of like using -autoconfig.[/quote]
Okay, I just compared the two in-game to see what happens with both of them, and they actually look REALLY different in the game. I did do a benchmark (and didn't think of copy and pasting), but the numbers were both very even. But why?[/quote]
I updated the valve developer wiki with a bit more information on what exactly -dxlevel does that +mat_dxlevel does not: https://developer.valvesoftware.com/wiki/Mat_dxlevel
[quote]
This can also be specified with Launch Options, use +mat_dxlevel [DirectX version] on the launch options of any Source game to do so. Alternatively, you can use -dxlevel [DirectX version], however this specifies a number of extra presets, including but not limited to:
[list]
[*]Resolution
[*]Windowed/Fullscreen status
[*]MSAA quality (mat_aaquality) and sample count (mat_antialias)
[*]Motion blur (mat_motion_blur_*)
[*]Shadow depth textures (flashlight)
[*]Gamma (mat_monitorgamma)
[/list]
[/quote][/quote]
Wait a moment...
If dxlevel_81 forces motion blur off, and +mat_dxlevel 81 doesn't, then with +mat_dxlevel 81, wouldn't it be possible to have transparent viewmodels?
-dxlevel just resets some parts of your config while +mat_dxlevel doesn't. You're still running the game in Direct3D 8 mode, where motion blur is not possible.
-dxlevel just resets some parts of your config while +mat_dxlevel doesn't. You're still running the game in Direct3D 8 mode, where motion blur is not possible.
Mighty- ASUS VG236H 2ms Response Time Monitor (OC'd to 74.5 Hz W/ patched HDMI frequency)
this is the part that seems fishy to me
you say other games feel fine though so i guess it cant be but still
[quote=Mighty]- ASUS VG236H 2ms Response Time Monitor (OC'd to 74.5 Hz W/ patched HDMI frequency)[/quote]
this is the part that seems fishy to me
you say other games feel fine though so i guess it cant be but still
Yeah you could be dropping frames from the overclock.
Yeah you could be dropping frames from the overclock.
I'm having a somewhat similar problem. I can get a stable 120 FPS, but when I get into mid fights, or even turn around a lot (I play HL Medic, kinda important), my frames just drop to 30, so I'll do a small turn and do a 180 because my FPS dropped to 30.
I'm having a somewhat similar problem. I can get a stable 120 FPS, but when I get into mid fights, or even turn around a lot (I play HL Medic, kinda important), my frames just drop to 30, so I'll do a small turn and do a 180 because my FPS dropped to 30.
Just out of curiosity, have you tried resetting your monitors refresh rate to 60hz to see if that does anything for you?
Considering TF2 reports a high framerate and your actual computer rig seems fine it might just be hdmi not liking your out of the ordinary refresh rate.
Even if your monitor itself can run the overclock, perhaps the actual cable itself can't support it the way it should.
Just out of curiosity, have you tried resetting your monitors refresh rate to 60hz to see if that does anything for you?
Considering TF2 reports a high framerate and your actual computer rig seems fine it might just be hdmi not liking your out of the ordinary refresh rate.
Even if your monitor itself can run the overclock, perhaps the actual cable itself can't support it the way it should.
HidiI'm having a somewhat similar problem. I can get a stable 120 FPS, but when I get into mid fights, or even turn around a lot (I play HL Medic, kinda important), my frames just drop to 30, so I'll do a small turn and do a 180 because my FPS dropped to 30.
Framerate shouldn't affect sensitivity in tf2. Are you using raw input?
[quote=Hidi]I'm having a somewhat similar problem. I can get a stable 120 FPS, but when I get into mid fights, or even turn around a lot (I play HL Medic, kinda important), my frames just drop to 30, so I'll do a small turn and do a 180 because my FPS dropped to 30.[/quote]
Framerate shouldn't affect sensitivity in tf2. Are you using raw input?
Okay, I just switched back to Chris' net settings, and my game feels like sh*^ again. When I switched back to R4ndom's net settings, my game felt smooth. The smoothness issues also happen offline with the wrong net settings. I can say for certain that my game is smoother with R4ndom's net settings, but the hit registration isn't good.
Can anybody figure anything out from my posted net_graph?
Also, I'm still crashing in-game.
http://pastebin.com/xYM1rZpb
http://pastebin.com/5qAj6sua
TwistedJust out of curiosity, have you tried resetting your monitors refresh rate to 60hz to see if that does anything for you?
Considering TF2 reports a high framerate and your actual computer rig seems fine it might just be hdmi not liking your out of the ordinary refresh rate.
Even if your monitor itself can run the overclock, perhaps the actual cable itself can't support it the way it should.
resetting the refresh rate didn't do anything. It's literally ALL the net settings.
Okay, I just switched back to Chris' net settings, and my game feels like sh*^ again. When I switched back to R4ndom's net settings, my game felt smooth. The smoothness issues also happen offline with the wrong net settings. I can say for certain that my game is smoother with R4ndom's net settings, but the hit registration isn't good.
Can anybody figure anything out from my posted net_graph?
Also, I'm still crashing in-game.
http://pastebin.com/xYM1rZpb
http://pastebin.com/5qAj6sua
[quote=Twisted]Just out of curiosity, have you tried resetting your monitors refresh rate to 60hz to see if that does anything for you?
Considering TF2 reports a high framerate and your actual computer rig seems fine it might just be hdmi not liking your out of the ordinary refresh rate.
Even if your monitor itself can run the overclock, perhaps the actual cable itself can't support it the way it should.[/quote]
resetting the refresh rate didn't do anything. It's literally ALL the net settings.
you only need dxlevel once in launch options btw. For subsequent launches of TF2, it will stay that dxlevel.
This doesn't impact your performance afaik, but it affects how quickly you load the game (I think?)
you only need dxlevel once in launch options btw. For subsequent launches of TF2, it will stay that dxlevel.
This doesn't impact your performance afaik, but it affects how quickly you load the game (I think?)
I started screwing around with my net settings to see what feels smooth, and ended up with this:
rate "60000"
cl_cmdrate "66"
cl_interp "0.0182"
cl_interp_ratio "1.2"
cl_lagcompensation "1"
cl_updaterate "66"
cl_smooth "1"
cl_smoothtime "0"
cl_pred_optimize "2"
net_queue_trace "0"
net_splitpacket_maxrate "1048576"
I used some settings from R4ndom's net settings, and got help on the interp settings from #24 (The ones that fix microstuttering/are for 120Hz): http://www.teamfortress.tv/14120/about-cl-interp-and-hit-registeration
So far, it feels really smooth, although, it's sacrificing a bit of lerp to fix microstuttering, a trade off I'm more than willing to do. Try them out, and tell me what you think.
Also, I think that +mat_dxlevel 81 makes you use DX9 rocket trails, because my rocket trails are feeling unusually large, so I'm going to switch back to -dxlevel 81. I'll take them out after the first launch like Yuki said.
I started screwing around with my net settings to see what feels smooth, and ended up with this:
[list]
rate "60000"
cl_cmdrate "66"
cl_interp "0.0182"
cl_interp_ratio "1.2"
cl_lagcompensation "1"
cl_updaterate "66"
cl_smooth "1"
cl_smoothtime "0"
cl_pred_optimize "2"
net_queue_trace "0"
net_splitpacket_maxrate "1048576"
[/list]
I used some settings from R4ndom's net settings, and got help on the interp settings from #24 (The ones that fix microstuttering/are for 120Hz): http://www.teamfortress.tv/14120/about-cl-interp-and-hit-registeration
So far, it feels really smooth, although, it's sacrificing a bit of lerp to fix microstuttering, a trade off I'm more than willing to do. Try them out, and tell me what you think.
Also, I think that +mat_dxlevel 81 makes you use DX9 rocket trails, because my rocket trails are feeling unusually large, so I'm going to switch back to -dxlevel 81. I'll take them out after the first launch like Yuki said.