From 3 Failed Setups to Flawless Runs: My 7-Point Pre-Flight Checklist for HP Reverb G2 on SteamVR

I've been handling enterprise VR hardware orders for 3 years. In that time, I've personally been responsible for 3 completely botched HP Reverb G2 setups—one that resulted in a $2,800 chargeback and a 2-week project delay.

The root cause? Not a hardware problem. Human error. Specifically: skipping a 10-minute verification process before shipping the headsets to end users.

After my third mistake (September 2024), I created this 7-point checklist. We've used it for every HP Reverb G2 SteamVR deployment since. Zero failed first-run setups. Total time investment: about 20 minutes per headset before it leaves the office.

Here's the checklist—exactly as I hand it to our deployment techs.

Who This Checklist Is For

If you're responsible for deploying HP Reverb G2 headsets for business use (training sims, virtual showrooms, engineering reviews), and your users aren't VR hobbyists, you need this.

It's for the scenario where the headset must work with SteamVR out of the box—no driver fiddling, no BIOS tweaks, no "call IT" moments.

Step 1: Verify the PC Spec Against the Bare Minimum (Not the Recommended)

What I learned the hard way

The HP Reverb G2 has a native resolution of 2160 x 2160 per eye. That's double the pixel count of the original Oculus Rift. You can't just plug it into any work laptop with a discrete GPU.

I once approved a deployment to 8 standard Dell Precision 3560 laptops. The specs looked fine on paper. The result: 8 headsets that couldn't maintain 60fps in SteamVR Home. That was a $6,400 hardware mistake, plus re-shipping costs.

Here's our internal check:

• GPU: NVIDIA GTX 1070 or better (desktop). For laptops: RTX 3070 Ti laptop GPU is the real minimum. A standard RTX 3060 laptop barely cuts it.
• RAM: 16GB, not 8GB. The G2's renderer is memory-hungry.
• DisplayPort: The Reverb G2 uses DisplayPort 1.3+. Many modern laptops omit DisplayPort in favor of HDMI. You'll need an active adapter or a Thunderbolt-to-DisplayPort solution. A passive adapter will not work.
• USB: The headset requires a USB 3.0 port providing at least 900mA. Some front-panel USB ports on desktops don't deliver enough power. Use the rear motherboard ports. Or, actually, the dedicated port on your power supply if you have one.

Check: Confirm your target PC meets these specs. Not just the SteamVR Performance Test passmark.

Step 2: Install the Correct Windows Mixed Reality (WMR) Software

This seems obvious, but the version matters.

The HP Reverb G2 requires Windows Mixed Reality for SteamVR—not just the base WMR portal. And it requires the stable release channel, not the beta.

Common mistake: Installing the regular "Mixed Reality Portal" from the Microsoft Store, then wondering why SteamVR doesn't see the headset.

My fix: On your deployment checklist, include a line that says: "SteamVR installed? Check. WMR for SteamVR (from Steam store, not Microsoft Store) installed? Check."

If you set the WMR runtime to the OpenXR path (which is the default in recent WMR builds), SteamVR will automatically detect the headset as an OpenXR device. But you don't need to mess with OpenXR manually—just install the bridge software.

Step 3: Configure Audio Routing Before the First Run

This one I really learned the hard way.

The HP Reverb G2 has built-in speakers—actually, off-ear speakers near your ears. They're decent for gaming, but for professional use (especially in quiet environments), users often prefer headphones.

The problem: Windows often routes audio to the headset's speakers and the system's default speakers simultaneously. Or it routes it to the monitor's audio output. Or it just doesn't work at all.

In Q1 2024, I had a senior engineer waste 40 minutes trying to get audio to work during a VR design review. Everyone was on the call, waiting. The headset was working visually, but the engineer couldn't hear anything. Embarrassing. The root cause? Windows defaulted audio output to the Realtek onboard audio, not the G2's USB audio device.

Pre-check: In Windows Sound Settings, set the WMR audio device (often listed as "HP Reverb G2 Audio") as the default communication device. Not just the default output. Then test both audio output and microphone input in the Windows Sound panel before launching SteamVR.

Step 4: Set SteamVR Supersampling to 100% (Not Auto)

SteamVR's auto-resolution scaling is aggressive. For the G2's native resolution, SteamVR often sets the render resolution to 120% or even 150% of the panel's native resolution. That sounds good in theory—supersampling can improve perceived clarity. But for a 2160x2160 display, 150% render resolution is essentially 4K per eye. That'll bring even a high-end GPU to its knees.

