In March 2021, our engineering lead sent me a message that said simply: "We need VR headsets for virtual reality development. Can you handle the purchase?"
I'm the office administrator for a 400-person company. I manage all hardware ordering—roughly $300,000 a year across 8 vendors—and I report to both operations and finance. Normally I buy office chairs and monitors, not headsets. But I've learned that a purchase request like this always comes down to the same thing: if I don't verify before I order, I'll be correcting after I sign the PO.
The Specs Made It Look Like a No-Brainer
The engineering team asked for three things: high-resolution displays, SteamVR compatibility, and a headset that didn't require a room full of external cameras. We looked at the HP Reverb VR lineup and settled on the G2 virtual reality headset. It checked every box. The published specs on HP's product page at the time (accessed March 15, 2021) showed 2160x2160 resolution per eye, inside-out tracking, and native SteamVR support. On paper, it was the obvious choice.
But most buyers focus on resolution and completely miss deployment reality. The question everyone asks is "What's the resolution?" The question they should ask is "What happens after the box arrives?" A VR headset is only good if the user's PC can feed it, the cable can reach, and the platform doesn't fight your IT policies. That's where our story started.
I Almost Ordered 12 at Once
I pulled quotes from three vendors. The best bulk price came to about $380 less than buying 12 units separately. It felt like a no-brainer. But I had been burned before by a supplier who couldn't produce a proper invoice—finance rejected the expense, and I ate the cost. So I overrode the discount and ordered one HP Reverb G2 first.
When the pilot unit arrived, setup was smooth. We plugged it into a developer laptop, installed SteamVR, and it worked in about 20 minutes. I was relieved. I almost hit "submit" on the remaining 11 headsets that same afternoon. If I had, we would have discovered our problem after 12 headsets were sitting in the IT closet.
The Assumption That Cost Us a Week
Here's where I got cheap. The G2 needs a high-bandwidth USB connection on the PC. Our developer machine had the right port, but the older Dell computers in our training room didn't. IT recommended a powered USB hub—about $60 each. I found a basic non-powered hub for $9 and ordered six to save roughly $300.
For two days, everything worked. Then the problems started: tracking glitched, audio crackled, SteamVR said "headset not detected," and one user reported the virtual environment froze while the headset audio kept playing. The non-powered hubs weren't supplying enough power and bandwidth consistently. We replaced them with the powered hubs IT originally recommended, and the issues disappeared.
That $300 savings cost about $700 in troubleshooting time and made a group of engineers lose faith in a new system. Classic penny-wise-pounds-foolish. I now tell anyone who asks: if the IT person recommends a specific adapter or hub, stop trying to save four dollars on a cheaper one. You are not the one who will debug it at 6 p.m.
Why Do I Hear Myself in My Headset?
Two days after the replacement hubs arrived, the first support ticket hit my inbox. Subject: "Why do I hear myself in my headset?" My first assumption was that the microphone monitoring was turned on in some app. I checked the driver and the volume mixer, then started searching for a setting that would make the self-voice disappear.
The truth was simpler, and I found it by reading the HP documentation and a few SteamVR forum threads. The HP Reverb G2's speakers are designed to sit slightly away from your ears rather than sealing over them. This is intentional: it reduces ear fatigue and helps you stay aware of your real surroundings. So when you speak, you naturally hear your own voice through your skull and through the open-ear speakers. It's not a defect. It's how the headset is supposed to feel.
One user tried to fix it by wearing a Peltor headset over the VR headset. I suspect they grabbed it because it was the only noise-blocking headset in the office. But a Peltor headset is hearing protection, not a VR audio accessory. The ear cups pressed against the G2's temple area, made the fit uncomfortable, and amplified the user's own voice like they were talking into a bucket. In other words, it made the exact problem worse.
If your team uses the G2 in a shared space, include "audio expectations" in your onboarding guide. Explain that open-ear speakers mean you'll hear some background noise and your own voice. If you need more isolation, use a pair of in-ear monitors and run VR in a quiet room. Don't bolt on a hearing-protection headset and call it a day.
What I'd Do Differently
After that rollout, I created a 12-point hardware deployment checklist. It starts with the same rule that saved me from buying 12 headsets at once: pilot one unit on the exact computer model your users will use. Then verify the USB port, the video connection, the room lighting, the cable length, and the app's audio configuration. Write the expected user experience before you hand the headset over, so "I can hear myself" doesn't become a bug report.
This is not exciting work. But 5 minutes of verification beats 5 days of correction. I know because I lived the 5 days.
Take it from someone who bought six non-powered USB hubs to save $300: verification is the cheapest insurance in procurement.
If you're evaluating the HP Reverb G2 for a new virtual reality development project, check the current SteamVR compatibility list and HP's support pages—driver versions and USB requirements have changed since our 2021 rollout. The headset we bought still works, but it works because we verified the whole setup, not just the spec sheet.
One last thing: if a user asks why they hear themselves in the headset, don't open the audio mixer. Close out of your ticket system, explain the open-ear design, and if they keep complaining, hand them a pair of earbuds. You'll thank me later.