Pimax 8KX + 3090 ti


I purchased a Gigabyte 3090 ti GPU and own a Pimax 8KX headset. The headset is recognized by the USB port, but the DP connector is not recognized. It’s not clear to me what’s broken since some people report that it works.

Any support on this is highly appreciated.

Best regards,

Hello @sami.amin2 and welcome to the NVIDIA developer forums!

I own a HP Reverb G2 myself and one thing that I found helped a lot for recognition is to power-cycle everything while it is connected. DP is not a real plug-and-play port, especially not with VR headsets.

If that does not help I usually just power-cycle the VR headset until the Windows Mixed Reality window pops-up, telling me about the newly connected device.

Other things you should look at are:

  • Is the “Monitor” maybe disabled in Graphics settings?
  • Make sure to install the latest versions of SteamVR, NVIDIA drivers and the Pimax drivers
  • Check that the DP port of your graphics card works with a normal monitor.
  • Try a different DP port on the GPU (it does not matter which you use, but in terms of "hot-plug events it could make a difference)
  • Don’t connect too many other monitors together with the VR headset. It should not be a problem for the card itself, unless you attach another 8k monitor and something on top, but PCIe Bandwidth might get to be a limiting factor.
  • Check with Pimax directly if an dhow the 3090TI is supported.

I hope this helps.

Hi there, thanks for the response. I went through the list and nothing helped unfortunately. It seems this is a known issue having gone through the release notes of the most recent driver update. Is there a fix planned anytime soon from Nvidia? I am a bit gutted since all my 3 rigs have been upgraded to the Rtx 3090ti…

Hi Sami,

Thank you for pointing out the release notes, I didn’t look at the latest ones yet.

The numbers in brackets behind the comment on Pimax HMDs not working on some 3090TI GPUs indicates that we have an internal bug open that tracks this issue. Unfortunately since it is internal I am not at liberty to disclose details or progress.

But suffice to say, since this is a highly desirable feature on a high-end GPU, this will be fixed as soon as we find a solution.

Thanks. Been using Nvidia for years now, and frankly speaking I have been extremely disappointed to find that the purchase of the highest end gpu (3 to be precise) is not compatible with a top tier vr headset. I really hope this gets resolved quickly.

I hear you!

We do have very extensive QA before release of our products and we also do have all the major VR HMDs at our disposal, only in this particular case our in-house testing did not encounter this problem.

Must admit that I am surprised this fell through the cracks at Nvidia. Could You share tentative timelines for a fix? I am concerned about the return of my investment with the 40 series around the corner.

Well, the problem itself is probably based on the DisplayPort compatibility and how the DP standard is implemented both in Hardware and Software. Which leads to a surprisingly big number of possible combinations of DP connectors both on the Add-In card side as well as the VR HMD side. Add the cable quality variations on top of that and it might not be that surprising anymore.

Regarding a timeline I need to ask for your understanding that such internal information is something we are not at liberty to share publicly. I am sorry.

I honestly don’t buy that argument. How come the hmd works on all cards except the Rtx 3090ti. This is your flagship card, and the lack of urgency to get this fixed is really disappointing. You should really tighten your driver testing processes before you slate other Organisations.

New driver release and issue not resolved. Truly speechless…

I just got my 3090 Ti today - bought specifically for the Pimax 8KX. And it doesn’t work. Please escalate. I just spent close to $15,000 total and I can’t run VR. because of this.

Hey Larry - I feel your pain. Upgraded both my rigs to Rtx 3090 ti (3 in total) and it’s extremely frustrating to see the lack of urgency to get this fixed. The problem has been known for over a month now (nearly 2). I am super disappointed…