Max_FX Dec 14, 2012 @ 12:10pm
TF2: Choppy Performance with FPS > 100
So, I've been enjoying my fair amount of TF2 on Linux as of late. However, I have an issue where sometimes TF2 is really choppy, but my frame rate is consistently above 100. I am using Kubuntu 12.10 that is completely up-to-date and using NVIDIA Binary drivers v.310.14

Any suggestions on where to look for improvements/solutions? Thanks!
Showing 1-15 of 15 comments
< >
gutigen o) Dec 14, 2012 @ 1:18pm 
Turn off composition in KDE, there was some shortcut for that, check google :)
Max_FX Dec 14, 2012 @ 1:25pm 
I should've mentioned, I have already tried this. In fact, it was the first thing I tried.
supereater14 Dec 31, 2012 @ 6:24pm 
Originally posted by Ubuntu gutigen o):
Turn off composition in KDE, there was some shortcut for that, check google :)
the key combo is alt+shift+f12, turning of compositing didn't help the choppiness, though.
[Linux] Junior s2 Camila Dec 31, 2012 @ 6:50pm 
Have you disabled vsync?
Max_FX Jan 13, 2013 @ 6:26pm 
I thought I would update, the problem has disappeared for me. I'm assuming an update along the way fixed because I've changed nothing.
mm0zct Jan 15, 2013 @ 9:05am 
I still have the same problem, XFCE, AMD 7870 with the current beta drivers, Fedora 17 x64. I haven't tried changing settings like vsync yet, I just noticed it when I tried TF2 today.
AC™ Jun1oR Feb 17, 2013 @ 8:40am 
TF2 is choppy for me also with FPS > 150+. I'm running Fedora 18 x86_64 with latest drivers and packages.
[Linux] unbridledExüberance Feb 17, 2013 @ 8:42am 
By "choppy" do you mean the graphics are going slower than the posted framerate or do you mean there is tearing? If you're framerate is higher than your monitor refresh rate, you don't have vsync on which would cause screen tearing.
gutigen o) Feb 17, 2013 @ 8:46am 
Originally posted by mr.exuberant:
By "choppy" do you mean the graphics are going slower than the posted framerate or do you mean there is tearing? If you're framerate is higher than your monitor refresh rate, you don't have vsync on which would cause screen tearing.

Playing with vsync creates input lag no matter how amazing your machine is, so I would advice to NOT use it for sake of joyful and fragful gaming :)

Tho limiting your framerate or turning limits off may fix your choppiness. Command for fps limit:
fps_max
If you put 0 it will turn limit off.
[Linux] unbridledExüberance Feb 17, 2013 @ 9:02am 
Not really. All vsync does is synchronize the buffer swaps with the monitor refresh rate, which is typically 60 Hz or 120 Hz for higher end monitors. 1/60th of a second is much faster than human reaction time.

If there's input lag, that's because the programmer is implementing events horribly horribly wrong. (Which does happen)
AC™ Jun1oR Feb 17, 2013 @ 9:12am 
Disabling TearFree in the ATI CCC and increasing cl_cmdrate, cl_updaterate, and rate has help with the stuttering but I still have hiccups but no where near as many.
gutigen o) Feb 17, 2013 @ 9:17am 
Originally posted by mr.exuberant:
Not really. All vsync does is synchronize the buffer swaps with the monitor refresh rate, which is typically 60 Hz or 120 Hz for higher end monitors. 1/60th of a second is much faster than human reaction time.

If there's input lag, that's because the programmer is implementing events horribly horribly wrong. (Which does happen)

Well input lag is created by GPU holding more frames in buffer to sync to slower refresh rate then actuall framerate, creating few ms delay. It can be ofc avoided by limiting framerate to your refresh rate or by enabling Triple Buffering. That can reduce input lag to 1 or 2 ms, but not entirely. And trust me, with 1000hz gaming mouse this can make difference (since mouse is an extension to hand).
Last edited by gutigen o); Feb 17, 2013 @ 9:19am
gutigen o) Feb 17, 2013 @ 9:19am 
Originally posted by AC™ Jun1oR:
Disabling TearFree in the ATI CCC and increasing cl_cmdrate, cl_updaterate, and rate has help with the stuttering but I still have hiccups but no where near as many.

You shouldn't change tickrate in CS:S, it's set to 66 for client and server for a reason.
https://developer.valvesoftware.com/wiki/Source_Multiplayer_Networking
AC™ Jun1oR Feb 17, 2013 @ 9:42am 
well mine was set to 33 by default so increasing it to 100 allows me to use whatever the server has it set to.
gutigen o) Feb 17, 2013 @ 10:21am 
Originally posted by AC™ Jun1oR:
well mine was set to 33 by default so increasing it to 100 allows me to use whatever the server has it set to.

Right right... TF2, not CS:S... tho highest working tickrate is 66 I think, just look at net_graph.
Last edited by gutigen o); Feb 17, 2013 @ 10:28am
Showing 1-15 of 15 comments
< >
Per page: 15 30 50
Date Posted: Dec 14, 2012 @ 12:10pm
Posts: 15