Surely it's quite obvious, being locked at 50fps, or just marginally below, what the problem is.
Why are you talking about tickrate? What experiences do you have which would suggest that tickrate can lock you down to 50fps maximum? Given the specs of the machine one would have to do _significant_ damage to the Source configuration in order to reduce it's FPS this low by simply changing tickrate. Please stop taking him down a road that ends dead. This is a kernel timer resolution issue. Kyle Milnes wrote:
2.6 kernels are by default 1000 However, its not always directly related to low FPS Play with your tickrate... And check stats to see what I'm on about
You suggest to do this, but if the FPS never goes above 50, you're going to suffer adverse affects different from those you are trying to point him at. The results you want him to see (which I have seen, and are not related to this issue) will not appear until this kernel timer restriction is removed. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
