You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Ivan Avdeev 7d6c12218f vk: comment on why we need inverse model matrix 3 weeks ago
.github ci: disable nswitch and psvita targets 1 month ago
3rdparty mainui: update 1 month ago
Documentation engine: common: soundlib: add support for MP3 looping through custom ID3v2.4.0 tagging 2 months ago
common Merge upstream master 1 month ago
contrib/mittorn contrib: remove my personal qtcreator project, as I'm using compile_commands.json support now 4 years ago
engine Merge upstream master 1 month ago
filesystem filesystem: add size argument to COM_Default/ReplaceExtension calls 1 month ago
game_launch wscript: allow to setup engine default gamedir during configure 9 months ago
pm_shared Trim all trailing whitespace 2 years ago
public public: restore unused, removed in upstream Matrix4x4_SetOrigin. Actually used in Vulkan fork 1 month ago
ref vk: comment on why we need inverse model matrix 3 weeks ago
scripts Merge upstream master 1 month ago
utils utils: mdldec: add size argument to COM_FileBase calls 1 month ago
.cirrus.yml ci: upgrade freebsd tasks 1 year ago
.editorconfig editorconfig: initial add 4 years ago
.gitattributes Add .gitattributes to enforce Git write normal human file endings and show pretty diffs for C and Python 2 years ago
.gitignore Merge remote-tracking branch 'upstream/master' into merge-from-upstream-2023-02-16 4 months ago
.gitmodules 3rdparty: add xash-extras submodule 9 months ago readme: sligthly update contributing guidelines 4 years ago Update 3 months ago
waf waifu: upgrade to latest revision 2 months ago
waf.bat waf.bat: use unicode charset 10 months ago
wscript Merge upstream master 1 month ago

Vulkan plus Ray Tracing (RTX) temporary fork of Xash3D FWGS engine

GitHub Actions Status


  • This fork adds Vulkan renderer to Xash3D-FWGS engine.
  • This is work-in-progress. It is in early stages and is not ready for unsupervised usage.
  • Vulkan renderer targets two different modes:
    • Traditional rasterizer. It is intended to produce pixel-perfect identical frames to existing GL renderer as possible.
    • Ray tracing. It implements real time path traced global illumination lighting with PBR materials. It will look noticeably different from original game.
  • It is intended to be merged back into upstream/master when it gets mature and stable enough.
  • Ray tracing requires 64-bit build. 32-bit drivers do not expose vulkan ray tracing extensions.
  • For more information, check out the wiki.
  • Page on Mod DB (screenshots, etc).

Current status

  • See Issues and ref/vk/
  • Traditional rasterizer works with some issues.
    • Works on Windows and Linux with any Vulkan GPU (and at some point it worked on Raspberry Pi 4 even).
    • It is slower than OpenGL renderer (1. I suck at Vulkan. 2. No visibility culling is performed).
    • Some features are not implemented yet.
  • Ray tracer mostly works too, with dynamic GI and stuff.
    • It also requires material remaster (i.e. newer textures for PBR parameters) and missing RAD files for most of the game maps.
    • Works under both Windows and Linux.
    • Works on both AMD and Nvidia GPUs.
  • If you feel adventurous, you can follow build instructions. Note that they might be slightly out of date, kek.

Follow development

This project is 99.999% developed live on stream. I'm not a graphics programmer, and have no idea what I'm doing. I'm essentially learning Vulkan, game engine renderer development, linear algebra, and ray tracing techniques while getting hands dirty with this. This is all for your amusement.

You can watch me making a fool of myself publicly here:

Regular upstream Xash3D follows.

Xash3D FWGS Engine

GitHub Actions Status FreeBSD Build Status Discord Server
Download Stable Download Testing

Xash3D FWGS is a fork of Xash3D Engine by Unkle Mike with extended features and crossplatform.

Xash3D is a game engine, aimed to provide compatibility with Half-Life Engine, 
as well as to give game developers well known workflow and extend it.
Read more about Xash3D on ModDB:

