Ghost Recon Wildlands VR (GRW-XR)

English | Deutsch | 한국어

A native OpenXR VR mod for Tom Clancy's Ghost Recon Wildlands (AnvilNext 2.0, DirectX 11). Head-tracked stereoscopic 3D rendered by the game's own engine and injected through a dxgi.dll proxy. No game files are modified, ever.

Important

YOU MUST DISABLE UBISOFT CONNECT OVERLAY AND STEAM OVERLAY OR THIS WILL CRASH!!!!! The Ubisoft Connect in-game overlay freezes the mod's first frame (black screen, then the game closes); the Steam overlay is suspected too. install.bat (v0.13.0) reads both settings and warns you. Ubisoft Connect: Settings, General, untick the in-game overlay. Steam: Settings, In Game, untick the overlay, and untick it in the game's Properties as well.

Download: v0.13.0, the body (GRW-XR-0.13.0.zip): unzip anywhere, run install.bat, read INSTALL.txt.

Reset in the headset: hold the LEFT MENU button for about a second, standing straight. That recentres the view, zeroes the lean and takes your standing height for the crouch. A short press is still the game menu.

Warning

SINGLEPLAYER OR PRIVATE CO-OP ONLY, never PvP, never matchmaking. This is a hard rule of the project and it has not changed. The 2026-08-13 title update removed Easy Anti-Cheat, and that does not loosen it: the mod is built and tested for the campaign, solo or with friends in a private session, and competitive play stays out of scope.

Note

This is not a complete VR experience yet, and v0.13.0 is the body

It is a real, playable VR mod rather than a proof of concept: stereo depth, a fullscreen head-tracked view, first person that turns itself on, your head and helmet hidden, the game's own weapon in your hands, and rounds that go where the barrel points. All of that has been played in a headset.

Weapon tracking is markedly better than it was. The weapon follows your controller in position and rotation, one to one - it is the game's own weapon, not an overlay - it is held at the pistol grip rather than the stock, and rounds leave its muzzle and go where it points rather than where you are looking. A green dot shows you where the barrel is aimed. That last part was the project's largest open problem for months.

v0.13.0 adds the body: your upper body turns with your head, you lean, step and crouch with your real body, the view is level, and recoil kicks the gun and hands, not your head. Cars, bikes and boats work in first person; helicopters and planes still show the outside camera.

There are still rough edges and they are listed honestly below. Holsters and gesture reload are next. A magnified scope fitted to a weapon does not work yet. The mod is right-handed only for now.

Each release has closed more of that list than it has opened, and the Roadmap says exactly where every piece stands: what works, what is being fixed, and what is coming.

Tip

Testers wanted

This has been built and tested largely on one machine, and the most useful thing anyone can do is run it on a different one. Other GPUs, other headsets, other runtimes, AMD and Intel cards, and the Ubisoft Connect and Epic editions are all thinly covered or not covered at all.

Especially wanted: anyone the mod has never worked for. Startup failures have been the hardest thing to chase precisely because they do not happen here, and every log sent in has moved it forward - the crash work in v0.11.1 exists because of them.

Open an issue with your GPU, headset and runtime, what you did and what happened, and attach GRWVR\grwxr-<numbers>.log - the one with digits in the name. Reports that it simply worked are just as useful as reports that it did not.

Which game version

Game update	TimeDateStamp	Supported
late-July 2026	6A692948	yes
2026-08-13 ("Last Rites")	6A75F2F4	yes
2026-08-19	6A7C5143	yes, and this is the current one

The mod pins itself to executables it recognises and never guesses at addresses. On an unrecognised build it installs nothing and logs build pin: UNKNOWN GRW.exe binary while the game runs flat. That is the check working, not a crash.

English only for now. The German and Korean pages above were contributed by community members and describe an earlier release; updated translations are planned rather than abandoned, and the thanks in Credits stand regardless.

See CHANGELOG.md for what changed between versions, and the Roadmap below for what is coming and how close it is.

The 2026-08 game updates: honest status

Ubisoft shipped three executables in quick succession in August 2026. The mod locates engine code at specific addresses inside GRW.exe, so a new executable means every address must be re-derived and re-verified before anything is written. This release carries verified tables for all of them, plus the two 2023 builds:

