VR is broken now in ED for me.

[CMDR Holycow]

So somewhere in here is a post about how to set your oculus to run at 60hz. I thought I would try it. At first, it seemed to work ok. Framerates were less juddery... but then Dr. Kaii posted up that you can actually use adaptive vsync to do basically the same thing. So I un-did the first steps and put my dk2 back at 75hz, and turned on adaptive vsync. And unfortunately, now the graphics are totally broken in the rift, in ED.

I get TTTEEERRRIIIBBLLLEEE purple fringe smearing when I turn my head, everything is about twice as bright as it is supposed to be, and every color has HUGE boarders between it and the color next to it (i.e. zero smooth transitions). It almost looks like what you get when you turn on like 16 color or something.

I have spent the better part of 4 hours over the last two nights trying to correct this... but I am stumped. I have done the following

1. completely blown away and reinstalled oculus runtime, and let the pc reinstall the drivers
2. Installed fresh graphics driver
3. Set every graphics setting back to it's default (flipped dk2 back to portrait)

I am at a loss.

(EDIT: Other games and demos look ok. BBUUTT if I look REALLY closely, I can see some of the same dark smearing I get in ED, it's just nowhere near as obvious).

 

[bonsek]

Did you try changing the resolution other to what you had in Elite and setting it to go to primary screen/monitor, click apply close the game. Then reopen and change resolution to what you had and set to secondary

 

[atlas974]

Try changing hdmi or dvi port for the dk2
Try also lastest nvidia driver and choose wide gamut color might fixed it
Try deleting the dk2 screen in windows display settings

 

[CMDR Holycow]

Did you try changing the resolution other to what you had in Elite and setting it to go to primary screen/monitor, click apply close the game. Then reopen and change resolution to what you had and set to secondary

I'm not sure what you're saying, but resolution is the same on both my monitor and my dk2 1920x1080. If I change it to primary monitor, it looks fine on my 27". Change it back to secondary, and nothing is different. Looks TERRIBLE beyond description.

 

[bonsek]

Sometime changing resolution, clicking apply and then setting the resolution back to 1080 resets some graphical glitches.
But I just read that the Samsung Note phones have issues with purple smearing. I belive that is what DK2 uses

There are tips how to fix it on the phones but not sure how could be done on the rift :/
http://forum.xda-developers.com/showthread.php?t=2462078

 

[bonsek]

Found this reddit post with a similar issue with your. I hope this fixes your problem.
http://www.reddit.com/r/oculus/comments/2kyl2h/fix_for_crushed_blackdark_range_16bit_look_when/

 

[CMDR Holycow]

Found this reddit post with a similar issue with your. I hope this fixes your problem.
http://www.reddit.com/r/oculus/comments/2kyl2h/fix_for_crushed_blackdark_range_16bit_look_when/

Thanks Bosek.. that IS the same problem I am having, but that wasn't my fix. I am back and running in VR, I will write it up tomorrow when I have time. Thanks for chiming in fellas.

 

[Commander Pew Pew]

Had the same a few days back. Reset some settings in NVCP and it was gone. Not sure what the issue was.

 

[iced01]

Thanks Bosek.. that IS the same problem I am having, but that wasn't my fix. I am back and running in VR, I will write it up tomorrow when I have time. Thanks for chiming in fellas.

An easier fix is to simply you the system restore application within windows to roll your system settings back prior to the change in settings. say the day before. I work in IT for a living and used this to fix the same issue you had a few months ago after one of my development project for oculus went south.

 

[iced01]

Thanks Bosek.. that IS the same problem I am having, but that wasn't my fix. I am back and running in VR, I will write it up tomorrow when I have time. Thanks for chiming in fellas.

An easier fix is to simply you the system restore application within windows to roll your system settings back prior to the change in settings. say the day before. I work in IT for a living and used this to fix the same issue you had a few months ago after one of my development project for oculus went south.

- - - - - Additional Content Posted / Auto Merge - - - - -

Thanks Bosek.. that IS the same problem I am having, but that wasn't my fix. I am back and running in VR, I will write it up tomorrow when I have time. Thanks for chiming in fellas.

An easier fix is to simply you the system restore application within windows to roll your system settings back prior to the change in settings. say the day before. I work in IT for a living and used this to fix the same issue you had a few months ago after one of my development project for oculus went south.

you = use. Sorry posting this from my smartphone sucks.

 

[PetroVitallini]

Ok, here is a few ideas.

1. Check if the dk2 has been set to direct mode in the oculus VR config utility.
2. Run the oculus desk demo to see if low-persistence is activating or do this to re-activate it (no idea if this works, but read that it might somewhere) . Low persistence is, as I have come to understand it, a "mode" which gets activated at high fps levels. (I believed you had to have 75 fps, but it seems it can be achieved with lower) I don`t think there is a toggle key, but you can notice it being activated when your screen goes a bit darker. I think that is because of higher refresh rates, less light is given out by the screen. That said, check your fps in game and googling difficulty with low-persistence might land you a fix.
3. Check if your rift is being slaved to your monitor. Fix for this I believe is to deactivate or turn of your monitor or change your monitor to a resolution that lets you set hz to 75 on the monitor.

edit: I see now that the link to the reddit page covers the things I`ve written here

 

[drkaii]

Thanks Bosek.. that IS the same problem I am having, but that wasn't my fix. I am back and running in VR, I will write it up tomorrow when I have time. Thanks for chiming in fellas.

So happy you fixed it. Was it the adaptive sync? If so I'll remove it right away from the suggestions. And from my PC...

And apologise profusely.

And share an Indi Borboun with you