On August 29, 2025, owners of Windows Mixed Reality headsets got an unexpected reprieve. A new native SteamVR driver called Oasis, developed by former Microsoft mixed reality engineer Matthieu Bucchianeri, began rolling out on Steam, restoring compatibility for devices that Microsoft had officially abandoned. The driver bypasses the deprecated Mixed Reality Portal entirely, letting headsets like the HP Reverb G2, Samsung Odyssey, and Lenovo Explorer behave as standard SteamVR hardware.

This release marks the first time since Windows 11’s 2024 updates removed WMR support that these headsets can run modern OpenVR and OpenXR applications without hacks or workarounds. The community response was immediate and enthusiastic, with industry outlets and forum threads lighting up with guides, troubleshooting tips, and success stories.

Background: The Fall of Windows Mixed Reality

Windows Mixed Reality launched in 2017 as Microsoft’s big push into PC-based VR. A partnership model brought headsets from HP, Samsung, Lenovo, Acer, and others, all relying on Microsoft’s Mixed Reality Portal and runtime to function. For years, the platform served as an affordable entry point into high-fidelity VR, with the HP Reverb G2 in particular earning praise for its sharp optics and audio.

But in late 2023, Microsoft announced it would deprecate Windows Mixed Reality, and by early 2024, Windows 11 updates began stripping the necessary runtime components. The Mixed Reality Portal became non-functional, and SteamVR stopped recognizing WMR headsets. Overnight, a generation of perfectly capable hardware was rendered obsolete—turning devices worth hundreds of dollars into e-waste.

What Is the Oasis Driver?

Oasis is not a Microsoft clone or a reimplementation of the Mixed Reality Portal. It is a native SteamVR driver that operates in Direct Mode. This means it communicates directly with the headset’s display over the GPU bus, bypassing the missing Windows runtime entirely. Once installed, the headset appears to SteamVR as a generic SteamVR device, complete with full 6DoF tracking for both the headset and controllers, input mapping, and haptic feedback.

The project’s singular focus is to make WMR headsets work like any other SteamVR headset—no extra portals, no Microsoft dependencies. Bucchianeri, who previously worked on Microsoft’s inside-out tracking algorithms, built Oasis to fill the vacuum left by his former employer’s policy shift.

Under the Hood: How Oasis Bypasses Microsoft’s Runtime

The magic is in Direct Mode. When a SteamVR native driver opens a headset in Direct Mode, it asks the GPU to dedicate a display pipeline exclusively to that device. This eliminates the overhead and compatibility issues of treating the headset as an extended desktop monitor. Oasis taps into the same mechanism that Valve’s Index and HTC headsets use.

But this approach places heavy demands on GPU drivers. The driver must expose low-level display acquisition calls, and not all vendors support them equally. At launch, only NVIDIA GPUs are compatible. AMD and Intel integrated graphics do not currently provide the necessary hooks, a limitation that Bucchianeri says is not a design choice but a consequence of how SteamVR’s architecture interacts with vendor drivers. He provided AMD with technical details, but as of the release cycle, AMD support was described as “dead in the water.”

For tracking, Oasis repurposes the headset’s onboard sensors and camera data, translating it into SteamVR’s coordinate system. The developer spent months fine-tuning distortion profiles, chromatic aberration correction, and controller pose smoothing to match or exceed the original WMR experience. Early testers note that head and hand tracking feel native, with the usual SteamVR guardian and recentering commands working as expected.

Features and Limitations

Oasis launches with a robust feature set:
- 6DoF positional and rotational tracking for headset and motion controllers.
- Controller input, haptics, battery level reporting, and 3D controller models for several WMR variants.
- 90 Hz and 60 Hz refresh rate support, hidden-area mesh rendering optimizations.
- OpenVR/OpenXR compatibility, enabling titles from SteamVR’s library and standalone OpenXR apps.

What it does not include—yet—is full passthrough parity. Initial passthrough is monocular and experimental. Some advanced headset-specific features, like the HP Reverb G2 Omnicept’s eye tracking, may depend on firmware limitations and are still being tested.

One critical constraint: Oasis remains closed-source. Bucchianeri cited reverse-engineering risks and IP/NDAs as reasons for keeping the code private. This has sparked debate—while closed-source means the community cannot audit the driver, the developer’s track record and the scrutiny of Steam’s distribution process offer some assurance. For enterprise or privacy-sensitive users, this remains a point to consider.

System Requirements and Installation

To use Oasis, you need:
- Windows 11 version 24H2 or later. Windows 10 may run but is unsupported and prone to instability.
- A supported NVIDIA GPU (any RTX series should work; older cards may struggle with performance).
- Steam and SteamVR installed and updated.
- The Oasis driver itself, available from the Steam store (Valve approved the listing shortly before launch).