Table	TimeDateStamp	How it was derived
Steam 2023-09-14	(2017 lineage)	original derivation, headset-confirmed
Epic / Ubisoft Connect 2023-09-08	(2017 lineage)	machine-verified offline, never headset-confirmed by a store user
late-July 2026 update	6A692948	full re-derivation, headset-confirmed 2026-08-08 (this is what v0.7.0 was)
2026-08-13 "Last Rites"	6A75F2F4	full re-derivation, shipped in the v0.9.0-test1 zip, new to this repository's source
2026-08-19 update	6A7C5143	new in this release. An offline byte comparison proved the patch re-stamped and re-wrapped the executable without moving anything the mod uses: all 51 pinned sites are byte-identical at the same addresses, and the head-setter signature still hits exactly once, on the same function

The mod identifies which one it is running inside from the executable's own headers, and every install still verifies the bytes at the address at runtime before writing. A wrong assumption refuses to arm rather than patching the wrong thing.

What was restored on the newer executables:

• Head hiding in first person. Out since v0.7.0 because the engine's head-visibility function had been recompiled rather than moved. Re-derived 2026-08-15 by constraining on a class method table with a slot-function fingerprint that occurs exactly once in the 411 MB executable, and corroborated against the verified 2017 original. It arms on both current executables.
• The first-person head-bone anchor, re-confirmed in the headset on the 2026-08-19 build on 2026-08-22.

What is still not derived on the newer executables, and therefore stays off rather than guessing: the on_calc_mvp camera entry point and the projectile-spawn function. Both were recompiled, not merely moved. Nothing depends on them in a shipped feature.

Recommended settings for the current game version: the August updates added FSR upscaling; keep FSR off while using the mod (it sits inside the render path the mod manages, untested and likely to blur the eyes). The native immersion toggles (reduced highlight glow, throwable sightline preview off, hidden-UI sounds) work fine and are recommended for VR.

If something misbehaves on your game version, please report it with your GRWVR\grwxr-<pid>.log. Nothing silently guesses: every feature that could not be verified either disabled itself or is listed here.

What works

• Native OpenXR session on the game's own D3D11 device, paced by the headset (72 Hz)
• Full head tracking driving the actual game camera, with the render-time pose submitted to the compositor so rotation stays smooth under alternate-eye rendering
• Stereoscopic depth via alternate-eye rendering: the engine renders one eye per frame, alternating, with per-eye swapchains and correct per-eye frustum placement
• Fullscreen view: the mod overrides the game's rendered field of view (default 1.92 rad, about 110 degrees) so the image fills the headset instead of appearing as a window. On by default, toggleable and tunable live.
• 4K internal rendering, no desktop changes required. The mod sizes the game's swapchain and reports a 4K client area to the engine, so the whole pipeline renders at 3840x2160 and the capture is sharp from an ordinary 1080p desktop. The render size is a config key, so it doubles as the quality-versus-frame-rate knob.
• Touch controllers work as an EMULATED GAMEPAD, so no physical gamepad is needed. Sticks, triggers, grips, A/B/X/Y and menu are translated into ordinary gamepad input. This is gamepad emulation, NOT motion control: it is reliable and convenient, and it is not what "VR motion controllers" normally means.
• THE WEAPON FOLLOWS YOUR CONTROLLER, position and rotation, one to one. The gun is the game's own weapon, placed by writing the bone the engine mounts it on, at the instant the engine reads that bone. Rounds leave its muzzle and go where it points; see "Motion controls: exactly where this is".
• The magnified overlay, for shooting at range. Click the left thumbstick (L3) and a magnified picture of whatever the barrel is pointing at appears on the weapon, large enough to aim through. Built for iron sights and red dots.
• Two-handed weapon handling. Your rear hand sets where the weapon is, your front hand sets where it points, and twisting your wrist rolls it about its own barrel.
• An in-headset settings panel (F1). Driven with the controller, so settings that can only be judged by feel while moving can be changed without taking the headset off. The panel polls the controller itself rather than waiting on the game, which is what finally made it usable.
• Whole-config presets on the numpad. Drop complete copies of grwxr.cfg into GRWVR\presets\ and the numpad digits load one each, ten keys per bank, with the panel paging between banks. Each load announces its name and logs a key-by-key diff of what changed.
• Spoken feedback (optional, voice = 1). The mod can say what it just did through Windows' own speech voice, so a key press confirms itself when you cannot see a log.
• Hand markers: two coloured dots drawn where your controllers actually are, with real stereo depth.
• True first person, anchored to your head bone. A toggle moves the viewpoint onto the player character's actual animated head bone: eye height tracks standing, crouch and prone automatically, the camera stays glued to the head while moving, and the player is identified through the engine's own player component so it attaches to your body rather than to a nearby NPC.
• Your character's head is hidden in first person, using the engine's own head-visibility mechanism, so you no longer see hair or helmet geometry from inside. It is hidden at all times, in every state, with no key to press and no aiming needed, and it holds through movement, firing and cover.
• The first-person close-range body blur is REMOVED. Your chest, arms and weapon no longer smear when the camera sits at the character's head. This was the top complaint from earlier builds.
• Resilient VR startup. If the headset is asleep when the game launches, the mod now waits and arms itself the moment the headset wakes; no relaunch needed.
• Continuous 1:1 head aim (optional, Numpad Decimal). Your head's yaw and pitch feed the game's own aim path, so the view, reticle and bullets all follow your gaze exactly, while the right stick still turns underneath you. Aiming down sights pauses it so scopes stay true.
• Scoped aiming: while scoped, the mod steps aside so the scope renders exactly as the flat game and bullets land on the crosshair. Magnified optics are displayed across a comfortable window so they actually magnify instead of shrinking to their true angular size.
• Config GUI and hot reload. All tuning lives in GRWVR\grwxr.cfg, re-read about one second after any save, and tools\cfg_gui\cfg_gui.exe is a standalone slider editor. Whatever is live is whatever grwxr.cfg says, always: the panel, the hotkeys and the presets all work by changing that one file.
• A cropped, non-alternating desktop mirror suitable for recording
• Stable at 72 fps on the test system through extended open-world play

