Add 2 tutorials (2 files)
Browse Source
Daemon666 committed
parent d64263085d
commit 18c99e9438fea91edcdacef2c2fda1add910e30f
2 changed files
with 64 additions and 0 deletions
cs16-net-graph-guide/en.md
A
| @@ -0,0 +1,12 @@ | ||
| 1 | +--- | |
| 2 | +title: "net_graph 3: How to Read It" | |
| 3 | +excerpt: "A field guide to the CS 1.6 net graph: what FPS, ping, in/out, loss and choke each mean, how to position and size it, and which numbers signal a real problem." | |
| 4 | +category: "client" | |
| 5 | +tags: "net_graph, netcode" | |
| 6 | +image: "" | |
| 7 | +read_time: "8 min read" | |
| 8 | +--- | |
| 9 | +<p>The net graph is the single most useful diagnostic a CS 1.6 player has. It overlays your real frame rate, ping, and the health of the connection between you and the server, and it turns vague complaints like "it feels laggy" into specific numbers you can act on. Most players turn it on and ignore it because nobody told them what the columns mean. Here is how to read every part.</p><h2>1. Turn it on and pick a display level</h2><p>The cvar takes three useful values:</p><pre>net_graph 1 | |
| 10 | +net_graph 2 | |
| 11 | +net_graph 3</pre><ul><li><code>1</code> — the graph plus the summary line (FPS, ping, and the traffic figures). This is the level most people want.</li><li><code>2</code> — adds per-frame byte sizes for incoming and outgoing packets.</li><li><code>3</code> — the most detailed, showing the packet timing bars. Good for diagnosing stutter.</li></ul><p>Start with <code>net_graph 3</code> when hunting a problem and drop to <code>1</code> for everyday play.</p><h2>2. Read the summary line</h2><p>The bottom text line is where the actionable numbers live:</p><ul><li><strong>fps</strong> — your rendered frames per second. Should sit above your monitor's refresh rate. If this drops in fights, it is a performance problem — see the <a href="/tutorials/cs16-fps-boost-guide">FPS boost guide</a>.</li><li><strong>ping</strong> — round-trip latency to the server in milliseconds. Lower is better; under 50 is excellent, over 100 is felt.</li><li><strong>in / out</strong> — bytes per second you are receiving and sending. These confirm data is actually flowing.</li></ul><h2>3. Understand loss and choke — the two that matter most</h2><p>Two figures tell you whether the connection is healthy, and people constantly confuse them:</p><ul><li><strong>loss</strong> — the percentage of packets lost in transit between you and the server. Loss is a network fault: a bad Wi-Fi link, a saturated line, or a route problem. Any sustained loss above zero causes rubber-banding and missed hits.</li><li><strong>choke</strong> — the server wanting to send you more updates than your <code>rate</code> or its <code>sv_maxupdaterate</code> allows, so it holds them back. Choke is a <em>rate</em> problem, not packet loss. It usually means your <code>cl_updaterate</code> exceeds what the server can deliver, or your <code>rate</code> is too low.</li></ul><p>The distinction is practical: loss you fix by improving your connection; choke you fix by adjusting rates. See the <a href="/tutorials/cs16-best-client-rates">client rates guide</a> for choke, and note that some choke is the <a href="/tutorials/fix-choke-loss-scoreboard">server's own rate cap</a>.</p><h2>4. Read the packet bars (net_graph 3)</h2><p>The moving bar graph shows each recent frame. A clean connection is a flat, even line. Interpret the colors and gaps:</p><ul><li>Even, consistent bars mean steady frame delivery.</li><li>Tall spikes or gaps in the line indicate stutter — a frame took too long, either to render (FPS drop) or to arrive (network hitch).</li><li>Yellow/red segments flag choke and loss visually, so you can see a problem the instant it happens rather than reading numbers.</li></ul><h2>5. Position and size the graph</h2><p>Move it out of your sightline and scale it to taste:</p><pre>net_graphpos 2 | |
| 12 | +net_graphheight 64</pre><p><code>net_graphpos</code> takes <code>1</code> (right), <code>2</code> (center) or <code>3</code> (left); use whatever does not sit under your crosshair. <code>net_graphheight</code> raises it off the very bottom edge so it is readable. Add these to your <a href="/tutorials/cs16-config-cfg-guide">config.cfg</a> so they persist.</p><h2>Common errors</h2><ul><li><strong>Constant choke but zero loss</strong> — your rates are mismatched to the server, not a bad connection. Lower <code>cl_updaterate</code> to what the server delivers or raise <code>rate</code>.</li><li><strong>Loss climbing on Wi-Fi</strong> — that is a physical link problem. Use a wired connection; no cvar fixes packet loss.</li><li><strong>FPS number is fine but the game stutters</strong> — the packet bars show gaps: network hitching, not frames. Check ping stability and loss.</li><li><strong>Graph is under the crosshair</strong> — change <code>net_graphpos</code> and raise <code>net_graphheight</code>.</li><li><strong>Ping is low but hits do not register</strong> — high interp or choke delaying updates; check choke and lower <code>ex_interp</code>.</li></ul><h2>Verification</h2><p>Join a server you consider good and read the baseline:</p><pre>net_graph 3</pre><p>On a healthy connection you should see FPS above your refresh rate, ping matching your expected latency, and loss and choke both at or near zero. Note those values — that is your "normal". When a server later feels bad, compare against this baseline: if loss appears, it is the network; if choke appears, it is rates; if FPS drops, it is performance. The net graph does not fix anything, but it tells you exactly which guide to open next, whether that is <a href="/tutorials/cs16-fix-high-ping">high ping</a> or <a href="/tutorials/cs16-mouse-input-lag">input lag</a>. Get in the habit of glancing at it whenever a server feels off — thirty seconds of reading the graph saves you from changing settings that were never the problem, and it is the difference between diagnosing a connection and guessing at one.</p> |
cs16-verify-game-files/en.md
A
| @@ -0,0 +1,52 @@ | ||
| 1 | +--- | |
| 2 | +title: "Verifying CS 1.6 Game File Integrity on Steam" | |
| 3 | +excerpt: "When and how to verify the integrity of Counter-Strike 1.6 files on Steam, what the process fixes, and how to avoid it wiping your custom content." | |
| 4 | +category: "client" | |
| 5 | +tags: "steam, files" | |
| 6 | +image: "" | |
| 7 | +read_time: "7 min read" | |
| 8 | +--- | |
| 9 | +<p>A surprising number of CS 1.6 problems — crashes on launch, missing textures, corrupt sounds, settings that will not save, "could not load library" errors — trace back to one or two damaged files. Steam has a built-in check that compares your local files against the known-good manifest and re-downloads anything wrong. It is the first thing to try when the game misbehaves for no obvious reason, but it has one side effect worth knowing about first.</p> | |
| 10 | + | |
| 11 | +<h2>1. When to verify</h2> | |
| 12 | +<p>Reach for a file verification when you see symptoms that point at a broken install rather than a server or a config:</p> | |
| 13 | +<ul> | |
| 14 | +<li>The game crashes immediately on launch, or before the main menu.</li> | |
| 15 | +<li>Missing or flashing "ERROR" models, purple/black checkerboard textures, silent weapons.</li> | |
| 16 | +<li>"Could not load library client" or a similar missing-DLL error.</li> | |
| 17 | +<li>Settings that refuse to save, or the game reverting to defaults each launch.</li> | |
| 18 | +<li>After a crash during a Steam update, or a disk error / unclean shutdown.</li> | |
| 19 | +</ul> | |
| 20 | +<p>If instead the problem is only on one server (slow downloads, cannot connect), verifying will not help — that is not a file issue.</p> | |
| 21 | + | |
| 22 | +<h2>2. Back up your custom content first</h2> | |
| 23 | +<p>Verification restores the game to its shipped state. It will <strong>not</strong> normally delete files that are not part of the game, but a mismatched or modified official file (a replaced HUD, a modified <code>gfx</code>, an edited game resource) can be reverted. Before you run it, copy anything you care about out of <code>cstrike/</code>:</p> | |
| 24 | +<pre>Steam\steamapps\common\Half-Life\cstrike\ | |
| 25 | + userconfig.cfg <- your settings | |
| 26 | + maps\ <- downloaded/custom maps | |
| 27 | + sound\ models\ <- custom content | |
| 28 | + sprites\ <- custom sprays/HUD</pre> | |
| 29 | +<p>Copy that folder somewhere safe. Custom maps and your <code>userconfig.cfg</code> are the two things people most regret losing.</p> | |
| 30 | + | |
| 31 | +<h2>3. Run the verification</h2> | |
| 32 | +<p>In the Steam Library, right-click <strong>Counter-Strike</strong> and choose <strong>Properties</strong>. Open the <strong>Installed Files</strong> (older Steam: <strong>Local Files</strong>) tab and click <strong>Verify integrity of game files</strong>. Steam hashes every file, compares it to the manifest, and re-downloads any that are missing or wrong. It typically takes a couple of minutes for a game this small. When it finishes it reports either that all files validated successfully, or that a number of files were reacquired.</p> | |
| 33 | + | |
| 34 | +<h2>4. Understand what it did (and did not) fix</h2> | |
| 35 | +<p>Verification repairs <em>official</em> game files. It fixes corrupt DLLs, damaged base maps, broken sounds, and a corrupt install that would not save settings. It does <strong>not</strong> fix: server-side problems, mouse/config preferences (those are yours), a wrong Windows setting, or a bad game branch. If the game launches cleanly after verifying, the fault was a damaged file. If it does not, the problem is elsewhere — move on to Windows compatibility or your launch options.</p> | |
| 36 | + | |
| 37 | +<h2>5. Restore your content</h2> | |
| 38 | +<p>After a clean verification, copy your backed-up <code>maps\</code>, <code>sound\</code>, custom models and <code>userconfig.cfg</code> back into <code>cstrike/</code>. Re-exec your config in-game with <code>exec userconfig.cfg</code>. Test before assuming everything is back.</p> | |
| 39 | + | |
| 40 | +<h2>Troubleshooting</h2> | |
| 41 | +<ul> | |
| 42 | +<li><strong>Verification re-downloads files every single time</strong> — a modified official file keeps failing the hash, or a disk/permissions problem prevents Steam writing the fix. Check the drive for errors and that Steam has write access to the folder.</li> | |
| 43 | +<li><strong>"1 file failed to validate and will be reacquired" every run</strong> — often a mod file replacing an official one. If it is a mod you want, that message is expected; if not, let Steam replace it.</li> | |
| 44 | +<li><strong>Game still crashes after a clean verify</strong> — not a file problem. Look at Windows compatibility and launch options via <a href="/tutorials/cs16-windows-11-fixes">the Windows 11 fixes guide</a>.</li> | |
| 45 | +<li><strong>Lost my custom maps</strong> — they were overwritten or you had not backed them up. This is why step 2 exists; restore from your copy or re-download them.</li> | |
| 46 | +<li><strong>Settings still reset after verifying</strong> — the config file is read-only or in the wrong place. Keep settings in <code>cstrike/userconfig.cfg</code> and exec it.</li> | |
| 47 | +</ul> | |
| 48 | + | |
| 49 | +<h2>Verification</h2> | |
| 50 | +<p>After the process reports success, launch the game and confirm the symptom is gone — the menu loads, textures render, sound plays. Load a base map like <code>de_dust2</code> from the console:</p> | |
| 51 | +<pre>map de_dust2</pre> | |
| 52 | +<p>If it loads with correct textures and audio, the official files are healthy. Then restore and re-exec your custom content and confirm the game still runs. If the crash or error persists on a freshly validated install, it is not a file-integrity problem and the next stop is <a href="/tutorials/cs16-windows-11-fixes">compatibility and launch options</a>.</p> | |
| 0 | 53 |
