A fork of OpenMW that makes Morrowind work your GPU hard again: ray-traced lighting and path-traced indirect light. The goal is a 2002 game made to look astonishing on current hardware, with its content as it stands and new light transport.
This tree is OpenMW 0.53 with a ray tracer in place of its renderer. What the engine itself is, the data path and the command line are in the upstream README. This file covers only what the fork adds, and how to get it and build it, which differ from upstream.
Huge kudos to the OpenMW developers, and to everyone who has contributed to OpenMW since 2008. Their engine inspired me to contribute to open source and to start this project, and everything here stands on their work. The full list of contributors is in AUTHORS.md.
— xxorza
Upstream OpenMW stays the host engine: cells, references, physics, scripts, animation, weather and the GUI. It no longer owns the picture. The ray tracer draws the whole image: primary visibility, shadows, direct and indirect light, sky, water and fog are ray traced on the GPU.
The ray tracer is the one renderer the game starts. No setting, launcher page or fallback reaches upstream's OpenGL renderer, which stays in the build only so that upstream's code merges as it stands.
Vanilla content and the PBR replacers made for OpenMW are read as they are. Morrowind's textures are pre-lit, so the renderer estimates the painted light and divides it out to recover materials the new light transport can use. What a replacer's companion maps add reaches the trace.
- An NVIDIA RTX card, Turing (RTX 20 series) or later, which is what the renderer is written and tested for. An AMD card, RDNA 2 (RX 6000 series) or later, starts too and draws right on a low-end AMD integrated GPU, but far too slowly there to play yet.
- Vulkan 1.4 with ray tracing pipelines, ray queries and position fetch. On a machine without them the game does not start, and its error box says what is missing and where the log is. No other renderer takes its place.
As of November 2026 it is measured on a high-end NVIDIA laptop GPU, an AMD handheld under RADV, and a low-end AMD
integrated GPU under AMD's Windows driver. On a slow GPU, [RTX] indirect lighting off saves the most.
Each release holds the game, with the launcher and the installation
wizard, as an AppImage for Linux and a zipped portable folder for Windows. Releases after v0.4.5 also carry the tools
(bsatool, esmtool, niftest, the save importer and the collision object tool), as a .tar.gz for Linux and a zip
for Windows. The editor, OpenMW-CS, is upstream's to download.
An NVIDIA RTX card may use DLSS Ray Reconstruction instead of FSR, which denoises and upscales in one pass in place
of the renderer's own denoisers. No NVIDIA code is built into or shipped with the game: the driver's NGX core is
loaded at run time, and the player supplies the DLSS feature library. The launcher's Download DLSS button links to
NVIDIA's licence beside it, fetches the library from NVIDIA's release and checks its SHA-256; a copy placed beside the
executable also works. [RTX] upscaler = auto | fsr | dlss chooses, and auto falls back to FSR when the library is
absent.
The game writes a report of every crash, and of every hang longer than 20 seconds. Once the game is gone, the log and
every dump of the session go into one file, OpenMW-crash-<time>.zip under crashes in the user data folder, and a
dialog names it. Its Report the crash button opens a new issue
filled in with the crash, and the folder, so the file can be dragged into the issue. Inside it:
openmw.log. Its last lines, which beginCrash:orHang:, say what happened and what the game was doing.- The dump: every thread's stack.
Each release publishes its symbols, -symbols.zip, beside its archive, and ./omw crash <dump> <symbols> reads a
dump, or the package, against them. [General] crash hang seconds sets the hang limit, and
OPENMW_DISABLE_CRASH_CATCHER=1 turns the catcher off.
./omw is the one way to build, on Linux and on Windows (omw.cmd), and needs Python 3.11 or later. Every library
comes from the dependency set the driver fetches, built static by vcpkg (vcpkg.json); the system keeps what the
programs open at run time, whose development files sudo env/install_ubuntu_deps.sh installs on Ubuntu 26.04 and
env/install_almalinux_deps.sh on AlmaLinux 8. On Windows, Visual Studio is all it needs.
./omw bootstrap # the pinned dependency set and CMake, into out/deps/
./omw release build
./omw release setup <Morrowind folder> # the openmw.cfg a fresh machine has none of
./omw release exec ./openmw
./omw help lists the rest: the flavours, the tests, and the harness that checks and measures the renderer without a
window.
What differs from upstream's build:
- Two compilers: on Linux the pinned Clang 23 and its lld, which the driver fetches, over GCC 15's libstdc++; on Windows MSVC from Visual Studio 2026. GCC is not supported as a compiler, and a configure refuses it.
- Pinned tools: CMake, Ninja, clang-format and the dependency set are the driver's own, fetched into
out/deps/at the versionstools/omw/pins.pynames, so every desk and CI build alike. - Flavours, not build types:
debug,release,asanandtsan, each a preset ofCMakePresets.jsoninout/<flavour>. Warnings are errors in every one. - Releases: the release flavour, with link-time optimisation (ThinLTO, and MSVC's
/GL), and the Linux AppImage built on AlmaLinux 8, in a container of it on any other system.
- The build: the details above and the reasons behind them
- Architecture: the seam, the layers, who owns whom, the order a frame is computed in
- Settings: every
[RTX]setting, the upstream settings the fork changes, and what the ray tracer declines of upstream's - The launcher's look: the palette and the style the launcher and the wizard wear
- SDL3 in place of SDL2, for display scaling on high-density and Wayland desktops.
[Video] resolutionsets the frame size, and the frame is scaled into the window.- The settings window and the launcher offer only what the ray tracer honours, with
[RTX]pages in place of the rasterizer's. - The interface scale and the font size apply while the game runs.
- A Light bolt that strikes no actor lights the surface it struck.
- A crash reporter of its own, built on Crashpad.
- Three fixes to upstream's picture that the ray tracer needed: the optimizer's merge order, the land of a map tile, and a groundcover plant's transforms.
.notes/UPSTREAM.md lists every change and the reason for it.
GPLv3, as upstream. See LICENSE.