Motion controls: exactly where this is

This section is deliberately blunt in both directions, because motion controls are the thing people care about most and the easiest thing to overstate.

What now works, confirmed in the headset

The weapon follows your controller, one to one, in position and rotation. Point your hand and the gun points there. Move your hand and the gun moves with it. You can raise it, lower it, swing it across your body. It is not a floating overlay or a cosmetic model: it is the game's own weapon, placed by the game's own systems, being told where to go.

Getting there meant finding, and confirming in the headset one at a time: that the weapon can be moved at all, which of the character's bones actually carries it, which axis of that bone is the barrel, and then setting that barrel onto the controller's ray directly rather than nudging it relative to where the game was already aiming. Two of those four had previously been assumed, and both assumptions turned out to be wrong, which is most of why this took as long as it did.

Two-handed handling

A long gun can be held in two hands: the rear hand sets where it is, the front hand sets where it points, and your wrist rolls it about the barrel.

It ships on, and it is the part of the build most worth trying.

Earlier releases described a bug here as the hold flipping at random on hand jitter. A measured run has refuted that reading: when it does misbehave it is consistently inverted, and the reason is that the mod has no test for whether your off hand is on the weapon at all, only how far apart your hands are. Anywhere between roughly 12 cm and 45 cm of separation, "my left hand happens to be there" and "my left hand is on the handguard" look identical to it. The fix is an actual on-weapon test and it is being built. If it bothers you in the meantime, wgun_twohand = 0 gives you a one-handed hold.

What is still coming

Rounds go where the barrel points. This was the project's biggest open problem for months and it is solved: the weapon fires down its own muzzle rather than down your gaze, confirmed on both axes in a headset, with a green dot showing you where the barrel is aimed. You can shoot from the hip and hit what you are pointing at.

Your hands hold the weapon, at the pistol grip. Forearms are deliberately hidden rather than shown wrong. There is no gesture-based weapon manipulation: no grabbing, no gesture reloads, no physical mag changes. Reload, swap and vehicle entry are ordinary button presses. The mod is right-handed only for now.

Everything else about the controls

Beyond the weapon, your Touch controllers are still read as an emulated gamepad: sticks, triggers, grips and face buttons become ordinary gamepad input, so no physical controller is needed. Your head aims and looks at 1:1, and two hand-position markers are drawn where your controllers are, with real stereo depth.

That part is gamepad emulation rather than motion control, and this README will not call it anything else. Turning the weapon feature off (wgun = 0 in the config) gives you exactly the v0.7.0 behaviour back.

The magnified overlay is how you shoot at range. Hold the left trigger and a magnified picture of what the barrel is pointing at appears on the weapon. It is built for iron sights and red dots and works well on those; a magnified scope fitted to the weapon shows you the scope body instead, so fit iron sights or a red dot for long shots. A real scope picture is being worked on.

Why this takes the time it takes

Wildlands is a closed 2017 AAA engine with no source, no SDK, no mod API and an anti-tamper layer, and it is a third-person game with no first-person rig to borrow from. Nothing about how it places a weapon, aims a shot or poses a skeleton is documented anywhere. Every address the mod uses was recovered by reading the shipped executable, and every one is confirmed in a headset before it is trusted, because a plausible-looking wrong answer costs days to disprove.

