Add 2 tutorials (2 files)
Browse Source
Daemon666 committed
parent 550020c877
commit 3b8cc5e016ef1a180bde097d37f7af23e0f8ea11
2 changed files
with 62 additions and 0 deletions
cs16-mouse-input-lag/en.md
A
| @@ -0,0 +1,12 @@ | ||
| 1 | +--- | |
| 2 | +title: "Fix: Mouse Lag and Input Delay in CS 1.6" | |
| 3 | +excerpt: "Track down mouse lag in CS 1.6: frame rate caps, v-sync, the rate and interp settings that add delay, raw input, and the Windows and driver options that matter." | |
| 4 | +category: "client" | |
| 5 | +tags: "mouse, input-lag" | |
| 6 | +image: "" | |
| 7 | +read_time: "8 min read" | |
| 8 | +--- | |
| 9 | +<p>Mouse lag in CS 1.6 is rarely the mouse. It is usually the display or network pipeline adding delay between your hand moving and the shot registering: a frame cap, v-sync, an interpolation setting, or Windows mouse smoothing sitting on top of raw movement. This works through the causes from most to least common so you can find yours quickly instead of changing ten things at once.</p><h2>1. Lift the frame cap and disable v-sync</h2><p>The biggest source of felt lag is a low or v-synced frame rate. Every frame you are not rendering is input you are not seeing. Raise the cap well above your refresh rate and turn v-sync off in the engine:</p><pre>fps_max 300 | |
| 10 | +gl_vsync 0</pre><p>V-sync in particular adds a full frame or more of latency by holding rendered frames back to match the monitor. Disable it in the driver as well — the <a href="/tutorials/cs16-nvidia-settings">NVIDIA settings guide</a> shows where. If frames are low regardless of the cap, that is a performance problem; see the <a href="/tutorials/cs16-fps-boost-guide">FPS boost guide</a> first, because you cannot fix input lag on top of 40 FPS.</p><h2>2. Turn on raw input</h2><p>Raw input reads the mouse directly and bypasses the Windows pointer pipeline, including acceleration and smoothing:</p><pre>m_rawinput 1</pre><p>With raw input on, the game ignores the Windows "Enhance pointer precision" acceleration entirely, so your aim is 1:1. This alone fixes the "my aim feels floaty" complaint for most players. Full detail is in the <a href="/tutorials/cs16-rawinput-mouse-accel">raw input and acceleration guide</a>.</p><h2>3. Fix the rate and interpolation settings</h2><p>Network settings can masquerade as mouse lag because your shots feel like they land late. Set sane rates so the server updates you frequently:</p><pre>cl_cmdrate 101 | |
| 11 | +cl_updaterate 101 | |
| 12 | +rate 100000</pre><p>Then set interpolation to the smallest value the server allows. A high <code>ex_interp</code> deliberately delays what you see to smooth other players' movement, which feels like lag:</p><pre>ex_interp 0.01</pre><p>On a good connection <code>0.01</code> (10 ms) is standard; the engine clamps it to the server's minimum anyway. See the <a href="/tutorials/cs16-best-client-rates">client rates guide</a> for the values matched to your ping, and <a href="/tutorials/sv-maxrate-maxupdaterate-values">the server-side rate caps</a> that limit what you can request.</p><h2>4. Disable Windows pointer acceleration</h2><p>Even with raw input, it is worth turning off Windows acceleration globally so every game behaves. In <strong>Settings > Bluetooth & devices > Mouse > Additional mouse settings > Pointer Options</strong>, uncheck <strong>Enhance pointer precision</strong>. Set the pointer speed slider to the middle (the 6th notch), which is 1:1 with no scaling. The legacy launch options that force this off still work as a belt-and-braces measure:</p><pre>-noforcemparms -noforcemaccel -noforcemspd</pre><h2>5. Rule out the hardware path</h2><p>If lag persists after all of the above, test the mouse itself. Set the polling rate to 1000 Hz in the mouse's own software, plug it directly into a rear USB port rather than a hub or front-panel port, and disable any driver-level "angle snapping" or smoothing. A worn USB cable or a dying switch produces intermittent lag that no cvar can fix.</p><h2>Common errors</h2><ul><li><strong>Aim feels floaty and delayed</strong> — Windows acceleration is active. Enable <code>m_rawinput 1</code> and uncheck Enhance pointer precision.</li><li><strong>Smooth in menus, laggy in a firefight</strong> — frame rate drops under load. This is a performance issue, not input; raise FPS first.</li><li><strong>Shots register late despite good FPS</strong> — high <code>ex_interp</code> or low <code>cl_updaterate</code>. Lower interp and raise the rates.</li><li><strong>Lag only with v-sync-like smoothness</strong> — v-sync is on in the driver even though <code>gl_vsync 0</code>. Turn it off in the control panel too.</li><li><strong>Intermittent stutter unrelated to settings</strong> — USB hub, low polling rate, or a failing cable. Move to a rear port and set 1000 Hz.</li></ul><h2>Verification</h2><p>Enable the net graph and watch it while you move:</p><pre>net_graph 3</pre><p>FPS should be high and stable, and the choke/loss figures near zero — if choke spikes when you move, the problem is network, not mouse. Then do a slow flick across a fixed point on the wall: the crosshair should track your hand exactly with no drift or catch-up, which is the signature of raw input working. If it still drifts, acceleration is sneaking in from Windows or the mouse driver. Once movement is 1:1, dial in sensitivity knowing the input path underneath it is clean. A last sanity check: quit every background overlay (recording software, RGB utilities, browser hardware acceleration) and retest, because an overlay hooking the render path can add a frame of latency that survives every in-game fix. Input lag is cumulative, so removing one cause at a time and re-testing with the net graph is the only reliable way to find which layer is responsible.</p> |
cs16-steam-cant-join-nonsteam/en.md
A
| @@ -0,0 +1,50 @@ | ||
| 1 | +--- | |
| 2 | +title: "Fix: Steam CS 1.6 Can't Join a Non-Steam Server" | |
| 3 | +excerpt: "Why a legitimate Steam CS 1.6 client fails to connect to a non-Steam community server, what the server must run to accept it, and what the client can check." | |
| 4 | +category: "client" | |
| 5 | +tags: "non-steam, connect" | |
| 6 | +image: "" | |
| 7 | +read_time: "8 min read" | |
| 8 | +--- | |
| 9 | +<p>A large share of CS 1.6's community servers run software that lets non-Steam (pirated) clients play. When your legitimate Steam client tries to join one, it can be rejected or hang on connect — which feels backwards, since you are the one who paid. The cause is almost always on the server: it either only accepts non-Steam clients, or it is misconfigured to accept both. Understanding the mechanism tells you what to check and what to ask the operator.</p> | |
| 10 | + | |
| 11 | +<h2>1. Understand the two client worlds</h2> | |
| 12 | +<p>CS 1.6 clients authenticate in one of two ways: through Steam (a real SteamID validated by Valve) or as a non-Steam client with a locally generated ID. A stock Valve server only accepts Steam clients. To accept non-Steam players, an operator installs an emulation layer — <a href="/tutorials/install-reunion-nonsteam">Reunion</a> on <a href="/tutorials/install-rehlds-on-linux">ReHLDS</a>, or dproto on original HLDS. Those layers can be configured to accept <em>only</em> non-Steam, <em>only</em> Steam, or <strong>both</strong>. If a server accepts only non-Steam, your Steam client is refused by design.</p> | |
| 13 | + | |
| 14 | +<h2>2. Read the actual error</h2> | |
| 15 | +<p>The message tells you which side is refusing:</p> | |
| 16 | +<ul> | |
| 17 | +<li><strong>"STEAM validation rejected"</strong> — the server's emulation layer is not configured to accept Steam clients (or its Steam validation is broken). This is a server-side setting; you cannot fix it from the client.</li> | |
| 18 | +<li><strong>Connection hangs then times out</strong> — often a firewall or the server dropping your protocol, not authentication.</li> | |
| 19 | +<li><strong>"Bad challenge" / "Server is enforcing consistency for this file"</strong> — a file/consistency check, unrelated to Steam vs non-Steam; a resource mismatch.</li> | |
| 20 | +</ul> | |
| 21 | +<p>Quote the exact line when you ask the operator for help — it points straight at the cause.</p> | |
| 22 | + | |
| 23 | +<h2>3. What the server must do (share this with the operator)</h2> | |
| 24 | +<p>To let both Steam and non-Steam players in, the operator sets the emulator's client-type mode to accept both. In Reunion this is a value in its config that selects a mode allowing Steam and non-Steam simultaneously, and Reunion additionally requires a <code>SteamIdHashSalt</code> of at least 16 characters or it refuses to load at all:</p> | |
| 25 | +<pre>; reunion.cfg (server side) | |
| 26 | +SteamIdHashSalt = a-long-random-string-16+ | |
| 27 | +; client-type mode must be set to accept both Steam and non-Steam</pre> | |
| 28 | +<p>If the salt is missing or too short, Reunion does not start and every client — Steam and non-Steam alike — fails to connect. That is a server fault, not yours.</p> | |
| 29 | +<p>The equivalent on original HLDS is dproto, which has its own config selecting whether Steam clients, non-Steam clients, or both are accepted. The concept is identical: an emulation layer sits in front of authentication and decides who is allowed. When you cannot join a non-Steam server as a paying Steam user, it is almost always this switch set to non-Steam-only, and only the operator can change it.</p> | |
| 30 | + | |
| 31 | +<h2>4. What you can actually check on the client</h2> | |
| 32 | +<p>Client-side options are limited, but rule these out:</p> | |
| 33 | +<ul> | |
| 34 | +<li><strong>Try a direct connect</strong> from the console to bypass browser quirks: | |
| 35 | +<pre>connect 203.0.113.10:27015</pre></li> | |
| 36 | +<li><strong>Verify your files</strong> so a consistency check is not the real culprit — see <a href="/tutorials/cs16-verify-game-files">verifying game files</a>.</li> | |
| 37 | +<li><strong>Check you are not on a stale beta branch.</strong> If you rolled back to <code>steam_legacy</code> after the 25th Anniversary update, your protocol may not match what the server expects. Switch back to the default branch and retry.</li> | |
| 38 | +<li><strong>Confirm it is not you.</strong> If other Steam players are on the server (visible player count with Steam names), the server accepts Steam clients and your problem is local — firewall, files, or branch.</li> | |
| 39 | +</ul> | |
| 40 | + | |
| 41 | +<h2>Troubleshooting</h2> | |
| 42 | +<ul> | |
| 43 | +<li><strong>"STEAM validation rejected" on one server only</strong> — that server accepts non-Steam only. Nothing to fix client-side; ask the operator to enable the both-clients mode.</li> | |
| 44 | +<li><strong>Every non-Steam server rejects you</strong> — likely your game branch or a firewall, not each server. Return to the default branch and test a direct connect.</li> | |
| 45 | +<li><strong>You can see Steam players in-game but still cannot join</strong> — local issue: verify files, check firewall, disable a VPN.</li> | |
| 46 | +<li><strong>Server owner and you both confirm the both-clients mode is on but it still fails</strong> — check the <code>SteamIdHashSalt</code> length; under 16 characters stops Reunion loading entirely.</li> | |
| 47 | +</ul> | |
| 48 | + | |
| 49 | +<h2>Verification</h2> | |
| 50 | +<p>Ask whether any Steam-authenticated players are currently on the target server. If yes, it accepts Steam clients and your fix is local — verify files and retry a direct <code>connect</code>. If no Steam player has ever joined, the server is non-Steam-only and the fix is entirely on the operator's side (enable the both-clients mode with a valid salt). Operators setting this up for the first time should follow <a href="/tutorials/install-reunion-nonsteam">the Reunion install guide</a>.</p> | |
| 0 | 51 |
