I received a CAC-1335 yesterday from Amazon. I want to use it connect a HP Reverb G2 VR Headset to an Aorus 17X YD with an HDMI 2.1 connection to its RTX 3080 discrete graphics cards. The HR Reverb G2 has a DisplayPort 1.4 cable to connect to a PC. This adapter does not enable the connection. I plugged in the USB power first, then the adapter into the HDMI port on the laptop, then connect the DisplayPort to the adapter. The laptop recognizes that the headset is there and then the Windows Mixer Reality Program throws an error code 1-4. What am I doing wrong? The resolution of each eye of the headset is 2160 X 2160 and it runs at a maximum speed of 90 hz. Why does it not work? The same cable will connect to an older laptop with a mini-displayport connection to the discrete graphic card, so the cable it good.
Does the headset appear as a display when used with the CAC-1335?
When connected to DisplayPort without the CAC-1335, does the headset present itself as a 4320 x 2160 display or as two 2160 x 2160 displays? Or the operating system might not show it as a display. I’ve never tried VR before so I’m not sure.
Can you extract the EDID(s) from the headset? Using AMD or Nvidia software? Or using CRU?
If it’s two 2160 x 2160 displays then it won’t work since that would require DisplayPort MST which cannot originate from HDMI.
I’m not sure the adapter was tested with any resolutions other than 3840×2160 or 7680×4320, so you should do your own tests if possible.
Do you have a normal display that you can test the CAC-1335 with? Can you create a 4320×2160 custom resolution for that display using AMD or Nvidia or CRU and test it without the adapter? I have a 4K display that can accept resolutions up to 4K120 or 5K60 or 6K50 or 8K30 as long as the pixel clock does not exceed ≈1080 MHz. Once you know you have a display that can support 4320×2160, you can test the adapter with that mode. You may need to recreate the custom resolution when you switch the connection from DisplayPort to HDMI port.
You said “The same cable will connect to an older laptop with a mini-displayport connection to the discrete graphic card, so the cable it good.” The CAC-1335 has DisplayPort, not Mini DisplayPort. Please explain exactly what is connected to the laptop (adapters, cables, display).
I would try this connection order: USB power, DisplayPort connection to display, HDMI connection to computer.
JoeVT,
Does the EDID data from above give you any indication of the problem? When I closely read the specifications for the HP Reverb G2 it states that only DisplayPort 1.3 is required. Since this adapter supports DisplayPort 1.4 it should work properly. What are we missing?
Also in the specifications it says that resolution is 2160 X 2160 per eye so it makes a display of 4320 X 2160.
Please let me know what else we can check or debug.
Thanks,
Jim
The EDID has a 4320×2160 60Hz mode for HBR2 8bpc RGB/4:4:4 and a 90Hz mode for HBR3 8bpc RGB/4:4:4. There’s no 4:2:2 or 4:2:0 or DSC support. Both of those modes are in the DisplayID 1.3 extension block. The CTA-861 extension block only contains a Microsoft Vendor-Specific Data Block which identifies the device as a Virtual reality headset and assigns a UUID which I suppose can be matched with a UUID of a corresponding USB device for position tracking purposes. Does the headset have a USB connection?
Was the EDID from direct DisplayPort connection or was the CAC-1335 involved? Can you get an EDID with the headset connected to the CAC-1335? It will be interesting to see how the CAC-1335 affects the EDID. I think it might try to add a HDMI 2.1 Vendor-Specific Data Block.
For both connection types (from HDMI and DisplayPort) can you open Device Manager, view by connection, find the headset, and see if it’s attached to Nvidia or Intel GPU?
The EDID has 2880×1440 90Hz mode (428MHz) which is doable by HDMI 2.0 (limit 600 MHz). Did you try this mode?
I am thinking the CAC-1335 and CAC-1336 are more finicky then they should be. Read my post on the CAC-1336. CAC-1336 operation
The fact that you can’t use adapters with them is bad especially the CAC-1336 – not being able to use a USB-C to DisplayPort cable or adapter is just wrong for a USB-C port…
Maybe you would have more luck if you put a Thunderbolt 4 hub between a CAC-1336 and your displayPort cable/adapters. The Thunderbolt controller might act like a DisplayPort repeater. It’s an awfully expensive solution, if it even works.