Just installed an EVGA 3090Ti FTW3 today to upgrade from an EVGA 3080Ti FTW3 which has worked properly with my HP Reverb G2 VR headset for months. I'm now receiving a "1-4 Display Port error" in Windows Mixed Reality Portal when starting up VR. This is usually indicative of a broken VR headset cable or a bad USB port. I've tried replacing the headset cable from the GPU/PC to headset with a spare, tried a different USB port on the PC, and even tried another HP Reverb G2 with the same result.
 
Seems the issue is not just limited to me, I found a thread on Reddit with similar reports, link here: https://www.reddit.com/r/HPReverb/comments/tu80hj/g2_v2_and_3090_ti/.
 
Sending this out for some visibility and in the off chance that someone has a workaround/fix. I'm going to guess it's either a driver issue or a GPU BIOS issue, but I'm open to suggestions.

Windows Mixed Reality is the Windows layer in between a GPU and the VR headset, this isn't an HP compatibility problem. I contacted HP support already, and since there are no issues with the headset and it works fine on my 3080Ti, they have nothing they can fix. HP doesn't make drivers for every known video card out there to work with the headset, that's what video card drivers are for along with Windows Mixed Reality.

I just got an EVGA 3090 Ti Ultra and it has been working flawlessly with my OG HP Reverb G2 (all OG accessories and cables). Nvidia game ready driver 512.16. One thing I never bothered to do was update my motherboard driver to enable Re-Bar for NVIDIA cards... not sure if its related at all. I use the default usb-c cable with no adapter directly plugged into my motherboard. I also use the power adapter that came with it with a power strip to turn it off.Whenever I have an issue with headset detection, all I usually have to do is restart the headset via my power strip.
 
Edit: It could be a V2 cable compatibility issue.

basic questions:
 
MB & BIOS version - check for updates
 
CPU ?
 
Is Fast Boot Off on your PC in BIOS ?  (so MB/BIOS correctly sees the New Hardware)
 
Is Windows Fast Startup Off ? (so Windows does not use the previous saved files to load hardware profile on Boot)
 
Any errors or warning in Device Manager ?
 
Did you install the complete Nvidia driver package or just parts of it ?
 
What Version of OS 10 or 11 ?  and details of the OS ... is it fully up to date ?

Report it to Nvidia. I had an issue with an Nvidia driver update a few months ago with an rtx 3080 mobile issue when mux switch was enabled and after some back and forth they had a hot fix within a few days. I was really surprised at how fast it was. If it's a driver problem they might be able to get it fixed quick.

CraptacularOne
You're miss understanding me. This is absolutely a compatibility issue and could be caused by the API not recognizing the RTX 3090 Ti or it's the 512.16 driver that only supports the RTX 3090 Ti that's the issue.

Gotcha. Judging from all the additional reports, it seems like it's either Windows Mixed Reality that doesn't support the 3090Ti, which means it's Microsoft that needs to fix it (ugh) since a fresh install of WMR does state the 3090Ti isn't "supported" but "might work", but it could also be Nvidia (slightly less ugh) drivers too. Or both. Or maybe EVGA? Possibly HP too?
 
As others have said, guess we'll find out soon enough.

mpetts

CraptacularOne
You're miss understanding me. This is absolutely a compatibility issue and could be caused by the API not recognizing the RTX 3090 Ti or it's the 512.16 driver that only supports the RTX 3090 Ti that's the issue.

Gotcha. Judging from all the additional reports, it seems like it's either Windows Mixed Reality that doesn't support the 3090Ti, which means it's Microsoft that needs to fix it (ugh) since a fresh install of WMR does state the 3090Ti isn't "supported" but "might work", but it could also be Nvidia (slightly less ugh) drivers too. Or both. Or maybe EVGA? Possibly HP too?
 
As others have said, guess we'll find out soon enough.

Unfortunately this isn't something EVGA can fix. I'm almost certain the issue lies in WMR itself not recognizing the RTX 3090 Ti, this falls squarely on Microsoft and Nvidia. 

CraptacularOne

mpetts

CraptacularOne
You're miss understanding me. This is absolutely a compatibility issue and could be caused by the API not recognizing the RTX 3090 Ti or it's the 512.16 driver that only supports the RTX 3090 Ti that's the issue.

Gotcha. Judging from all the additional reports, it seems like it's either Windows Mixed Reality that doesn't support the 3090Ti, which means it's Microsoft that needs to fix it (ugh) since a fresh install of WMR does state the 3090Ti isn't "supported" but "might work", but it could also be Nvidia (slightly less ugh) drivers too. Or both. Or maybe EVGA? Possibly HP too?
 
As others have said, guess we'll find out soon enough.

Unfortunately this isn't something EVGA can fix. I'm almost certain the issue lies in WMR itself not recognizing the RTX 3090 Ti, this falls squarely on Microsoft and Nvidia. 

It's probably going to be a pretty fast fix now that the graphics card is out. I am also thinking with the PSVR 2 games are going to need to be developed and tested on the PC which could help a lot since I could see people using a 3090Ti for game development. 

I did open a hub ticket yesterday and have not heard anything back. I flagged it as a critical breaking issue but who knows if or what that even triggers for a response.

Yep. Still nobody taking responsibility at this point. Not good.

It is strange that no one at HP has run that card with the Ti.  But the specs. do say it is compatible all the way to the RTX 3090 ... nothing regarding a specific version of the card.
 
The 1-4 errors can normally be corrected by removing and replacing the USB cable?
 
Did you completely uninstall the WMR and start over and set up the headset with the new card, as I suggested?

tl;dr: HP is aware of the issue.
 
HP Support will tell you to downgrade to a "supported" video card and/or take it up with EVGA and then wash their hands of it. While it's true that downgrading to a previous video card obviously works (duh), that's less than helpful. Microsoft has acknowledged the issue as I mentioned above, but have gone radio silent.
 
On Reddit, an HP representative on the VR team posted that they are aware of the issue and currently obtaining a 3090Ti for testing. The problem is with ALL 3090Ti's, not just EVGA's.
 
Good news in some aspect that ownership has been taken, but no idea how long it will take to resolve. In the interim getting a Rev1 PC to headset cable HP part number M18238-001 is a confirmed workaround, although it's long been discontinued, but there's currently a seller on Ebay that has several for sale which is where I purchased one. Why an older somewhat unreliable version of the cable works and the latest does not is not known specifically, but there are several people who have tested that it does work, including me. If you absolutely must have your HP Reverb G2 VR headset working with your new shiny 3090Ti until they fix the problem, that's currently the only avenue.

Not that I am aware. In fact, they had to make a whole hardware revision already (but still the same SKU to add confusion) that addressed previous connectivity issues with the "old" headset cable interface. That was all USB related, though, as the Displayport has not been an issue for anyone up until now.

Also might make a difference whether the headset and base unit both have updatable firmwares, or that the problematic of the two is the one that has the updatable firmware.

It is not, not even with the latest just released driver. HP and Nvidia are still trying to diagnose the problem. There is a huge thread on Reddit about it.