Installation is straightforward: subscribe to the tool on Steam, ensure SteamVR is set as the default OpenXR runtime, and launch SteamVR. Oasis will automatically detect the headset and take over. The first run may require recentering and guardian boundary setup. Some users reported that controller offsets needed a manual restart, but those issues were largely resolved by launch.

Crucially, the old Mixed Reality Portal is not required. In fact, having its remnants installed can interfere. The developer’s documentation advises removing any leftover Microsoft WMR components for the cleanest experience.

Community Reception and Real-World Performance

Within days of the release, forums like r/WindowsMR and r/SteamVR filled with testimonials. Users with HP Reverb G2s reported “buttery smooth” 90 Hz gameplay in demanding titles like Half-Life: Alyx and Microsoft Flight Simulator. Samsung Odyssey+ owners praised the rich OLED colors finally being usable again. The common thread: relief that expensive hardware wasn’t doomed to landfill.

Performance is ultimately bounded by the headset’s panel resolution and the host GPU’s muscle. Oasis itself introduces negligible overhead, so if you could run a game before the deprecation, you likely can now. Hidden-area mesh rendering helps squeeze out extra frames by not rendering pixels obscured by the lens mask.

Not all feedback was flawless. Some users encountered occasional tracking jitter in low-light rooms or with mirrored surfaces—an issue Oasis inherited from WMR’s inside-out tracking reliance. Passthrough alignment during room setup could drift, though a quick recenter fixed it. These are typical growing pains for a newly released community driver, and Bucchianeri has committed to ongoing updates.

Why It Matters: E-Waste and Hardware Preservation

Oasis isn’t just a technical curiosity; it’s a statement on hardware longevity. The HP Reverb G2, launched at $599, is arguably still one of the sharpest consumer VR headsets with its 2160×2160 per-eye resolution. For simulation enthusiasts, it remains a prized piece of kit. Without a driver, those panels were destined for closets or recycling centers.

By restoring functionality, Oasis directly combats e-waste. The environmental cost of manufacturing a VR headset—rare earth metals, plastics, shipping—is not trivial. Extending a device’s life by even two or three years has a measurable impact. It also challenges the industry’s planned obsolescence narrative, proving that community engineering can step in where corporations step out.

Risks and Trade-offs

Adopting a closed-source third-party driver entails calculated risks. Future Windows updates or SteamVR changes could break Oasis overnight, and the maintenance burden rests on a single developer. The NVIDIA-only requirement locks out AMD and Intel users, a gap that may never close if GPU vendors don’t cooperate.

Security-conscious users might balk at a driver with no public code review. While Steam’s approval process provides a baseline vetting, the driver operates at a low level and could theoretically cause system instability. At least one early adopter reported a blue screen when swapping GPUs without uninstalling Oasis first—a solvable issue, but a reminder that native drivers demand respect.

For those unwilling to accept these trade-offs, the alternative is to buy a modern SteamVR-native headset like the Valve Index or a Meta Quest via Link. But with prices starting at $999 for a full kit, Oasis makes a compelling case for the frugal and environmentally conscious.

The Road Ahead

Bucchianeri has indicated that Oasis will continue evolving. Top priorities include polish on passthrough, persistent room anchors, and more device-specific profiles. The longer-term picture hinges on vendor cooperation. If AMD or Intel eventually enable the necessary Direct Mode support, Oasis’s potential audience could double.

Valve’s ongoing commitment to SteamVR also plays a role. Any major architectural shift in SteamVR could require rewriting parts of Oasis. However, Valve’s public support of community drivers (evidenced by the quick store approval) suggests they see value in keeping the PC VR ecosystem broad and inclusive.

The broader lesson is clear: when platforms deprecate hardware, the community can organize. Oasis is not the first community driver, but it’s the most polished attempt yet to rescue a class of headsets from forced obsolescence. It sets a precedent for how we think about VR hardware lifecycles.

Conclusion

Oasis is more than a driver—it’s a bold response to a platform’s withdrawal. By engineering a native SteamVR bridge, Matthieu Bucchianeri has given Windows Mixed Reality headset owners a second lease on VR life. If you have an HP Reverb G2, Samsung Odyssey, Lenovo Explorer, or similar device gathering dust, and you meet the NVIDIA and Windows 11 24H2 requirements, Oasis is worth trying. You’ll likely find your old headset performing better than ever under SteamVR’s mature runtime.

Yes, it’s closed-source and vendor-limited. But for thousands of users, it transforms a bleak obsolescence into a vibrant second act. In an industry where hardware often feels disposable, Oasis stands as a testament to what one skilled engineer can do when he decides that no device should be left behind.