EDVR 0.20.0: Elite Dangerous VR Gets XeSS, Seat Memory and One Installer

By Indie Kings | October 20, 2026

Updated October 20, 2026: EDVR, an unofficial VR patch for Elite Dangerous: Odyssey, released version 0.20.0 on October 20, 2026. The update adds Intel XeSS super resolution, per-headset seat memory, a VR plugin loader and a single installer for the desktop and VR editions. It is the first release built and checked against Elite build 334473, the Anaconda Mk II update from October 13.

The one-sentence version: EDVR is a community OpenXR layer that fixes the parts of Elite Dangerous that still behave like a flat-screen game in a headset, and 0.20.0 turns it into one installer with a longer list of fixes.

Image credit: EDVR project, Elite Dangerous: Odyssey.

What EDVR is

EDVR is not a new game and not a VR mod that replaces Elite's renderer. It is a patch that loads beside Elite Dangerous: Odyssey as a d3d11.dll proxy and supplies its own openvr_api.dll as an OpenXR runtime. The game still starts through its normal OpenVR-facing path, but EDVR owns the OpenXR session behind it and fixes frames before the headset sees them.

That design matters because Elite's VR support is old. The game can run in a headset, but several effects are drawn once for two eyes, pinned to the camera instead of the world, or sized for a monitor. EDVR's README describes the pattern plainly: something that looks correct on a screen is wrong in a headset because it is drawn once, head-locked, or scaled for the wrong surface.

The project is free, MIT licensed and not affiliated with Frontier Developments or Valve. It requires a legitimate copy of Elite Dangerous: Odyssey. It does not touch the game's network traffic, account state or gameplay values, according to its own documentation, and it does not interact with anti-cheat.

What version 0.20.0 adds

The biggest practical change is the installer. Earlier releases split VR and flat-screen installs, and 0.20.0 replaces both with one edvr-installer.exe that installs either or both. Elite's own 3D setting picks the profile at launch: modes 0 and 1 are the desktop edition, modes 2 through 6 are VR, and an unknown mode is treated as VR. The /vr and /novr switches override the automatic choice.

XeSS-SR is now an anti-aliasing option in both editions. It joins DLSS and FSR 3.1 in the same in-headset menu, and it is off by default. The release notes say XeSS runs on any GPU, with the obvious caveat that Intel Arc cards are the ones with the hardware path. On other cards it costs more than DLSS: the README says XeSS took about 1.2 ms more per frame than DLSS on an RTX 5090 in VR.

Seat memory is the other feature a regular player will notice. EDVR now remembers the cockpit centre for each headset and restores it when the player starts, boards, changes cockpit or leaves Explorer Cam. A manual recentre still takes effect immediately, and the game's automatic resets restore the stored seat rather than throwing the view away.

The release also fixes the hangar wall flicker, the left-eye black squares in the Full System Scanner ring, and the carrier disembark flash. Both eyes now share one exposure calculation, which the release notes say saves about 0.15 ms of GPU time. Canted headsets such as the Pimax 8KX get world motion computed for each eye, which matters for temporal upscalers on displays that are not parallel.

The build 334473 problem

Elite's October 13 update broke the previous release candidate. The project's issue 120 reports that an install of 0.20.0-rc.5 saw Elite exit one to ten seconds after launch, with no EDVR log written. That is the kind of failure that looks like a game crash and is actually a patch built for the wrong executable.

Version 0.20.0 retargets EDVR's addresses to build 334473, version string 2026.10.13.334473, and the release says it has been flown on that build in both the desktop edition and VR. The verified-build field is now only 334473. Older builds still start with EDVR, but the Oculus route is not installed when the game has no matching profile, and Explorer Cam does not start on anything other than 334473. The log is supposed to say why.

That limit is worth taking seriously. EDVR is not a universal patch that survives every Elite update by magic. The brightness, black-void, screen-distance and resolution fixes find their targets by behavior or by what the frame looks like, so some of them degrade instead of guessing. The two fixes measured from one build are the ones that need a new profile after a game update.

DLSS, FSR and XeSS in VR

EDVR's upscaling is built around Elite's HMD Quality setting. With HMD Quality below 1.0, the game renders a smaller image and the upscaler brings it back to headset resolution. That is where the frame time saving comes from. At 1.0 or above, DLSS runs at the full render size, which is effectively DLAA and not a performance mode.

