Some Help With Oculus

There was a lot of discussion here about this stuff when the CV1 first came out, for example ..

https://forums.frontier.co.uk/showthread.php/278996-Rift-hdmi-port-users

https://forums.frontier.co.uk/showt...k-levels-finally-fixed-for-me!-Weird-solution

I think it's to do with the nvidia dynamic range setting not defaulting to "full". This guy tries to explain it ..

https://forums.frontier.co.uk/showthread.php?p=4813271&viewfull=1#post4813271

The adapter that I (and a few othes from those threads) got was this one ..

https://www.amazon.co.uk/gp/product/B013G4EXMM/ref=oh_aui_detailpage_o09_s00?ie=UTF8&psc=1

Seems to work fine.
 
For most 90%+ this shouldn't matter in vr.
It's an issue with some poorly designed displays or if you have a tv connected.
Sure display tech is similar but there are large differences in a tv and a monitors internals.

There is a subset and confluence of issues where some display triggers Nvidia cards to force a limited range, for most when this happen you can override manually, and vr hmd's should not be affected.

In fact I suspect what is happening is that for some this adapter might disable the spud setting for oculus. I have noticed sometimes this happened after a driver update, where blacks where suddenly proper black.
A reboot or oculus service restart and things goes back to slightly more grey.

Although currently I. am employing the registry setting to disable spud and black levels are lovely and deep.
 
Back
Top Bottom