DK2 display calibration results

RAJA

R
Hooked up my i1D to Calman 5. This is how things look at default:


Red is the weak aspect of the DK2 display. I took the measurements through the lens (as that is what the eye sees). Luminance of blue and green will need to be dropped for close RGB tracking.



Running a calibration for an ICC profile now.




As stated above, we need to drop 2 to 3fl to get things tracking nicely across the greyscale.


The end result with compare. ICC profile generated, with DE well below perceptive threshold :)

View attachment 40532


System Specs

ASUS Z97 Deluxe
ASUS GTX 980 Matrix
16GB Corsair 2800 Dom Platinum
DK2 (connected to DVI output)
Windows 8.1

​

In theory we should be able to use Color Clutch to inject an ICC profile with ED (NV driver settings can be left at default).
 
Last edited:

rennarda

R
Obvious question is did you perceive any visual difference with this profile ? I'm quite happy with my heavily tweaked display settings via the nVidea control panel - I have nicely detailed Milky Way without it being over bright and no smearing on blacks. Not sure how much better it could get tbh
 

RAJA

R
Absolutely. The difference is immediately apparent. We are capable of picking up De's greater than 3. If you look at the pics I posted above, the De range is over 5 for color accuracy and nearing 7 for greyscale errors. Pulling that all down below 3 is very perceptible to the human eye.

I prefer using a colorimeter to check things. The changes people are making subjectively here have a lot of implications for dynamic range - which is far from ideal.
 
Last edited:

rennarda

R
Great to hear - I'll experiment with the file you shared as I don't have a colorimeter of my own :)
Whereabouts do I apply this ? Is there an option in the nVidia control panel, or the windows system panel ?
 

rennarda

R
Thanks for sharing this - I applied it and it's good. I had almost the same results with my nVidia tweaking, but the detail Barnards Loop for example stands out better with this profile. I recommend this is added to the 'DK2 setup' sticky topic :D
 

RAJA

R
It's likely not perfect for your DK2 as the panel variance will come into play - probably better than running default in places. The NV control panel is okay for setting up brightness and contrast (with test patterns, not by eye as we're terrible at discerning the accuracy of whites and blacks), but greyscale and gamut accuracy is way off. That's where calibration helps massively. Greyscale is the most visible and desirable thing to have accurate given the choice.

Did you use Color Clutch to inject or just using Windows? I'm not sure if the game will use the profile if it's not injected..
 
Last edited:

rennarda

R
I just used colour calibration in Windows to apply it. It must be getting used as I see an improvement comparable to my tweaked nVidia settings (as mentioned above)
 
Last edited:

RAJA

R
rennarda said:
I just used colour calibration in Windows to apply it. It must be getting used as I see an improvement comparable to my tweaked nVidia settings (as mentioned above)
Click to expand...

Okay that is good news. It is likely working then due to extended mode (but can't be sure). Just clarification for anyone reading; the ICC V4 profile should be used with the NV settings I posted, otherwise, everything will shift.


On a crudely and somewhat objectively related sidenote; the flocking used internally around the panel frame can be replaced for improved contrast perception. Our eyes use a reference point to determine what is white and black. The less reflective the frame is, the better. Sticky back flocking paper can be cut to size and placed over the flocking used in the Oculus. At least in my unit, the flocking used is a lot further from "blackness" than "good" flocking paper. Adding good flocking paper will aid perceived black levels and help immersion.
 
Last edited:

[VR] Scifikomori

[VR] Scifikomori
Interesting!

I decided to give this a try, and I' think (I'll have to get back to that after some more testing - plus it's been a while since I've really used E: D atm) the visuals improved for me. I still got some issues with a green/gray haze around nebulaes etc, but they were somewhat less noticeable now. Also, using Oculus runtime 0.4.4, as 0.5.0.1 don't work.. Yet to try the new 0.6, which I'm about to try.

Also: I got two displays including the Rift. In a typical Windows fasion, my Windows 7 Color Management disagrees with both itself (the Screen Resolution settings in Control Panel) and nVidia Control Panel, about which one is display 1 and 2! Tried to remove display drivers and let Windows reinstall them upon reboot, but it turned out exactly the same. Oh well. I just applied the color profile to both atm.

In the screenshot below the Rift is the right-most screen (display 1, or, erroneously shown as a big nr "2" when pressing "Identify monitors" from the Color Management window).

Windows 7 color management.jpg


EDIT:

So now I've also tested the color profiles on my secondary windows partition, nearly identical to the first except not used as much, and not installed as much stuff (plus, it's not on an SSD). And so Oculus runtime 0.5.0.1 worked in that one, but 0.6.0.0. "half-worked" (!). That is, Direct to HMD mode didn't work (only got a black screen), but Extend Desktop to HMD mode works.

It also had the same annoying display identification mismatch. Applied the Rift profile to both displays. But I couldn't really see any difference here, with or without it. (Haven't really compared with and without on my primary Windows, in which the latest Oculus runtime that works is version 0.4.4). Just FYI I guess.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom