GraphicsOverdrive

⚡ GRAPHICS OVERDRIVE ⚡

Basic and Expert Modes, 120+ Graphics Settings, Full FSR 3 Upscaling & Frame Generation and Hardware Ray Tracing in Valheim

🐧 Developed and Tested on Linux

All development and testing of Graphics Overdrive was done on Linux: the native Linux version of Valheim on Vulkan, with an NVIDIA GeForce RTX 4070 (laptop GPU).

• Windows: the Windows libraries are built from the same source and included, but they have not been through the same testing. A Windows tester has confirmed the Native Door and DLSS on a GeForce RTX 5070 laptop GPU (1.0.2). If something misbehaves on Windows, please report it with your logs (see "Logs" and "Windows: how the layer is loaded" in the FSR 3 section).
• Windows, Native Door not starting: another Windows player's game ran on Vulkan, but the Vulkan loader never picked up the Native Door's layers, and nothing said why (the player has since confirmed it: the game ran with administrator rights). That report led to the loader check and the registry fallback of 1.1.4. Both are Windows-only code that could not run on Linux, so their first real run is on a Windows PC. If FSR 3, DLSS or ray tracing are missing with -force-vulkan, read the settings page: it now says why the Native Door did not start. A game with administrator rights (a Steam or Gale started "as administrator", or a Windows build with User Account Control switched off, where every program runs that way) is the most likely cause, and the Native Door now takes the registry route by itself on such a PC.
• AMD and Intel GPUs: FSR 3 is made to run on them, but they have not been tested.
• FSR 1 on Windows: a Windows tester has confirmed FSR 1 on integrated graphics (Intel HD Graphics 4600) (1.1.3). Other Windows GPUs have not been tested: if the picture looks wrong, pick Vanilla on the Scaler row and please report it.

✨ What's new in 1.1.4

• Windows: the Native Door checks that the Vulkan loader really sees its layers, and says why when it does not. On some Windows PCs the game runs on Vulkan and the Vulkan loader still never picks up the Native Door's layers, so FSR 3, DLSS and ray tracing are simply missing. At every Vulkan start the Native Door now asks the loader, writes what it found (administrator rights, the Vulkan variables on your PC, the loader's version, the layers it lists) into one "Windows loader check" block in patcher.log, and when the layers are not seen, the settings page names the cause.
• Windows: two repairs. A VK_LAYER_PATH on your PC that hides the Native Door's folder is extended with it. Where the loader ignores the environment variables the Native Door uses (when the game has administrator rights: a Steam or Gale started "as administrator", or a Windows build with User Account Control switched off), the layers are registered through the registry instead, only when needed and removed again as soon as the plain route works. See "Windows: how the layer is loaded" in the FSR 3 section. Nothing changes on Linux.

1.1.3 brought FSR 1, the game's own scaler sharpened by AMD FSR 1, for every graphics card, Direct3D included. 1.1.2 took the 3D render scale down to 20%, also in Basic mode and with FSR 3. 1.1.1 brought the Basic and Expert menus, experimental hardware ray tracing on Vulkan, display settings in F11 and texture pack fit for big HD packs.

Fixes are listed in the changelog.

🌌 The Problem: Valheim Leaves Most of Its Own Graphics Dials Locked

Valheim runs on Unity 6000's Built-in Render Pipeline with Post Processing Stack v1. The engine and the game ship far more dials than the settings menu shows:

• Dormant Screen-Space Reflections: Post-Processing Stack v1 contains a raymarched SSR engine, but Valheim leaves it switched off. Wet stone, metal and polished armor get flat reflections.
• Downsampled Ambient Occlusion: SSAO is rendered below native resolution.
• Tiny Streaming Buffers: Async GPU uploads default to a 4 MB buffer and a 2 ms time slice, which can show up as stutter and pop-in when crossing zo