+sv clockcorrection msecs 0: Difference between revisions

Latest revision as of 17:31, 24 February 2014

++ Dieser Bug wurde am 04.12.2012 von Valve mit einen Patch beseitigt ++

Interpolate Bug FIX bei CKRAS CS:GO aktiv

Wir haben den Interpolate Bug FIX für alle CounterStrike Global Offensive Server aktiviert, auf diesen zBlock Programmierer im offiziellen Valve Forum verwiesen hat. Wir wollen Euch damit die Möglichkeit bieten, dass ihr selber optional mit einen Neustart im Webinterface, den Interpolate Bug Fix für CS:GO aktiviert.

Zitat:
Cvar "sv_clockcorrection_msecs" defaults to "60"
So this is something I discussed a while ago, as spotting this in the SDK struck me as somewhat odd. The result was in VALVE not changing this.
I understand why there is a need for jitter correction like this, but I've never liked this implementation.
I feel it should be down to the client to decide how much they need, this basically performs the same feature as "cl_interp" but isn't being configurable.

All zBlock match-servers currently have this set to "30" and Verygames DM have been running with "0" on their servers for months now.
It's also presently set at 0 in a couple of competitive league configs.

If you were to remove this cvar (or set it to 0 in CSGO) I'd be happy if the result was more relaxed cl_interp restrictions, so that "cl_interp_ratio" could be between 1 and 3, instead of the current forced competitive values min 1 and max 2.

Reducing this value should have the largest impact on the game for competitive players.
For example I have a average jitter of between 2-10ms on my home Internet connection and a latency of about 15ms to many game servers.
There is no need for me to have the 60ms jitter correction, it's increasing position latency by about 4x! So I could easily get away without the jitter correction and rely on a tiny amount of extrapolation.

If I wanted a slightly smoother more accurate game I could increase cl_interp_ratio to 2.
I'd really appreciate it if this in particular could be reviewed."

<youtube>y_WZD3s7FFg</youtube>

center
Wir würden uns über Euer Feedback in unserem Forum oder via support @ ckras . com freuen.

@@ Line 1: / Line 1: @@
+++ Dieser Bug wurde am 04.12.2012 von Valve mit einen Patch beseitigt ++
 == Interpolate Bug FIX bei CKRAS [[CS:GO]] aktiv ==
-Cvar "sv_clockcorrection_msecs" defaults to "60"
+Wir haben den Interpolate Bug FIX für alle CounterStrike Global Offensive Server aktiviert, auf diesen [[zBlock]] Programmierer im offiziellen [[Valve]] Forum verwiesen hat. Wir wollen Euch damit die Möglichkeit bieten, dass ihr selber optional mit einen Neustart im [[Webinterface]], den Interpolate Bug Fix für [[CS:GO]] aktiviert.
-So this is something I discussed a while ago, as spotting this in the SDK struck me as somewhat odd. The result was in VALVE not changing this.
+<br><br>
-I understand why there is a need for jitter correction like this, but I've never liked this implementation.
+Zitat: <br>
-I feel it should be down to the client to decide how much they need, this basically performs the same feature as "cl_interp" but isn't being configurable.
+Cvar "sv_clockcorrection_msecs" defaults to "60"<br>
+So this is something I discussed a while ago, as spotting this in the SDK struck me as somewhat odd. The result was in VALVE not changing this.<br>
+I understand why there is a need for jitter correction like this, but I've never liked this implementation.<br>
+I feel it should be down to the client to decide how much they need, this basically performs the same feature as "cl_interp" but isn't being configurable.<br><br>
+All zBlock match-servers currently have this set to "30" and Verygames DM have been running with "0" on their servers for months now.<br>
+It's also presently set at 0 in a couple of competitive league configs.<br><br>
-All zBlock match-servers currently have this set to "30" and Verygames DM have been running with "0" on their servers for months now.
+If you were to remove this cvar (or set it to 0 in CSGO) I'd be happy if the result was more relaxed cl_interp restrictions, so that "cl_interp_ratio" could be between 1 and 3, instead of the current forced competitive values min 1 and max 2.<br><br>
-It's also presently set at 0 in a couple of competitive league configs.
-If you were to remove this cvar (or set it to 0 in CSGO) I'd be happy if the result was more relaxed cl_interp restrictions, so that "cl_interp_ratio" could be between 1 and 3, instead of the current forced competitive values min 1 and max 2.
+Reducing this value should have the largest impact on the game for competitive players.<br>
+For example I have a average jitter of between 2-10ms on my home Internet connection and a latency of about 15ms to many game servers.<br>
+There is no need for me to have the 60ms jitter correction, it's increasing position latency by about 4x! So I could easily get away without the jitter correction and rely on a tiny amount of extrapolation.<br><br>
-Reducing this value should have the largest impact on the game for competitive players.
+If I wanted a slightly smoother more accurate game I could increase cl_interp_ratio to 2.<br>
-For example I have a average jitter of between 2-10ms on my home Internet connection and a latency of about 15ms to many game servers.
+I'd really appreciate it if this in particular could be reviewed."<br><br>
-There is no need for me to have the 60ms jitter correction, it's increasing position latency by about 4x! So I could easily get away without the jitter correction and rely on a tiny amount of extrapolation.
+<youtube>y_WZD3s7FFg</youtube>
-If I wanted a slightly smoother more accurate game I could increase cl_interp_ratio to 2.
+[[Datei:Beispiel.jpg|center]]<br>
-I'd really appreciate it if this in particular could be reviewed."
+Wir würden uns über Euer Feedback in unserem [https://forum.ckras.com/thread.php?threadid=3521 Forum] oder via support @ ckras . com freuen.