Add 2 tutorials (2 files)
Browse Source
Daemon666 committed
parent d8da18a5a1
commit 15fdb15480c3bd25f756ab9fc5ddf7c17b26c81b
2 changed files
with 70 additions and 0 deletions
cs16-nvidia-settings/en.md
A
| @@ -0,0 +1,9 @@ | ||
| 1 | +--- | |
| 2 | +title: "Best NVIDIA Control Panel Settings for CS 1.6" | |
| 3 | +excerpt: "A per-game NVIDIA Control Panel profile for CS 1.6 that lowers latency and fixes aspect ratio: v-sync off, low latency mode, power management, scaling and threaded optimization." | |
| 4 | +category: "client" | |
| 5 | +tags: "nvidia, gpu" | |
| 6 | +image: "" | |
| 7 | +read_time: "8 min read" | |
| 8 | +--- | |
| 9 | +<p>CS 1.6 is an old OpenGL game, and the NVIDIA driver's defaults are tuned for modern titles, not for a game where the entire point is minimal latency. A dedicated per-application profile fixes the two things players actually complain about: input latency from v-sync and buffering, and a stretched or pillar-boxed image at non-native resolutions. These changes are made once in the NVIDIA Control Panel and stick per game.</p><h2>1. Create a per-application profile</h2><p>Open the <strong>NVIDIA Control Panel</strong>, go to <strong>Manage 3D settings</strong>, and switch to the <strong>Program Settings</strong> tab. Add Counter-Strike by browsing to <code>hl.exe</code> in your CS folder. Making the changes here, not under Global Settings, means they only affect CS and do not degrade other games.</p><h2>2. Kill latency: v-sync and low latency mode</h2><p>These two settings do the most for how the game feels:</p><ul><li><strong>Vertical sync</strong> — set to <strong>Off</strong>. V-sync holds finished frames back to match the monitor, adding a frame or more of delay. In a game running at hundreds of FPS this is pure latency for no benefit. Pair it with <code>gl_vsync 0</code> in-game.</li><li><strong>Low Latency Mode</strong> — set to <strong>Ultra</strong>. This minimizes the render queue so frames reach the screen as soon as they are drawn, cutting click-to-photon delay.</li></ul><h2>3. Force maximum performance</h2><p>Stop the GPU from down-clocking mid-game:</p><ul><li><strong>Power management mode</strong> — <strong>Prefer maximum performance</strong>. The default adaptive mode lets the card drop clocks when it thinks the load is light, and because CS is trivially easy for a modern GPU, the card constantly under-clocks and produces micro-stutter. Forcing max performance keeps clocks pinned.</li><li><strong>Texture filtering - Quality</strong> — set to <strong>High performance</strong>. There is no visible cost in a game this old and it removes a small amount of overhead.</li></ul><h2>4. Fix the aspect ratio and scaling</h2><p>If your 4:3 or stretched resolution looks wrong on a widescreen monitor, scaling is the lever. In <strong>Adjust desktop size and position</strong>:</p><ul><li>Set <strong>Perform scaling on</strong> to <strong>GPU</strong>, not Display. GPU scaling gives you the aspect-ratio options; display scaling hands control to the monitor, which may ignore them.</li><li>Choose the <strong>Scaling mode</strong>: <strong>Aspect ratio</strong> keeps 4:3 with black bars (pillarboxing), <strong>Full-screen</strong> stretches it edge to edge, and <strong>No scaling</strong> renders 1:1 centered. Pick the look you want — stretched vs. black bars is personal preference.</li></ul><p>For getting a true widescreen resolution into the game itself rather than stretching a 4:3 one, see the <a href="/tutorials/cs16-widescreen-resolution">widescreen resolution guide</a>.</p><h2>5. Threaded optimization and other toggles</h2><p>A couple of settings behave differently on this old engine:</p><ul><li><strong>Threaded optimization</strong> — leave on <strong>Auto</strong>, or set <strong>Off</strong> if you see stutter. Forcing multi-threading on a single-threaded engine like GoldSrc can occasionally cause hitching rather than help.</li><li><strong>Antialiasing</strong> — optional. The game is cheap enough to run high AA if you want smoother edges, but competitive players usually leave it off for maximum clarity and frames.</li><li><strong>Digital Vibrance</strong> — under <strong>Adjust desktop color settings</strong>, many players raise this (toward 60-70%) to make enemy models pop against the environment. It is a visibility preference, not a performance setting.</li></ul><h2>Common errors</h2><ul><li><strong>Settings do nothing</strong> — you edited Global Settings or pointed the profile at the wrong executable. The profile must target <code>hl.exe</code> in your actual CS install.</li><li><strong>Still capped to refresh rate</strong> — v-sync is on somewhere. Set it Off in the profile and confirm <code>gl_vsync 0</code> in game.</li><li><strong>Aspect ratio options greyed out</strong> — scaling is set to Display, not GPU. Switch to GPU scaling to unlock them.</li><li><strong>Micro-stutter despite high FPS</strong> — power management is on adaptive and the GPU is down-clocking, or threaded optimization is fighting the engine. Force maximum performance and try threaded optimization Off.</li><li><strong>Image stretched and you wanted bars</strong> — scaling mode is Full-screen. Change it to Aspect ratio.</li></ul><h2>Verification</h2><p>Apply the profile, launch the game, and confirm with the net graph that frames are unlocked and stable:</p><pre>net_graph 3</pre><p>FPS should exceed your refresh rate with no v-sync cap, and it should hold steady rather than sawtoothing (the signature of a down-clocking GPU). Check the aspect ratio looks the way you chose — bars or stretched — and that motion has no v-sync smoothness to it. If frames are still capped at exactly your Hz, v-sync survived somewhere; recheck both the profile and <code>gl_vsync</code>. One caveat worth remembering: a driver update can reset per-application profiles, so if the game suddenly feels laggy or stretched weeks later, open the control panel and confirm your CS profile still exists and still points at <code>hl.exe</code>. Combine this with a forced high <a href="/tutorials/cs16-freq-refresh-rate">refresh rate</a> for the full benefit, and with in-game <code>fps_max</code> raised above your monitor's rate so the low-latency mode always has a fresh frame to deliver.</p> |
cs16-windows-11-fixes/en.md
A
| @@ -0,0 +1,61 @@ | ||
| 1 | +--- | |
| 2 | +title: "Running CS 1.6 on Windows 11 (Compatibility Fixes)" | |
| 3 | +excerpt: "The launch options, compatibility settings and renderer changes that make a 20-year-old GoldSrc engine run cleanly on Windows 11." | |
| 4 | +category: "client" | |
| 5 | +tags: "windows-11, compatibility" | |
| 6 | +image: "" | |
| 7 | +read_time: "8 min read" | |
| 8 | +--- | |
| 9 | +<p>Counter-Strike 1.6 runs on Windows 11, but the GoldSrc engine predates every display and DPI convention modern Windows assumes. The result is a familiar set of glitches: a tiny window in the corner, black bars, an unmovable mouse, crashes on Alt-Tab, or a launch that dies before the menu. Almost all of them are fixed by a handful of launch options and compatibility flags. Here is the working set.</p> | |
| 10 | + | |
| 11 | +<h2>1. Set sane launch options</h2> | |
| 12 | +<p>Right-click Counter-Strike in Steam → <strong>Properties</strong> → <strong>Launch Options</strong>, and start with:</p> | |
| 13 | +<pre>-full -noforcemparms -noforcemaccel -noforcemspd -freq 144</pre> | |
| 14 | +<ul> | |
| 15 | +<li><code>-full</code> forces fullscreen (use <code>-windowed</code> if you prefer a window, often more Alt-Tab-stable on Windows 11).</li> | |
| 16 | +<li>The three <code>-noforcem*</code> options stop the engine overriding your Windows mouse settings.</li> | |
| 17 | +<li><code>-freq</code> sets the refresh rate to match your monitor (change 144 to your Hz). A wrong value here causes a black screen on launch, so match your display.</li> | |
| 18 | +</ul> | |
| 19 | +<p>If you get a black screen, remove <code>-freq</code> first — it is the usual culprit.</p> | |
| 20 | + | |
| 21 | +<h2>2. Fix fullscreen scaling and the tiny window</h2> | |
| 22 | +<p>Modern Windows scaling shrinks old games or letterboxes them. Fix it on the executable, <code>hl.exe</code> in the Half-Life install folder. Right-click it → <strong>Properties</strong> → <strong>Compatibility</strong> → <strong>Change high DPI settings</strong>, then tick <strong>Override high DPI scaling behaviour</strong> and set scaling performed by <strong>Application</strong>. Back on the Compatibility tab, tick <strong>Disable fullscreen optimizations</strong>. These two together resolve the small-window, wrong-scale, and Alt-Tab-crash trio for most people.</p> | |
| 23 | + | |
| 24 | +<h2>3. Choose a renderer that behaves</h2> | |
| 25 | +<p>In the game's Video options, GoldSrc offers OpenGL, Direct3D, and Software modes. On Windows 11:</p> | |
| 26 | +<ul> | |
| 27 | +<li><strong>OpenGL</strong> is the best-looking and usually the right default.</li> | |
| 28 | +<li>If OpenGL gives a black screen or crashes, try <strong>Software</strong> mode temporarily to confirm the game itself works, then troubleshoot the GPU driver.</li> | |
| 29 | +<li>Update your GPU driver — a stale or generic OpenGL driver is a common cause of a black or flickering screen on new Windows installs.</li> | |
| 30 | +</ul> | |
| 31 | +<p>You can force software mode from launch options with <code>-soft</code> to get into the menu when OpenGL will not start, then switch the renderer from there.</p> | |
| 32 | + | |
| 33 | +<h2>4. Run with the right permissions</h2> | |
| 34 | +<p>Some Windows 11 setups block the engine from writing its config or reading input properly under standard permissions. On <code>hl.exe</code> Compatibility tab, tick <strong>Run this program as an administrator</strong>. This also helps when settings will not save because the install lives under <code>Program Files</code>, which is write-protected.</p> | |
| 35 | + | |
| 36 | +<h2>5. Deal with missing-library and crash-on-launch errors</h2> | |
| 37 | +<p>If the game dies before the menu with a message like <strong>"Could not load library client"</strong> or a bare crash, the fix order is:</p> | |
| 38 | +<ol> | |
| 39 | +<li><a href="/tutorials/cs16-verify-game-files">Verify the game files</a> — a damaged DLL produces exactly this.</li> | |
| 40 | +<li>Remove all launch options, launch clean, then add them back one at a time to find the offender.</li> | |
| 41 | +<li>Update the GPU driver and the Microsoft Visual C++ redistributables.</li> | |
| 42 | +</ol> | |
| 43 | + | |
| 44 | +<h2>6. Move the install out of Program Files</h2> | |
| 45 | +<p>Windows protects <code>C:\Program Files</code> and <code>Program Files (x86)</code> with UAC virtualization, which can quietly redirect or block the writes GoldSrc makes to its own folder — config saves, downloaded content, screenshots. That is a frequent cause of settings that never persist and content that fails to download. If you keep hitting write problems, move the Steam library (and with it Counter-Strike) to a folder outside Program Files, for example <code>D:\Games\Steam</code>, using Steam's <strong>Add Library Folder</strong> and then <strong>Move install folder</strong>. An install on a plain, unprotected path behaves far better with a 20-year-old engine than one buried under Windows' protected directories, and it removes the need to run as administrator just to save a config.</p> | |
| 46 | +<p>While you are tidying, keep your personal settings in <code>cstrike/userconfig.cfg</code> rather than only <code>config.cfg</code>. The engine rewrites <code>config.cfg</code> on every exit, so a permission hiccup at shutdown can lose your edits; a hand-maintained <code>userconfig.cfg</code> you <code>exec</code> is the durable place for launch-critical settings.</p> | |
| 47 | + | |
| 48 | +<h2>Troubleshooting</h2> | |
| 49 | +<ul> | |
| 50 | +<li><strong>Black screen on launch, sound plays</strong> — wrong <code>-freq</code>, or an OpenGL/driver problem. Remove <code>-freq</code>, try <code>-soft</code> to reach the menu, update the GPU driver.</li> | |
| 51 | +<li><strong>Tiny window or black bars in fullscreen</strong> — DPI override not set. Apply the high-DPI and disable-fullscreen-optimizations steps on <code>hl.exe</code>.</li> | |
| 52 | +<li><strong>Crashes on Alt-Tab</strong> — use <code>-windowed</code> or a borderless window, and disable fullscreen optimizations.</li> | |
| 53 | +<li><strong>Mouse feels accelerated or stuck</strong> — add the <code>-noforcem*</code> options and set <code>m_rawinput 1</code> per <a href="/tutorials/cs16-sensitivity-dpi">the sensitivity guide</a>.</li> | |
| 54 | +<li><strong>"Could not load library client"</strong> — corrupt install; verify files. If it persists, a modified <code>cstrike</code> DLL is the cause.</li> | |
| 55 | +<li><strong>Settings never save</strong> — install is under Program Files; run as admin, or keep settings in <code>userconfig.cfg</code>.</li> | |
| 56 | +</ul> | |
| 57 | + | |
| 58 | +<h2>Verification</h2> | |
| 59 | +<p>Launch the game and confirm it opens fullscreen at the correct resolution and refresh rate with a normal-size, movable mouse. Alt-Tab out and back in — it should survive without crashing. Load a map to confirm the renderer is stable:</p> | |
| 60 | +<pre>map de_dust2</pre> | |
| 61 | +<p>If it renders cleanly and your mouse feels 1:1, the compatibility set is correct. If it still crashes on a freshly verified install with no launch options, the remaining suspects are the GPU driver and the VC++ redistributables rather than the game.</p> | |
| 0 | 62 |