The README is unusually direct about the trade-offs. DLSS needs an RTX card and NVIDIA's runtime, which the installer places only on machines with an NVIDIA GPU. FSR 3.1 runs on any GPU and needs no extra file. XeSS-SR also runs on any GPU, but it is fastest on Intel Arc and costs more elsewhere. The project measured about 1.2 ms per frame more than DLSS on an RTX 5090 in VR, which is a real cost at 90 Hz or 120 Hz.

The setup rule is simple and easy to get wrong: leave Elite's Supersample Quality at 1.0. Pick DLSS, FSR or XeSS in the Anti-aliasing row on the in-headset Performance page, or set fix.temporal_aa in edvr.ini. Set Elite's own anti-aliasing to Off or SMAA while EDVR's temporal pass is on. The DLSS preset defaults to K, and sharpening is off by default; the README suggests 0.3 as a starting point if the temporal pass softens the image too much.

Source: EDVR README and 0.20.0 release notes, fetched October 20, 2026.

The fixes that matter in a headset

EDVR's fix list is long because Elite's VR problems are not one bug. The two eyes disagree on exposure near bright stars, with the README measuring a 1.5-stop difference without the fix and 0.4 stops with it. A planet can render as a black disc in one eye in the scanners. The FSS can show each eye a different scan. The RemLok helmet's edge lines can hang along the nose instead of at the temples.

Other fixes put effects back in the world. A star's full glare is no longer rolled and tilted with the head like a camera overlay. Geyser plumes and solar prominences stop swimming as the player looks past them. The loading ship's head-locked scan pattern and the launch movie's 27-degree rectangle are moved onto the surfaces they belong to.

The jump flash is handled differently. Each jump or supercruise dropout produces a one-frame flash, and EDVR catches it and holds the previous frame instead. That fix is always on and has no setting. A game build the patch does not recognize gets no hold, and the log says so.

Over planets, Elite culled terrain using a head pose about 42 ms older than the one it drew with, which could leave squares of ground undrawn at the edges when the player moved their head. EDVR answers the game's request for the current head pose at the instant the frame is drawn. On headsets whose eyes see further out than the centred frustum, such as a Quest 3 or a cropped Pimax, it also widens the frustum to what each eye shows, which the project says stopped black flashes at the outer corners over flat ground.

On foot, the grey surround is made properly black, the screen is moved, bent and raised above its forced 1920x1080, and Explorer Cam provides a stereo view from the commander's head in the free camera. Explorer Cam is not a first-person 3D mode: the game still renders the on-foot world once and flat, and the patch does not pretend otherwise. It works only in the free camera, where the game already draws stereo.

A plugin loader with a manual approval step

Version 0.20.0 adds a third-party plugin loader for VR. Each plugin file has to be approved separately on the F8 Plugins page. A plugin can take keyboard and joystick input, and a plugin that faults is disabled. That is a sensible default for a scene where a VR mod can hook input and rendering, and it is more conservative than loading every DLL it finds.

The loader is VR only. Desktop users do not get it, which fits the release's split between the two editions. The installer also handles EDHM and ReShade coexistence: EDHM installs itself as d3d11.dll, the same slot EDVR uses, so the installer renames it and writes the setting instead of letting one mod overwrite the other. ReShade needs no configuration and composes with EDVR.

Install and requirements

The Windows install is a single unsigned executable inside a zip. The README says it takes about three minutes, finds the game, shows what it is about to change and waits for confirmation before writing. It copies every file it replaces into edvr_backup\. Windows SmartScreen will warn because the installer is not code signed; the release publishes a SHA-256 hash, and the project says that hash is the only way to check the download without a signature.

On Linux, the release includes edvr-installer-linux-<version>.zip with a shell launcher and a Python wrapper. It uses the Proton installation Steam already has, with no Protontricks or system Wine required. The user runs Elite once from Steam, closes it, then runs the installer from Desktop Mode on a Steam Deck. The launcher opens the Windows installer GUI with the Odyssey folder preselected.

The OpenXR runtime has to be set before launch. EDVR bundles the Khronos loader and reaches whichever runtime Windows has marked active, whether that is SteamVR, Pimax's PiOpenXR, Virtual Desktop's VDXR or Meta's runtime. The project says it has been checked on Pimax over PiOpenXR, Quest 3 over VDXR and Air Link, and that it does not need OpenComposite or a vendor OpenXR loader. Canted Pimax headsets should turn Parallel Projection off; the README says that cut GPU time by up to about 30% in its own test on an 8K X at FOV Wide.

Source: EDVR README, install guide and 0.20.0 release notes, fetched October 20, 2026.

What it does not do

