Skip to content

CS2FOW 0.3.0

Latest

Choose a tag to compare

@karola3vax karola3vax released this 22 Jul 12:59
Immutable release. Only release title and notes can be modified.

CS2FOW 0.3.0

This is the next public CS2FOW release after 0.2.4-preview. You can update directly from 0.2.4 to 0.3.0; the unpublished versions in between are already included and do not need to be installed.

CS2FOW 0.3.0 supports the current public CS2 build 24304127 (1.41.7.2) on Windows and Linux servers.

Update from 0.2.4

  1. Stop the server.
  2. Update the CS2 server and Metamod:Source.
  3. If you changed game/csgo/cfg/cs2fow.cfg, save a copy of it.
  4. Download the 0.3.0 core ZIP for the server's operating system: Windows or Linux.
  5. Extract the ZIP directly into the server's game/csgo folder and allow it to replace the old CS2FOW files.
  6. If you saved a customized config, copy your chosen values into the new cs2fow.cfg. Keep the new cs2fow_worker_threads 2 line unless you have a reason to change it.
  7. Start the server, load a map, and run cs2fow_status in the server console.

The ZIP already contains the correct addons, cfg, and tools folders. After extraction, they must be directly inside game/csgo, not inside another nested CS2FOW folder.

No uninstall, client download, database change, or intermediate CS2FOW version is required. Existing 0.2.4 settings still work.

Official maps

If the 0.2.4 official-map package is already installed and working, keep it; the same 23 validated map files are used by 0.3.0. New installations can extract cs2fow-0.3.0-official-maps.zip into the same game/csgo folder.

What server owners will notice

  • More accurate player visibility. CS2FOW now checks the player's complete animated CS2 hitbox shape instead of a small collection of hand-placed dots. A genuinely visible part of the player can reveal the whole player more reliably around corners, stairs, railings, and narrow gaps.
  • Much better performance on full servers. The live 32-player test reduced visibility-worker time by about 25% and cut tested map triangles by about half compared with the first capsule implementation.
  • Two visibility workers by default. Work is shared across two background threads. The allowed range is one to four, but most owners should leave cs2fow_worker_threads 2 unchanged.
  • Clearer diagnostics. cs2fow_status now shows real elapsed worker time, combined CPU work, recent slow frames, cache use, and the shortcuts that avoided unnecessary work.
  • Stronger failure safety. Missing animation data, uncertain visibility, worker failure, or an expired time budget still leaves the player visible instead of risking an incorrect hide.

Smoke blocking, HE smoke clearing, optional teammate filtering, full player-equipment grouping, automatic map baking, and the fail-open safety model continue to work as before.

Visibility Studio was also updated to reflect the new runtime and is for local development only. Server owners do not install or run Studio.

Confirm that it works

Run:

cs2fow_status

The first line should say active and show the loaded map. If it says the server fingerprint does not match, finish updating CS2 and restart the server. If the command is unknown, check that Metamod:Source is current and that the ZIP was extracted into the correct folder.

Release files

  • cs2fow-0.3.0-windows-x86_64.zip — Windows servers
  • cs2fow-0.3.0-linux-x86_64.zip — Linux servers
  • cs2fow-0.3.0-official-maps.zip — optional for new installations
  • SHA256SUMS.txt — file-integrity checksums
  • v0.3.0-manifest.json — verified build and artifact information

Validation

  • Valve's current Windows server.dll and Linux libserver.so exactly match the packaged gamedata fingerprints for CS2 build 24304127.
  • The Windows and Steam Runtime Linux builds pass the complete runtime test suite.
  • Package contents, checksums, official-map pairs, and fail-open visibility behavior pass automated validation.
  • The final live 32-player benchmark completed without budget exhaustion, cache saturation, missing capsule data, or incorrect visibility decisions.

Compiled ZIPs are distributed only as GitHub Release assets and are not stored or linked from the README.