W40KRT_VR 0.9.80 beta

Warhammer 40K: Rogue Trader VR expands its tabletop VR experience with a dedicated launcher, broader headset setup, direct interface layout controls, and improved camera-follow behavior.

Highlights

• One shared installer and a dedicated VR launcher. The same INSTALL.cmd installs the mod for every supported headset; there are no separate headset-specific installers. Then use LAUNCH-VR.cmd or the installed Rogue Trader VR shortcut to select the headset, connection, runtime, rendering mode, DLSS quality, and optional OFXR.
• Expanded headset paths. Meta Quest supports Virtual Desktop/VDXR and Meta Quest Link/Air Link. PICO 4 and PICO 4 Ultra use Virtual Desktop/VDXR. Pimax Dream Air and Dream Air SE SLAM use Pimax Play native OpenXR.
• Configurable camera following. Automatic follow recentering starts off, allowing right-stick party movement to retain the current tabletop height, angle, and scale. The 0.9.79 framing behavior remains available as an option.
• Interface position and size controls. HUD, management screens, maps, control hints, and the F1 menu can be adjusted directly from the main VR settings. F1 has independent offsets and improved fitting within both eyes.
• Clearer native hints. Tutorial panels use their complete bounds for improved placement and legibility.
• Star-map controls. The warp-route Star map uses its native right options bar, while the system/planet map keeps its right wheel.
• Safer startup diagnostics. Runtime/GPU mismatch and insufficient D3D11 capability are reported separately, and startup details can be copied with Ctrl+C.
• Safer Steam startup. The launcher checks that the Steam edition can connect to Steam before saving changes or opening the game, avoiding a silent flat launch without mods.
• Preserved player choices. Updates retain existing settings, custom layouts, and the selected DLSS DLL. A clean installation receives the revised default layout.

Installation and launch

1. Download and extract W40KRT_VR-0.9.80-beta.zip into a new folder.
2. Close Rogue Trader and run the shared INSTALL.cmd, regardless of which supported headset you use.
3. Open Steam normally and sign in.
4. Connect the headset and controllers through Virtual Desktop, Meta Quest Link/Air Link, or Pimax Play as appropriate.
5. Run LAUNCH-VR.cmd, or use the installed Rogue Trader VR shortcut.
6. Review the detected game folder and runtime, choose the preferred rendering options, and press Launch game.

The game uses its built-in mod loader; a separate Unity Mod Manager installation is not required. Starting the game normally through Steam or its executable remains flat. The launcher checks the Steam connection and then starts WH40KRT.exe directly with the VR flag; it does not launch the Steam client. It applies the selected OpenXR runtime only to the game process and does not change Windows OpenXR settings or NVIDIA profiles.

Compatibility

This beta targets the Steam edition of Warhammer 40,000: Rogue Trader, 64-bit Windows 10/11, DirectX 11, and OpenXR.

The listed Meta Quest 3, PICO 4/4 Ultra, and Pimax Dream Air/Dream Air SE SLAM paths have been physically validated. PICO Connect, legacy PimaxXR, eye tracking, Quad Views, and Lighthouse controllers are outside this release.

Beta limitations

Combat frame-time fluctuations remain under investigation, and this release does not claim an FPS improvement. Some Meta configurations may stop at Preparing VR when the GPU selected by the game does not match the runtime or does not provide the required D3D11 capability; the new diagnostics distinguish these cases but do not claim to resolve every hardware configuration. Dialogue layout and hyperlinks are unchanged in this version. Controller tilt can still become limited in an as-yet unidentified situation.

OFXR remains experimental, optional, and disabled by default. It may improve perceived smoothness, but results depend on the PC, scene, and configuration and may include artifacts or additional latency.

The final package passed installation, update, reinstall, removal, settings-preservation, launcher-policy, process, and integrity checks. The direct VR launcher and the listed Meta, PICO, and Pimax paths were physically validated. Compatibility can still vary with unlisted hardware, software versions, and connection configurations.

SHA-256: 0B4E26AE1791F8B6D991A3D3D511ADDCA702018FC5174A36C08696D347FADCFA