Steam for Linux > Discussões Gerais > Detalhes do Tópico
Max_FX 14 Dez, 2012 às 12:10
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!
A mostrar 1-15 de 15 comentários
< >
gutigen o) 14 Dez, 2012 às 13:18 
Turn off composition in KDE, there was some shortcut for that, check google :)
Max_FX 14 Dez, 2012 às 13:25 
I should've mentioned, I have already tried this. In fact, it was the first thing I tried.
supereater14 31 Dez, 2012 às 18:24 
Originalmente postado por 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.
Junior s2 Camila 31 Dez, 2012 às 18:50 
Have you disabled vsync?
Max_FX 13 Jan, 2013 às 18:26 
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 15 Jan, 2013 às 9:05 
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 17 Fev, 2013 às 8:40 
TF2 is choppy for me also with FPS > 150+. I'm running Fedora 18 x86_64 with latest drivers and packages.
[Linux] unbridledExüberance 17 Fev, 2013 às 8:42 
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) 17 Fev, 2013 às 8:46 
Originalmente postado por 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 17 Fev, 2013 às 9:02 
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 17 Fev, 2013 às 9:12 
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) 17 Fev, 2013 às 9:17 
Originalmente postado por 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).
Última alteração por gutigen o); 17 Fev, 2013 às 9:19
gutigen o) 17 Fev, 2013 às 9:19 
Originalmente postado por 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 17 Fev, 2013 às 9:42 
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) 17 Fev, 2013 às 10:21 
Originalmente postado por 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.
Última alteração por gutigen o); 17 Fev, 2013 às 10:28
A mostrar 1-15 de 15 comentários
< >
Por página: 15 30 50
Postado a: 14 Dez, 2012 às 12:10
Comentários: 15