Fork features

  • HLSDK 2.4 support.
  • Crossplatform: supported x86 and ARM on Windows/Linux/BSD/Android. (see docs for more info)
  • Modern compilers support: say no more to MSVC6.
  • Better multiplayer support: multiple master servers, headless dedicated server.
  • Mobility API: allows better game integration on mobile devices(vibration, touch controls)
  • Different input methods: touch, gamepad and classic mouse & keyboard.
  • TrueType font rendering, as a part of mainui_cpp.
  • Multiple renderers support: OpenGL, GLESv1, GLESv2, Software.
  • Voice support.
  • External filesystem module like in GoldSrc engine.
  • External vgui support module.
  • PNG image format support.
  • A set of small improvements, without broken compatibility.

Planned fork features

  • Virtual Reality support and game API.
  • Vulkan renderer.

Installation & Running

  1. Get Xash3D FWGS binaries: you can use testing build or you can compile engine from source code.
  2. Copy engine binaries to some directory.
  3. Copy valve directory from Half-Life to directory with engine binaries. If your CPU is NOT x86 compatible or you're running 64-bit version of the engine, you may want to compile Half-Life SDK. This repository contains our fork of HLSDK and restored source code for some of the mods. Not all of them, of course. You still needed to copy valve directory as all game resources located there.
  4. Run the main executable (xash3d.exe or AppImage).

For additional info, run Xash3D with -help command line key.


  • Before sending an issue, check if someone already reported your issue. Make sure you're following "How To Ask Questions The Smart Way" guide by Eric Steven Raymond. Read more:
  • Issues are accepted in both English and Russian
  • Before sending a PR, check if you followed our contribution guide in file.

Build instructions

We are using Waf build system. If you have some Waf-related questions, I recommend you to read

NOTE: NEVER USE GitHub's ZIP ARCHIVES. GitHub doesn't include external dependencies we're using!


If your CPU is x86 compatible, we are building 32-bit code by default. This was done to maintain compatibility with Steam releases of Half-Life and based on it's engine games. Even if Xash3D FWGS does support targetting 64-bit, you can't load games without recompiling them from source code!

If your CPU is NOT x86 compatible or you decided build 64-bit version of engine, you may want to compile Half-Life SDK. This repository contains our fork of HLSDK and restored source code for some of the mods. Not all of them, of course.

Windows (Visual Studio)

  • Install Visual Studio.
  • Install latest Python OR run cinst python.install if you have Chocolatey.
  • Install latest Git OR run cinst git.install if you have Chocolatey.
  • Download SDL2 development package for Visual Studio.
  • Clone this repository: git clone --recursive
  • Make sure you have at least 12GB of free space to store all build-time dependencies: ~10GB for Visual Studio, 300 MB for Git, 100 MB for Python and other.


  • Enable i386 on your system, if you're compiling 32-bit engine on amd64. If not, skip this

$ sudo dpkg --add-architecture i386

  • Install development tools
    • For 32-bit engine on amd64:
      $ sudo apt install build-essential gcc-multilib g++-multilib python libsdl2-dev:i386 libfontconfig-dev:i386 libfreetype6-dev:i386
    • For everything else:
      $ sudo apt install build-essential python libsdl2-dev libfontconfig-dev libfreetype6-dev
  • Clone this repostory: $ git clone --recursive


Windows (Visual Studio)

  1. Open command line
  2. Navigate to xash3d-fwgs directory.
  3. Carefully examine which build options are available: waf --help
  4. Configure build: waf configure -T release --sdl2=c:/path/to/SDL2
  5. Compile: waf build
  6. Install: waf install --destdir=c:/path/to/any/output/directory


If compiling 32-bit on amd64, you may need to supply export PKG_CONFIG_PATH=/usr/lib/i386-linux-gnu/pkgconfig prior to running configure.

  1. Examine which build options are available: ./waf --help
  2. Configure build: ./waf configure -T release (You need to pass -8 to compile 64-bit engine on 64-bit x86 processor)
  3. Compile: ./waf build
  4. Install(optional): ./waf install --destdir=/path/to/any/output/directory