Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
Lhun's avatar
Lhun
Explorer
11 years ago

Does anyone own a dr HDMI and is willing to test something?

I only own a DR DVI from nonoprice, which unless I can provide it false edid info somehow and get it to store it, won't work for this purpose.

http://www.hdfury.com/shop/otherhdfuryhardware/dr-hdmi/

This device allows you to write custom EDID information to a display output. If I am correct (oculus team seems to think so) the edid in detailed line 3, in the extended information of the rift DK is incorrect.

I propose changing the modeline to the correct timing information, to see if that will allow the rift to work under wddm 2.0.

Currently, the standard timing the rift display adapter internally supplies is not listed in the detailed information provided by the CHA extended bit, it is my suspicion that WDDM 2.0 rejects it in favor of the more "accurate" extended bit info.

In short, on Windows 10, on the prerelease DX12 drivers, the rift just blinks in extended mode.

Oculus has not compiled a direct mode driver for windows 10 at this time, and we would not expect that mode to work with this display model (yet. They have confirmed they are working on it.)

I could provide an edid bin that has the correct modeline information. If anyone (or someone at oculus) would like to try this, let me know.
No RepliesBe the first to reply