That is also why the mod fails safe rather than guessing: if something cannot be verified on your game version, it disables itself and says so in the log instead of writing to an address it is not sure about.

Progress therefore arrives in discrete confirmed steps rather than continuously. The upside is that what is listed as working here is genuinely working, and has been watched working through a headset rather than inferred from a log.

Known limitations (honest list)

• The two-handed hold can invert when it engages. A measured run showed it is not flipping on jitter as older notes said: when it misbehaves it is consistently inverted, because the mod tests only how far apart your hands are and not whether your off hand is actually on the weapon. The real fix is an on-weapon test and it is being built. wgun_twohand = 0 gives you a one-handed hold if you would rather.
• The numpad digits load whole configs now. Before this release, most of them did nothing. Now every digit 1..9 and 0 replaces your entire grwxr.cfg with a preset file. If you have no GRWVR\presets\ folder they do nothing and the log says so, but if you do, a stray press changes everything at once. Each load says its name out loud so you know it happened. Your live config is backed up once before the first load of each session.
• Preset files must be WHOLE copies of grwxr.cfg. Loading is additive: keys a preset leaves out keep whatever the previous preset set them to, they do not reset to defaults. The mod warns and names every missing key when it loads a partial one.
• A magnified scope fitted to a weapon does not work yet. The overlay shows the scope body rather than the target. Iron sights and red dots are what the overlay is built for, and it works well on those, so fit those and take your long shots through the overlay. A real scope picture is being worked on.
• The gun may not sit exactly in your fist. It is placed at the point the engine mounts it, which is near the receiver, so it can hang slightly off your hand. A grip offset is coming; wgun_pos_scale tunes reach in the meantime.
• No gestures or physical weapon manipulation. Your hands hold the weapon, but there is no grabbing, gesture reload or physical magazine change.
• The mod is right-handed only. The aim ray and the weapon both come from the right controller. Left-handed support is a known gap and is on the roadmap.
• The camera can occasionally attach to the wrong body after a respawn or fast travel. Toggling first person off and on while facing your character re-acquires it.
• Cars, bikes and boats work in first person and follow your head. Helicopters and planes are not wired up yet and show the game's outside camera.
• Wide-angle rendering can look warped or "off" toward the edges; the projection geometry is under active tuning.
• Sky and cloud registration at wide field of view is still imperfect.
• Frame rate dips below 72 in dense towns on the test system.
• The desktop mirror shows a cropped single eye; judge the image only in the headset.
• Tested on exactly one configuration (below). Other headsets and runtimes are untested.
• If a game patch ever makes head aim turn the wrong way, flip aim_yaw_sign or aim_pitch_sign in the config (the engine's aim directions are calibrated per game build; the signs differ per axis on the current build).

Roadmap

Three buckets: what is working now, what is known broken and being fixed, and what is coming. Nothing here is a date or a promise. A line only moves into the first table once it has been watched working in a headset.

Working now

First person, by itself	Load in and wait a few seconds. No hotkey to press
The head, helmet and night vision hidden	At all times, in every state, with no aiming needed. Holds through movement, firing and cover
The weapon in your hands	The game's own weapon, held at the pistol grip, moved by writing the bone the engine mounts it on
Rounds go where the barrel points	Fired down the muzzle rather than down your gaze, confirmed on both axes, with a green dot showing you where that is. This was the project's biggest open problem for months
The magnified overlay	Click the left thumbstick (L3). Large enough to aim through as of v0.11.1. Built for iron sights and red dots
Full stereo, head tracked, 72 Hz	A wide field of view, with the sky and clouds fixed to the world
Touch controllers as a gamepad	Sticks, triggers, grips, buttons and menus, so no physical gamepad is needed
Settings you can change with the headset on	An in-headset panel on F1, and a config that reloads about a second after you save it

Being fixed

Driving	Done since v0.12: cars, bikes and boats in first person, the view following the head. Helicopters and planes are the open part
The two-handed hold	It works and ships on, and it is the part of the build most worth trying. It is not flipping on jitter as older notes said: when it does misbehave it is consistently inverted, because the mod tests how far apart your hands are rather than whether your off hand is on the weapon. A real on-weapon test is the fix
A magnified scope you can look through	A scope fitted to a weapon still shows you the scope body rather than the target. The game keeps only one camera and has no separate scope render to borrow, so the picture has to be built; the approach other VR shooters use is identified and the groundwork is in
The startup crash on some machines	A possible fix ships in v0.11.1 and needs reports from affected machines to confirm. If yours still fails, the log is what helps

Coming

Parachuting and the wingsuit	Not yet handled as its own thing. It needs its own camera behaviour rather than inheriting the on-foot one
Vehicle interiors	Helicopters and planes have not been wired up at all, and being able to lean and look around inside a cabin follows the driving fixes above
An optimization pass	A large share of every rendered frame is currently drawn outside what the lenses can physically show. Reclaiming it is understood and measured, and it buys frame rate and sharpness at once
Left-handed support	The mod is right-handed throughout: the aim ray and the weapon both come from the right controller. This needs doing before a stable release
Physical weapon handling	Gesture reloads, magazine changes and grabbing. The weapon is already in your hands, so this is a build rather than a research problem

This release (v0.11.1) carries a possible fix for the startup crash and a magnified overlay big enough to shoot through, with the two-handed hold on. The next release is about holsters and gesture reload on the new body. A public beta follows once a previously broken machine has confirmed it starts with the overlays off.

Which version of the game do I need?

The current one is fine. As of this release the mod carries verified address tables for every GRW.exe shipped in 2026, including the 2026-08-19 update, which is the build it was developed and run on. Since the late-July update, Steam and Ubisoft Connect ship the byte-identical executable, so Ubisoft Connect installs are covered by the very same tables (headset confirmation from a Ubisoft Connect user is still welcome).

The mod finds the engine's camera and projection code at specific addresses inside GRW.exe, so every distinct build of that executable needs its own verified address table. This release carries FIVE; they are listed with their provenance in "The 2026-08 game updates" above. The mod identifies which one it is running inside from the executable's own headers.

If the mod meets a GRW.exe it does not recognize (a future game patch, or a build not yet analysed), it says so in its log, names the builds it knows, and installs nothing: your game runs completely unmodified. The symptom of that state is a small flat window in the headset that does not respond to head movement, with controllers possibly still working. Check GRWVR\grwxr-<pid>.log for the "build pin:" line to confirm.

Requirements

• Ghost Recon Wildlands, any version up to and including the 2026-08-19 update, Steam or Ubisoft Connect (identical executable since the late-July update; see above). The two 2023 builds remain supported by their own address tables.
• A PC VR headset with an OpenXR runtime. Tested only on Meta Quest 3 over Link cable with the Meta Quest Link runtime.
• Asynchronous Spacewarp must be disabled (Oculus Debug Tool, set ASW to Disabled). The mod manages the stale eye itself; ASW compounds artifacts on top of it.
• A GPU with headroom: the test system is an RTX 5060 Ti 16 GB with a Ryzen 7 9700X.
• To build: MSVC x64 with the Visual Studio C++ workload (provides cl and ml64). See Building below for the exact toolchain each release used and how build.bat selects one.

Install

You do not need to build anything. Download the latest release and follow these steps.

1. Set your game resolution first. Launch the game flat once and set a resolution your card is comfortable with. Too high a setting can crash the game before the menu ever appears, and that looks exactly like the mod failing when it is not.
2. Unzip the release anywhere and run install.bat. It finds the game by itself - Steam libraries, Ubisoft Connect, or the folder it is sitting in
   • and asks you for a VR render resolution. If it cannot find the game it asks you for the path.
3. If the game lives somewhere Windows protects, such as C:\Program Files, right-click install.bat and Run as administrator. Without that the files do not copy and the game starts without the mod, with no error to tell you so.
4. Set your OpenXR runtime to the one you actually use - Meta Quest Link, Virtual Desktop (VDXR), or SteamVR - before launching.
5. Turn Asynchronous Spacewarp off (Oculus Debug Tool, or Virtual Desktop's own settings) and SteamVR reprojection off. The mod re-presents frames itself and these fight it.
6. Launch the game. First person turns itself on a few seconds after you load in. Press F1 in the game window for the settings panel.

INSTALL.txt inside the zip is the full manual: every control, every setting, the graphics baseline, troubleshooting, and how to report a problem. To remove the mod, run uninstall.bat.

If the mod has never started for you - black screen, then the game closes a few seconds later - v0.11.1 carries a possible fix for that. See the release notes, and send the log if it still happens.

The sections below are for building from source.

Building

1. Download the OpenXR SDK loader release from https://github.com/KhronosGroup/OpenXR-SDK/releases (tested with 1.1.61). Place it so these paths exist:
   • tools/xr_probe/extern/include/openxr/openxr.h
   • tools/xr_probe/extern/lib/openxr_loader.lib Keep the loader's openxr_loader.dll from the same release; you will copy it to the game folder in the install step.
2. If your Visual Studio is not at the default path, edit VCVARS at the top of build.bat.
3. Run build.bat. Output: build\dxgi.dll (the script prints its SHA256).

Build toolchain (which Visual Studio is used)

build.bat selects the toolchain in this order, using the first that exists:

1. C:\Program Files\Microsoft Visual Studio\18\Community (the project's primary build machine; every release through v0.7.0, and v0.9.1-test2, was compiled with this),
2. C:\Program Files\Microsoft Visual Studio\2022\Community (fallback).

This matters right now. The releases split by compiler:

Releases	Machine	Compiler
through v0.7.0 (worked on VD / Steam Link)	primary build machine	Visual Studio at \18\
v0.8.0, v0.8.1, v0.8.2 (startup crash on VD / Steam Link)	second machine	Visual Studio 2022 Community, MSVC 14.39.33519
v0.9.1-test2	primary build machine	Visual Studio at \18\

The startup crash is not a compiler difference. Earlier versions of this page said it probably was, and that is now ruled out: the same binary, sha for sha, plays on one machine and wedges on another. The compiler cannot be what separates them, and anyone debugging from that theory was being sent down a blind alley.

What the logs actually point at is other OpenXR API layers installed on the machine — ReShade's OpenXR layer, VIVE layers, foveation layers. Across every log sent in, the machines that die almost always have one and the machines that play have none. One machine that dies has none either, so it is a strong lead rather than a proven cause.

v0.11.1 acts on it. The mod now reads the layers actually installed on your machine and disables each one by the name that layer itself declares, instead of guessing at two names as it used to — a guess that never matched ReShade's real one, so for ReShade users that suppression had been doing nothing at all. And if a layer survives anyway, or the first frame hangs, the mod stands down and lets the game run flat instead of taking it down. If you have been unable to start the mod, that release is the one to try, and the log is what helps if it still fails.

Installing

1. Close the game.
2. If your game is not at C:\Steam\steamapps\common\Wildlands, edit GAME at the top of deploy.bat.
3. Run deploy.bat auto. It verifies the game is closed, builds, copies dxgi.dll into the game folder, creates dxgi_real.dll there (a local copy of your own C:\Windows\System32\dxgi.dll, used for export forwarding), and byte-compares the result.
4. Copy openxr_loader.dll (from the OpenXR SDK release in the build step) into the game folder next to GRW.exe.
5. Set the baseline graphics settings below.
6. Launch through Steam. The headset no longer needs to be awake before launch: the mod waits and arms itself the moment the headset wakes.

Optional: to use the numpad preset loader, make a GRWVR\presets\ folder and put whole copies of grwxr.cfg in it, named so they sort the way you want them (01-baseline.cfg, 02-wide-stereo.cfg, and so on). Numpad 1 loads the first, 0 loads the tenth. With no such folder the digit keys do nothing.

Baseline graphics settings (start here before judging anything)

This is the tested baseline. Test against it before reporting a graphics or performance problem, because two of these settings (window mode and anti-aliasing) can silently cost half the frame rate.

In-game video settings (these write to GRW.ini in Documents\My Games\Ghost Recon Wildlands):

Setting	Value	Why
Resolution / window	1920x1080, Fullscreen (WindowMode=1)	The mod renders internally at 4K regardless of the desktop size. A BORDERED window locks the game to your monitor's refresh rate and caps VR at 60
Frame rate limit	72 (FpsLimit=72)	Matches the Quest 3 refresh the mod paces to
Supersampling	0.90 (Supersampling=0.90)	1.00 exceeds the tested GPU's budget at 4K; 0.90 holds 72 fps
Anti-aliasing	SMAA or Off. NEVER any temporal (TAA) mode (AntiAliasingMode=3 is SMAA, 0 is off)	Temporal AA blends the alternating eye viewpoints into ghosting, and it is expensive: a TAA-enabled save measured a sustained drop from 72 to the low 60s
Motion blur	Off	Smears under head tracking

Two traps worth knowing, both observed on the test system:

• The game rewrites GRW.ini when you apply anything in its menus, and it has silently wiped FpsLimit doing so. After any in-game menu apply, re-check the ini.
• Old saves can carry old settings with them. A save from before this baseline loaded with TAA enabled and read as "the mod got laggy". If performance suddenly looks wrong, check the anti-aliasing setting first, then the ini.

The mod writes its runtime files to GRWVR\ inside the game folder: a per-process log (grwxr-<pid>.log) and an optional grwxr.cfg.

In the headset

The key map changed in this release. The numpad digits used to be feature toggles; they are preset loaders now, and the features they carried moved onto the F1 panel. The mod prints its own key list at startup, generated from what the keys actually do, and that log line is the authority if this table ever drifts.

Warning

Numpad 1..9 and 0 each replace your whole grwxr.cfg. They read GRWVR\presets\*.cfg in file-name order. With no presets folder they do nothing. With one, a stray press changes every setting at once.

Play keys:

Key	Action
F1	Open / close the settings panel (drive it with the controller)
F2	First person on / off. You do not need it: first person turns itself on, and the head, helmet and night vision are hidden at all times with no aiming needed
Home	Recenter (look where you want forward to be, then press)
Space	Also recenters. Note it still vaults, because the mod polls the keyboard and does not intercept it
Numpad . (Decimal)	1:1 head aim on / off (bullets follow your gaze; default off)
Numpad 1..9, 0	Load a whole preset config from GRWVR\presets\ (see the warning above)

Live tuning keys:

Key	Action
Insert	Cycle which setting the tuner is editing
Page Up / Page Down	Step that setting up / down
Delete	Reset that setting
Numpad /	World BIGGER (ipd_scale up)
Numpad *	World SMALLER (ipd_scale down)
Numpad +	Head roll into the camera (cam_pose_rot). Diagnostic: it also makes the camera fight yaw and pitch
Numpad -	Skinning palette capture (research aid)
End	Start a guided spoken test run for weapon identification (silenced by voice = 0)

Every press logs the name, the value and what it changes. Saving grwxr.cfg restores the file's values over anything a key changed.

What moved onto the F1 panel: barrel aim, trigger ADS, the eye swap and the camera pose write are Settings rows; the weapon-draw recorder and first person are Captures rows.

Touch controllers (emulated as a gamepad)

The mod merges the Touch controllers into the game as a gamepad, so the full normal control scheme works and no physical gamepad is needed: sticks move and turn, face buttons and grips act as their gamepad equivalents. To be clear, that is gamepad emulation, not motion control. The one motion-tracked addition:

Input	Action
Head	Aim: bullets follow your gaze (toggle with Numpad Decimal)
Both controllers	Hand markers: blue (left) and orange (right) dots drawn where your hands are
Right trigger, full squeeze	Fire (hold for automatic fire)
Left trigger (hold)	Aim down sights (the sight picture is at view center, which is where head aim points, so it stays true)

A physical gamepad still works if you prefer it (the Touch snapshot merges with it).

Configuration

GRWVR\grwxr.cfg in the game folder holds the persistent settings and documents every key in comments. The ones most worth knowing:

Key	Meaning
ipd_scale	Eye separation multiplier. 1.00 means your headset's measured IPD at 1 world unit = 1 metre. v0.11.1 ships 0.90, which a tester found made the scale feel right. Lower values flatten depth and make the world read larger; some people prefer that. It hot reloads, and Numpad / and * step it while you play, so find your own value with the headset on
ipd_swap	If the stereo looks wrong, try this first. 1 (the shipped value) swaps which eye gets which offset. See the note below the table
fullscreen_fov	Rendered field of view in radians (default 1.92)
upsize_width / upsize_height	Internal render size (default 3840x2160). Lower it, for example 3200x1800, to trade sharpness for frame rate
fp_head_anchor	1 (default) anchors first person to the character's head bone; 0 falls back to the origin anchor
fp_head_eye	Eye offset above the head bone, meters (default 0.10)
fp_eye	First-person eye height above the character origin, meters (fallback anchor only)
fp_anchor_side	First-person lateral centering, meters
aim_yaw_sign, aim_pitch_sign	Head-aim direction calibration (defaults -1 and +1 for the current game build; flip one only if head aim turns the wrong way on that axis)
aim_source	0 (default since v0.6.0) aim follows the head; 1 is the retired controller-aim experiment, which fights head-look
aim_ctrl_smooth	Controller-aim smoothing, 0 to 1 (default 0.35)
aim_reticle	1 (default) draws the hip-fire dot reticle; 0 hides it
xinput_touch	1 (default) merges Touch controllers into the gamepad; 0 passes through untouched
hand_markers	1 (default) draws the two hand-position dots; 0 hides them
wp_markers	0 (default in the shipped config) research aid: colored dots on the engine objects nearest the camera, used to identify the weapon's placement handle; turn on only if you are helping with that hunt
aim_steer, aim_ads, aim_fire	Controller-pointing aim, trigger ADS and trigger fire; set any to 0 to disable
wgun	The controller-tracked weapon. 0 gives you the v0.7.0 behaviour back
wgun_twohand	Two-handed hold, 1 by default. Set to 0 if the 180-degree flip bothers you
wgun_grip_fwd	Metres along the barrel: slides the gun forward or back in your fist
wgun_grip_two	Front-hand hold strength, 0 to 1
voice	1 speaks what the mod just did through Windows' own voice, 0 is silent
desktop_fov	Crop of the desktop recording view, 0 disables

Note

About ipd_swap and the shipped stereo values. A controlled A/B in the headset on 2026-08-22, toggling only this one key three times, came out in favour of ipd_swap = 1. This release ships that swap at ipd_scale = 0.90. The practical reading is that the eye sign was inverted, and that people running a very small ipd_scale because "everything looks huge" were compensating for it. This is "better", tested once, and not declared correct, which is exactly why the panel puts the swap on the first row. If it looks wrong to you, flip it and say so in an issue.

Disabling and uninstalling

• Disable temporarily: rename dxgi.dll in the game folder (to dxgi.dll.off, for example). The game then runs completely unmodified.
• Uninstall: run deploy.bat remove, or delete dxgi.dll, dxgi_real.dll, openxr_loader.dll, and the GRWVR folder from the game directory.

Rules of use

• Solo campaign only. Never use this in co-op, PvP, or any matchmaking. The 2026-08-13 title update removed Easy Anti-Cheat from the game, and that changes nothing about this rule: the mod is built and tested for the solo campaign only, and it must never run in a competitive context.
• Keep play to the campaign, solo or with friends in a private session, while the mod is under development.
• This repository ships source code only. It contains no game files, no Ubisoft binaries, and no anti-cheat components, and it never patches any file of your install; the proxy DLL sits beside the game and is loaded by normal Windows DLL search order.
• Use at your own risk. The game's anti-tamper occasionally reacts to hooks in unpredictable ways. If something looks broken, rename dxgi.dll and re-check before blaming the game or the mod.

How it works, briefly

The mod is a dxgi.dll search-order proxy. It hooks IDXGISwapChain::Present, creates an OpenXR session on the game's own D3D11 device, and locates the engine's camera and projection functions through byte-signature scanning (never hardcoded addresses; a failed scan logs loudly and leaves the game untouched). Each frame it composes the live headset rotation onto the game camera's root transform and offsets the camera position left or right of center, alternating each frame. The projection hook also overrides the game's field-of-view argument (within a band that excludes scopes, menus, and the engine's sky and reflection captures) so the engine renders the headset's coverage. Each rendered frame is copied into that eye's swapchain, drawn at its exact angular size inside a canvas shaped like the eye's real display frustum, and submitted with its stored pose; the compositor reprojects both eyes to display time. The engine therefore runs at 1x headset rate while both eyes stay continuously fed.

Credits

• mutars/anvilengine2vr (MIT): the reference implementation this project is a port of. Its per-game adapter architecture, hook targets, and porting guides are the foundation of this work.
• elliotttate/vrframework: the field guides that document the technique family for AnvilNext titles.
• dariulone/cyberpunk-vr-port (MIT): a sibling architecture for REDengine whose documented lessons on eye tagging, pose pairing, and runtime frustum correction directly informed the diagnosis of this mod's hardest bug.
• pancreations/Halo-MCC-VR (MIT): whose notes on Quest runtime double-vision behavior corroborated that diagnosis.
• Khronos OpenXR SDK (Apache 2.0): the OpenXR loader and headers.
• SolKutTeR and vrforum.de, for the thread about this mod and for bringing German-speaking players to it. That thread is the reason this README now exists in German (README.de.md).
• 아키아PhD, for the Naver Cafe post about this mod and for bringing Korean-speaking players to it. That post is the reason this README now exists in Korean (README.ko.md).
• Tom Clancy's Ghost Recon Wildlands is the property of Ubisoft. This project is not affiliated with, endorsed by, or supported by Ubisoft, and distributes none of their work.

Supporting the project

A few people have asked whether they could donate, so there is now a page for that: buymeacoffee.com/firejumper93. Entirely optional and never required: the mod is free, nothing is gated behind donations, and donating changes nothing about what you get. It just helps with tools and late nights, and it is appreciated.

License

MIT, see LICENSE. Portions derived from anvilengine2vr, Copyright (c) 2024 mutars, MIT.