I've owned my Reverb G2 for about 3 years and have unfortunately had to replace the cable a couple of times.  Last month the headset went again so I assumed it was the cable again and purchased yet another one. However, this time the headset remained dead, with WMR portal telling me to connect a headset. The seller assures me that the cable was tested and was working on shipping. Is there any way, other than finding another headset to test, to independently figure out whether the issue is with the cable or the headset ? 

 

Assuming everything is plugged in well, the power supply and the white light on the cable box is on:

If with the previous cable the headset showed the same problem (not recognised as connected) then almost certain it is the headset or the software.

If you have the old cables still, just try them again and see if the problem you had with them before shows up again, if so then the new cable is broken.

I understand it is not a completely new cable?

Be sure the cable is plugged in well. For me I have to push quite hard to get the plug seated in the headset.

It's a new cable. I'm leaning toward the headset being bad but would like confirmation before shelling out for a new/refurbished one. 

One thing for sure with the Reverb G2: if you are using a non default display resolution in Windows, then WMR portal will say "connect headset" as long as you stay in that non default resolution.

I mean your 2d monitor display resolution which you set after right clicking on desktop and choosing "Display settings". Whatever is listed as (Recommended) must be used or Windows will never find the headset if it is a G2 Reverb. I imagine it's the same with any WMR headset, but for sure with the G2.

Edited April 15, 20242 yr by Fielder

Try switching between 90Hz and 60 Hz in WMR.  My G2 gets "stuck" sometimes and this gets it going again.  I did not have to do this in the past so I'm suspecting an "update" somewhere along the way did this.  This wouldn't be the first time a piece of hardware was intentionally bricked on me (looking at me dead Smasung Galaxy Note that was bricked years ago and they didn't even try to hide it very well)

LouP

just to close out the thread it turns out both the cable and the headset were bjorked. Picked up a used G2 headset only ( no cables or power brick ) on E-bay for $120 which has been working perfectly with the new cable ( but not the old cable ). The only issue I had was no sound from the game, but sound into the headset from other sources so I lnew the headset was fine. Turns out Windows had muted the FlightSimulator app volume. This is a tough one to diagnose unless you know that windows has a seperate app by app volume setting independent of the global setting, and that it is only accessible when the app is running.