EDVR does not make Elite a native OpenXR game. It keeps the game's OpenVR entry point and puts its own runtime behind it. It does not support Elite's legacy LibOVR path, and it does not fall back to it. It does not install on Elite Dangerous: Horizons, and it refuses an unreadable executable before writing anything. An Odyssey revision the build was not checked against installs with a warning, but the fixes tied to that build stand down and the log names each one.

It also does not survive every game update without work. Frontier's launcher may remove d3d11.dll when it verifies the install, which uninstalls EDVR without breaking the game; the user has to copy the file back. A new Elite build can move the addresses the patch depends on, as build 334473 did. The project is explicit that this is a moving target, not a one-time install.

The plugin loader is new, and plugins are third-party code. The approval step reduces the risk of an accidental load, not the risk of a plugin doing something unwanted. The same applies to any mod that hooks input and rendering.

Our take

The most interesting thing about EDVR is not XeSS. It is the decision to build a native OpenXR layer that fixes the game's frames instead of asking Frontier to rewrite a decade-old VR path. That approach lets the project fix exposure disagreement, head-locked effects and terrain culling without touching the game's network code or gameplay state. It also means every Elite update can break it, which is the trade-off the project accepts in public.

The 0.20.0 release is a maturity step. One installer for both editions, a profile picker that follows Elite's own 3D setting, a plugin loader with per-file approval and a documented recovery path are all things a project needs before ordinary players can use it. The seat memory and the XeSS option are the features people will notice, but the installer and the build check are what make them usable.

We would still call it enthusiast software. It is unsigned, it modifies a running game in memory, it depends on the active OpenXR runtime and it has a build-specific profile. The README is honest about all of that, which is a good sign. Anyone trying it should read the install guide, keep the backup folder and expect to reinstall after a big Elite patch.

FAQ

What is EDVR?
EDVR is an unofficial VR patch for Elite Dangerous: Odyssey. It loads as a d3d11.dll proxy, supplies an OpenXR runtime through openvr_api.dll, and fixes rendering and comfort problems that the game's own VR path leaves in place.

What is new in EDVR 0.20.0?
Version 0.20.0 adds XeSS-SR, per-headset seat memory, a VR plugin loader, a single installer for the desktop and VR editions and fixes for the hangar wall, the Full System Scanner ring and the carrier disembark flash. It is the first release verified against Elite build 334473.

Does EDVR work with the latest Elite Dangerous update?
Version 0.20.0 is built and checked against build 334473, version string 2026.10.13.334473, the Anaconda Mk II update. The release says older builds still start, but some fixes degrade and Explorer Cam only starts on 334473.

Does EDVR add DLSS, FSR or XeSS?
Yes. It supports DLSS on RTX cards, FSR 3.1 on any GPU and XeSS-SR on any GPU. XeSS is fastest on Intel Arc and costs more on other cards; the project measured about 1.2 ms per frame more than DLSS on an RTX 5090 in VR.

Does it work on a Steam Deck or Linux?
The release includes a Linux installer that uses Steam's Proton, with no Protontricks or system Wine. It is meant to be run from Desktop Mode. The project says the installer was tested with Proton, but handheld performance and compatibility still depend on the headset and runtime.

Is EDVR safe and legal?
EDVR is free and MIT licensed, and it requires a legitimate copy of Elite Dangerous: Odyssey. It is not affiliated with Frontier Developments or Valve. It modifies the running game and hooks graphics calls, so it is unofficial software; the source is public and the installer backs up the files it replaces.

Bottom Line

EDVR 0.20.0 is an unofficial VR patch for Elite Dangerous: Odyssey that adds XeSS-SR, per-headset seat memory, a VR plugin loader and a single installer for the desktop and VR editions. It is built and verified against Elite build 334473, the October 13 Anaconda Mk II update, and it includes fixes for exposure disagreement, head-locked effects, terrain culling, the jump flash, the hangar wall and the Full System Scanner. DLSS, FSR 3.1 and XeSS are supported, with DLSS on RTX, FSR on any GPU and XeSS fastest on Intel Arc. The patch is free, MIT licensed, unsigned and not affiliated with Frontier or Valve, and it needs a legitimate copy of Odyssey plus a working OpenXR runtime.

Sources

• EDVR repository and README: characterecho-sean/edvr-unofficial-patch
• EDVR 0.20.0 release notes, published October 20, 2026: v0.20.0
• EDVR issue 120, Elite exit after the October 13 update: issue 120
• EDVR install and troubleshooting documentation: docs directory

Related: Swing, Draw, Heal: Vanilla WoW Gets A Full Body VR Client | Upshift Wraps OptiScaler With Full Game Library Manager