Add 2 tutorials (2 files)
Browse Source
Daemon666 committed
parent ab2fb368c6
commit d9ba45b9cda60f7a0bf276b16ed2af47cb571b3d
2 changed files
with 61 additions and 0 deletions
cs16-install-skins-models/en.md
A
| @@ -0,0 +1,10 @@ | ||
| 1 | +--- | |
| 2 | +title: "Installing Weapon Skins and Player Models Safely" | |
| 3 | +excerpt: "Where CS 1.6 stores view, world and player models, how to install custom skins without breaking hitboxes, and why sv_consistency can kick you for the wrong files." | |
| 4 | +category: "client" | |
| 5 | +tags: "skins, models" | |
| 6 | +image: "" | |
| 7 | +read_time: "8 min read" | |
| 8 | +--- | |
| 9 | +<p>Custom weapon skins and player models are one of the oldest reasons to mod CS 1.6, and also one of the easiest ways to get yourself kicked from a server or, worse, quietly disadvantaged in a match. The engine loads models from fixed folders and some servers enforce that your files match theirs. This walks through where each type of model lives, how to install one cleanly, and how to back out when a skin causes problems.</p><h2>1. Know the three kinds of model</h2><p>A CS 1.6 weapon is actually three separate model files, and a skin pack usually replaces all three:</p><ul><li><strong>v_ models</strong> — the <em>view</em> model, the weapon in your own hands. This is what a skin visibly changes for you.</li><li><strong>p_ models</strong> — the <em>player</em> (world) model, the weapon as seen on other players' backs and hands.</li><li><strong>w_ models</strong> — the <em>weapon</em> model lying on the ground before pickup.</li></ul><p>All of these live in <code>cstrike/models/</code>, for example <code>v_ak47.mdl</code>, <code>p_ak47.mdl</code> and <code>w_ak47.mdl</code>. Player character models live in <code>cstrike/models/player/<name>/</code>, one folder per character such as <code>leet</code>, <code>gign</code> or <code>terror</code>.</p><h2>2. Back up the originals first</h2><p>Before overwriting anything, copy the stock file so you can restore it. From the CS folder:</p><pre>cd cstrike/models | |
| 10 | +copy v_ak47.mdl v_ak47.mdl.bak</pre><p>On Linux use <code>cp v_ak47.mdl v_ak47.mdl.bak</code>. A backup is the difference between a two-second undo and reinstalling the game, because a bad model can crash the map load or produce broken hitboxes.</p><h2>3. Install the view/world skin</h2><p>Drop the replacement <code>.mdl</code> files into <code>cstrike/models/</code>, keeping the exact original filenames. If the skin pack ships a <code>v_</code>, <code>p_</code> and <code>w_</code> set, install all three so the weapon looks consistent in your hands, on the ground, and on other players. Filenames must match the originals exactly — <code>v_ak47.mdl</code>, not <code>v_ak47_custom.mdl</code> — or the engine will not load them.</p><h2>4. Install a player model</h2><p>Player models replace the character skins. Place the folder under <code>cstrike/models/player/</code> using the stock character name it replaces, so <code>cstrike/models/player/leet/leet.mdl</code>. <strong>Only replace models whose skeleton and hitboxes match the original.</strong> A model with altered proportions can shift the visible body away from the real hitboxes — for you, that is cosmetic, but a mismatched model is exactly why some servers ban custom player models outright.</p><h2>5. Respect server consistency checks</h2><p>Many servers set <code>sv_consistency 1</code> and force-check specific files. If your model differs from what the server expects, you get kicked at join with a message like:</p><pre>Server is enforcing file consistency for models/player/...</pre><p>This is not a bug — it is the server refusing a client whose files do not match, precisely to stop no-hitbox or wallhack-style models. When a server enforces consistency, you must play with the stock model (restore your backup) or the server's own required files. There is no client-side override that beats a server enforcing consistency; that is the whole point of the feature. Server admins configure this with the <code>sv_consistency</code> cvar and a <a href="/plugins/csb-cvar-checker">cvar checker</a> plugin.</p><h2>Common errors</h2><ul><li><strong>Kicked at join with a consistency message</strong> — the server enforces file consistency and your model does not match. Restore the original file from your backup.</li><li><strong>Map fails to load or the game crashes</strong> — the model is corrupt or built for a different engine. Remove it and restore the backup.</li><li><strong>Skin does not appear</strong> — wrong filename (must match the original exactly) or you edited the wrong folder. View models are in <code>cstrike/models/</code>, not a subfolder.</li><li><strong>Weapon shows in your hands but not on the ground</strong> — you installed the <code>v_</code> model but not the matching <code>w_</code> and <code>p_</code> files.</li><li><strong>Hitboxes feel off after a player model swap</strong> — the model's skeleton differs from stock. Do not use models with changed proportions; they are the reason consistency exists.</li></ul><h2>Verification</h2><p>Load a bot match offline to test without risking a kick:</p><pre>map de_dust2</pre><p>Buy the weapon and confirm the view model looks right, drop it and check the world model, then check another player (a bot) for the world/player model. Then join a server that enforces consistency and confirm you are not kicked — if you are, restore the specific file it names from your <code>.bak</code> copy. Keep your backups; the fastest fix for any skin problem is putting the stock file back. A tidy habit is to keep a small folder of your installed skins outside the game directory so a Steam file-integrity verification (which restores stock models) does not wipe your work permanently — you can reapply from that folder in seconds. For sound customization done the same careful way, see the <a href="/tutorials/cs16-no-sound-windows">audio troubleshooting guide</a>, and if you run your own server and want to push a required model set to players, that is the FastDL and consistency path rather than a local install.</p> |
cs16-slow-server-downloads/en.md
A
| @@ -0,0 +1,51 @@ | ||
| 1 | +--- | |
| 2 | +title: "Fix: Slow Downloads When Joining a Server" | |
| 3 | +excerpt: "Why custom maps and models crawl when you join a CS 1.6 server, what the client can control, and how FastDL on the server fixes it for everyone." | |
| 4 | +category: "client" | |
| 5 | +tags: "downloads, fastdl" | |
| 6 | +image: "" | |
| 7 | +read_time: "7 min read" | |
| 8 | +--- | |
| 9 | +<p>You join a server running a custom map, the loading screen sits on "Verifying and downloading resources," and files trickle in at a few kilobytes a second. A 20 MB map can take minutes, and sometimes you time out before it finishes. Understanding why tells you which parts are yours to fix and which belong to the server operator.</p> | |
| 10 | + | |
| 11 | +<h2>1. Understand what is actually happening</h2> | |
| 12 | +<p>When you connect, the server sends a list of resources the map needs — the <code>.bsp</code>, models, sounds, sprites. Anything you are missing is downloaded before you spawn. If the server has no HTTP mirror configured, those files come over the old in-game UDP transfer channel, which is throttled to a crawl by design. That slow trickle is the default, and no client setting makes it fast — the fix is a server-side HTTP mirror called FastDL.</p> | |
| 13 | + | |
| 14 | +<h2>2. Confirm downloads are enabled on your client</h2> | |
| 15 | +<p>There is one client cvar that can stop downloads entirely. Make sure it is on:</p> | |
| 16 | +<pre>cl_allowdownload 1 | |
| 17 | +cl_allowupload 1</pre> | |
| 18 | +<p>If <code>cl_allowdownload</code> is 0 you will not download missing content at all — you spawn with missing textures, error models (the flashing "ERROR" sign), or get kicked for a missing file. Set it to 1. This is the only download knob the client owns; it controls <em>whether</em> you download, not how fast.</p> | |
| 19 | + | |
| 20 | +<h2>3. Know that speed is the server's job (FastDL)</h2> | |
| 21 | +<p>Fast downloads come from the server operator pointing <code>sv_downloadurl</code> at an HTTP mirror. When that is configured, your client fetches the same files over plain HTTP at your full connection speed instead of the throttled UDP channel — the difference is seconds versus minutes. You cannot enable this from the client side; if a particular server is slow, it simply does not run FastDL. Server admins reading this should set it up with <a href="/tutorials/fastdl-setup-guide">the FastDL setup guide</a>.</p> | |
| 22 | + | |
| 23 | +<h2>4. Reduce what you need to download</h2> | |
| 24 | +<p>The fastest download is the one you skip. A few habits cut transfer time:</p> | |
| 25 | +<ul> | |
| 26 | +<li><strong>Keep popular maps installed.</strong> If <code>de_dust2_2x2</code> or a common surf map is already in <code>cstrike/maps/</code>, you download nothing for it. Community map packs are worth keeping.</li> | |
| 27 | +<li><strong>Do not delete downloaded content.</strong> Files you pull once stay in <code>cstrike/</code> (and in <code>cstrike/downloads/</code> on newer builds) so the next visit is instant.</li> | |
| 28 | +<li><strong>Rejoin rather than reconnecting repeatedly.</strong> A timeout mid-download can leave a partial file; a clean reconnect resumes cleanly.</li> | |
| 29 | +</ul> | |
| 30 | + | |
| 31 | +<h2>5. Rule out your own connection and disk</h2> | |
| 32 | +<p>If <em>every</em> server is slow, including ones you know run FastDL, look closer to home: a saturated connection (something else downloading), a VPN adding latency, or a nearly full disk that cannot write the files quickly. FastDL downloads ride your normal internet speed, so a slow line shows up here too.</p> | |
| 33 | + | |
| 34 | +<h2>6. What the two transfer paths look like</h2> | |
| 35 | +<p>It helps to picture the two routes a file can take. The <strong>legacy path</strong> is the file coming down the same UDP game channel you connect over; the engine deliberately rate-limits it to a trickle so downloads cannot swamp live gameplay for everyone else, which is why a big map crawls. The <strong>FastDL path</strong> is an ordinary HTTP GET to the operator's mirror — the same kind of request your browser makes — so it runs at your real line speed and does not touch the game channel at all. Both paths are triggered automatically by the same missing-file list; you never choose between them, the server's configuration does. That is the whole reason "why is this server slow when that one is instant" has nothing to do with your settings: one operator set up a mirror and the other did not.</p> | |
| 36 | +<p>One more thing worth knowing: files you download are cached on disk, so the pain is a one-time cost per piece of content. Visit the same map server twice and the second join skips the download entirely. Deleting your <code>cstrike/downloads/</code> folder or the map files to "clean up" simply forces every slow transfer again, so leave downloaded content in place.</p> | |
| 37 | + | |
| 38 | +<h2>Troubleshooting</h2> | |
| 39 | +<ul> | |
| 40 | +<li><strong>Stuck on "Verifying and downloading resources" then disconnected</strong> — the file is large, the server has no FastDL, and you hit the connection timeout. Try again; partial files resume. If it never finishes, the server's transfer is simply too slow.</li> | |
| 41 | +<li><strong>Spawn with missing textures or ERROR models</strong> — <code>cl_allowdownload 0</code>, or the server disabled downloads with <code>sv_allowdownload 0</code>. Set your cvar to 1; the server side is out of your hands.</li> | |
| 42 | +<li><strong>"Missing map, disconnecting"</strong> — the download failed or was blocked and the map is not on disk. Re-enable downloads, or install the map manually.</li> | |
| 43 | +<li><strong>One server slow, others fast</strong> — that server has no FastDL mirror. Nothing you can change client-side.</li> | |
| 44 | +<li><strong>All servers slow</strong> — your connection, a VPN, or disk, not CS. Test a normal web download to compare.</li> | |
| 45 | +</ul> | |
| 46 | + | |
| 47 | +<h2>Verification</h2> | |
| 48 | +<p>Check your client cvars in the console:</p> | |
| 49 | +<pre>cl_allowdownload | |
| 50 | +cl_allowupload</pre> | |
| 51 | +<p>Both should read 1. Then join a busy modern community server that you know runs FastDL and watch a custom map pull in seconds rather than minutes — if it is fast there but slow elsewhere, you have confirmed the difference is server-side FastDL, exactly as expected. If it is slow everywhere, the bottleneck is your own connection.</p> | |
| 0 | 52 |