What happened to me: I demoed a G2 to a CTO on a high-spec desktop with a 3090. The SteamVR Home stuttered. He was unimpressed. Turned out SteamVR had auto-set the resolution to 150%. Dropped it to 100% (native). Butter smooth. I wasted a sale because I didn't check one SteamVR setting.

My default policy: For any business deployment, set the per-application supersampling slider to 100% and lock it per application in the SteamVR settings. Let users increase it later if they have GPU headroom. Start at native resolution. Always.

Step 5: Calibrate the Room Boundaries (But Don't Over-Calibrate)

The Reverb G2 uses inside-out tracking—no external base stations. It relies on cameras on the headset to track the room and your position. This works well in well-lit, stable environments. It fails in rooms with reflective surfaces, strong IR interference, or poor lighting.

Check this:

• Lighting: Avoid direct bright sunlight on the cameras. But also avoid dim lighting. The sweet spot is standard office fluorescent or LED (about 500-700 lux).
• Reflective surfaces: Mirrors, glass tables, and even glossy monitors can cause tracking drift. In one deployment, the tracking kept losing the floor because the user had a large glass desk. Took us an hour to figure it out.
• Floor height: When setting the room boundary, place the headset on the floor to calibrate the floor height. Do not hold it at standing height and estimate. The floor calibration is critical for a comfortable VR experience. Mis-set floor height causes immediate motion sickness.

Step 6: Test the Cable (and the Cable Clip)

The HP Reverb G2's cable is proprietary and fragile. The connector at the headset end is a small, rectangular plug that can easily be stressed if the cable is pulled at the wrong angle. A loose or damaged cable is, actually, one of the most common failure points for the G2.

The surprise wasn't the cable breaking after heavy use—it was how easily it disconnected during initial setup. The user tripped slightly, the cable pulled, and the usb-c connector at the headset end popped loose. Windows made the disconnect sound—but SteamVR didn't recover gracefully. The user had to restart everything. That happened less than 30 minutes after unboxing.

Check: Make sure the cable clip (the small plastic piece that routes the cable along the back of the headband) is properly installed. This reduces strain on the connector. Before shipping, physically tug on the cable connection to verify it's seated. I know it sounds like it's obvious—a basic thing—but I'm including it because it's the first thing we check now when a user reports a signal issue.

Step 7: Run the Windows Mixed Reality Check for Mixed Reality Portal

Launch the WMR portal. It runs a quick diagnostic: checks for proper USB 3.0 connection, DisplayPort bandwidth, and driver version. If the portal says "Everything looks good," you're probably fine. If it shows a yellow warning—warnings like "Your system is below the recommended specs" or "USB connection speed may be insufficient"—don't ignore it. That warning is worth taking seriously—it means you'll likely have issues in SteamVR.

Even if it shows a warning, it might still work. But in my experience, 8 out of 10 yellow warnings eventually become problems. I'd rather spend 15 minutes troubleshooting before shipping than 2 hours on a support call after.

A Note on Wired vs. Wireless for Professional VR

The G2 is a wired headset. That's a limitation for some use cases. But for seated or stationary professional use (engineering reviews, training simulations, virtual showrooms), the wired connection provides stable, uncompressed video—no artifacts, no latency spikes.

I've looked into wireless options for the G2. There are third-party kits, but they often introduce latency that breaks the experience for professional applications. Wireless might work for general gaming, but for precision work, the trade-off isn't worth it.

If you really need wireless, I'd argue you're better off looking at a different headset designed from the ground up for wireless, like the Vive Focus or the Pico line. But for a PCVR headset like the HP Reverb G2 that connects to SteamVR, wire is the reliable choice. You don't need to fight a wireless connection on top of everything else.

There's something satisfying about a perfectly executed first-run setup—headset on, SteamVR loads without a hitch, user is immersed, no glitches. After charging back $2,800 worth of returns, finally having a checklist that works consistently—that's the payoff.

One more thing to keep an eye on: When someone turns off the headset and turns it back on, sometimes Windows doesn't re-enumerate the USB device correctly. If that happens, unplug and reconnect the USB (not the DisplayPort). That fixes it 90% of the time. The rest of the time, you need to restart SteamVR or even the WMR portal. It's a minor distraction—or rather, it's a known quirk that you should tell your users about in advance so they don't panic.