fitness88 Posted April 11, 2018 Share Posted April 11, 2018 version 2.5 Last night's first night flight in months, I noticed it looked like there was dust everywhere I looked, as though I was looking through a nylon stocking. Anyone have this happen? Thank you. Link to comment Share on other sites More sharing options...
A Hamburgler Posted April 11, 2018 Share Posted April 11, 2018 Agree its fine with the A-10 but I have the same issue with the AV8B. Link to comment Share on other sites More sharing options...
fitness88 Posted April 11, 2018 Author Share Posted April 11, 2018 (edited) Off the web: This works I tried it. EDIT: this is not correct it is a problem with Oculus not DCS It's a problem with DCS, I don't need to do this fix for similar environments in other games. But because night flying graphics are so poor in 2.5 I don't bother flying at night. I read DCS is working on the night flight issues. It seems since the last update when looking into darkness I see a fine film of what looks like dust particles [see attachment]. I read an online article: "the need to disable "SPUD" (Oled Mura)" 1- Disable OVRService from Task manager (Services tab) 2- Open Regedit.exe and go to HKEY_LOCAL_MACHINE > Software 3- Right click on the Software folder > New > Key and name the new folder "Oculus" 4- Right click on the Oculus folder > New > DWORD 32bit Value and name it UseSpud 5- Set the value to 0 6- Start OVRService again and put on your headset 7- (Probably) be amazed at how everything looks clean and black Edited May 18, 2018 by fitness88 Link to comment Share on other sites More sharing options...
wrd7105 Posted May 17, 2018 Share Posted May 17, 2018 Hi all, the green haze when flying night sorties in 2.5 Stable with my Mirage is terrible. Is the disabling of the SPUD as per fitness88 recommendation the proven solution? I have seen "turn of deferred Shading" and also resetting NVidia specs. Can someone say that there is a tried and tested way to remove the MURA from night flights yet? Link to comment Share on other sites More sharing options...
fitness88 Posted May 17, 2018 Author Share Posted May 17, 2018 Hi all, the green haze when flying night sorties in 2.5 Stable with my Mirage is terrible. Is the disabling of the SPUD as per fitness88 recommendation the proven solution? I have seen "turn of deferred Shading" and also resetting NVidia specs. Can someone say that there is a tried and tested way to remove the MURA from night flights yet? The registry edit took away 90% of the issue I described having. It takes 1 minute to do and if you don't feel it's doing anything for you just delete the edit. Link to comment Share on other sites More sharing options...
wrd7105 Posted May 17, 2018 Share Posted May 17, 2018 thanks mate, really appreciate your help. followed the steps and its a totally new game. beautiful deep blacks, no Mura and can now night fly properly. Link to comment Share on other sites More sharing options...
fitness88 Posted May 17, 2018 Author Share Posted May 17, 2018 thanks mate, really appreciate your help. followed the steps and its a totally new game. beautiful deep blacks, no Mura and can now night fly properly. Glad to help. I've been in communications with the techs at Oculus. They had no idea what I was talking about let alone how to fix it...very strange! Link to comment Share on other sites More sharing options...
Kayos Posted May 17, 2018 Share Posted May 17, 2018 Glad to help. I've been in communications with the techs at Oculus. They had no idea what I was talking about let alone how to fix it...very strange! So it's an Oculus issue and not a DCS issue? [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
fitness88 Posted May 17, 2018 Author Share Posted May 17, 2018 So it's an Oculus issue and not a DCS issue? Correct. Link to comment Share on other sites More sharing options...
wrd7105 Posted May 17, 2018 Share Posted May 17, 2018 Hi all and just to finish off my experience, I also fly the Gazelle and struggled with the very blurred dash. It was also due to very poor dark colours but the suggested fix has also worked to sort this out. The Gazelle’s interior has just come to life after the changes. Crystal clear dials, interior lights and all that you can see in the cockpit is now so much better. I would recommend this fix to anyone wanting crisp sharp visuals in VR. I have even noticed the changes to terrain and weather which are now beautifully clear and crisp. I thought I would share my system if that also helps. ASRock Z370 extreme, i7 8700K, GTX 1080ti extreme edition, 32G Vengeance 3200 Ram, cooler master water cooling, 2x250G Evo 960 SSD with one dedicated to DCS and the other for Windows etc, Windows 10 64bit OS, Oculus Rift CV1 and nothing overclocked, full Warthog throttle and joystick HOTAS. Thanks everyone. Link to comment Share on other sites More sharing options...
fitness88 Posted May 18, 2018 Author Share Posted May 18, 2018 I just edited my original post... Link to comment Share on other sites More sharing options...
kunterbunt Posted May 18, 2018 Share Posted May 18, 2018 Hi all and just to finish off my experience, I also fly the Gazelle and struggled with the very blurred dash. It was also due to very poor dark colours but the suggested fix has also worked to sort this out. The Gazelle’s interior has just come to life after the changes. Crystal clear dials, interior lights and all that you can see in the cockpit is now so much better. I would recommend this fix to anyone wanting crisp sharp visuals in VR. I have even noticed the changes to terrain and weather which are now beautifully clear and crisp. I thought I would share my system if that also helps. ASRock Z370 extreme, i7 8700K, GTX 1080ti extreme edition, 32G Vengeance 3200 Ram, cooler master water cooling, 2x250G Evo 960 SSD with one dedicated to DCS and the other for Windows etc, Windows 10 64bit OS, Oculus Rift CV1 and nothing overclocked, full Warthog throttle and joystick HOTAS. Thanks everyone. What amount of pixel density are you using, also called super sampling. It might have an impact on this effect. My Rig: AMD Ryzen 9 3950X | 64GB DDR4-3200 Ram | NVIDIA GeForce RTX 2080 Ti | Thrustmaster Hotas Warthog | MFG Crosswind rudder pedals | HP Reverb Link to comment Share on other sites More sharing options...
FoxDelta Posted May 18, 2018 Share Posted May 18, 2018 SPUD was intentionally by oculus, to speed the response time of the single pixels up, otherwise black pixels would go to sleep(sounds strange, of course in milliseconds), this ms delay got people motion sick, so they changed it to this. disabling SPUD as mentioned in this thread fixes they grey looking pixels, this is definately an intended issue on the oculus side, because its very technically and needs more knowledge of their system i would assume their employes on the support side dont even know about that. PD does not change anything, for a better explanation google "how to disable spud oculus" which guides u to the original FIX, this threads (several) regarding dcs night lighting came up with 2.5s dark night, but spud was already enabled before, just not recognized by the people my projects: https://www.sim-addons.com/ https://www.shapeways.com/shops/sim-addons-1 AV8B nozzle lever https://forums.eagle.ru/showthread.php?t=233670 F18C fingerlifts https://forums.eagle.ru/showthread.php?t=234747 F18C radar elevation https://forums.eagle.ru/showthread.php?t=248080 Link to comment Share on other sites More sharing options...
kunterbunt Posted May 21, 2018 Share Posted May 21, 2018 Off the web: This works I tried it. EDIT: this is not correct it is a problem with Oculus not DCS It's a problem with DCS, I don't need to do this fix for similar environments in other games. But because night flying graphics are so poor in 2.5 I don't bother flying at night. I read DCS is working on the night flight issues. It seems since the last update when looking into darkness I see a fine film of what looks like dust particles [see attachment]. I read an online article: "the need to disable "SPUD" (Oled Mura)" 1- Disable OVRService from Task manager (Services tab) 2- Open Regedit.exe and go to HKEY_LOCAL_MACHINE > Software 3- Right click on the Software folder > New > Key and name the new folder "Oculus" 4- Right click on the Oculus folder > New > DWORD 32bit Value and name it UseSpud 5- Set the value to 0 6- Start OVRService again and put on your headset 7- (Probably) be amazed at how everything looks clean and black tried this and did not see any change. If it is the grainy filter that can be seen in very dark scene, then it is still there. Any ideas? My Rig: AMD Ryzen 9 3950X | 64GB DDR4-3200 Ram | NVIDIA GeForce RTX 2080 Ti | Thrustmaster Hotas Warthog | MFG Crosswind rudder pedals | HP Reverb Link to comment Share on other sites More sharing options...
fitness88 Posted May 21, 2018 Author Share Posted May 21, 2018 tried this and did not see any change. If it is the grainy filter that can be seen in very dark scene, then it is still there. Any ideas? Did you make sure to disable first the ovrservice and did exactly as mentioned above then restart the ovrservice? Link to comment Share on other sites More sharing options...
kunterbunt Posted May 22, 2018 Share Posted May 22, 2018 Did you make sure to disable first the ovrservice and did exactly as mentioned above then restart the ovrservice? Yes, thanks. Interestingly, I had an entry in the registry that starts with oculus but ends with inc something. Sorry, not at my computer currently. Is it possible this entry is no longer valid with the new version? My Rig: AMD Ryzen 9 3950X | 64GB DDR4-3200 Ram | NVIDIA GeForce RTX 2080 Ti | Thrustmaster Hotas Warthog | MFG Crosswind rudder pedals | HP Reverb Link to comment Share on other sites More sharing options...
fitness88 Posted May 22, 2018 Author Share Posted May 22, 2018 Yes, thanks. Interestingly, I had an entry in the registry that starts with oculus but ends with inc something. Sorry, not at my computer currently. Is it possible this entry is no longer valid with the new version? Are you sure then that you effectively created the correct registry edit in the correct place? Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Oculus Link to comment Share on other sites More sharing options...
kunterbunt Posted May 22, 2018 Share Posted May 22, 2018 Are you sure then that you effectively created the correct registry edit in the correct place? Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Oculus Yes, but let me share the export from regedit. Look as if regedit will not export the first part "computer". [HKEY_LOCAL_MACHINE\SOFTWARE\Oculus] "UseSpud"=dword:00000000 But I also added the same value to the existing key [HKEY_LOCAL_MACHINE\SOFTWARE\Oculus VR, LLC] "UseSpud"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Oculus VR, LLC\LibOVR] "AswEnabled"=dword:00000001 My Rig: AMD Ryzen 9 3950X | 64GB DDR4-3200 Ram | NVIDIA GeForce RTX 2080 Ti | Thrustmaster Hotas Warthog | MFG Crosswind rudder pedals | HP Reverb Link to comment Share on other sites More sharing options...
fitness88 Posted May 22, 2018 Author Share Posted May 22, 2018 Yes, but let me share the export from regedit. Look as if regedit will not export the first part "computer". [HKEY_LOCAL_MACHINE\SOFTWARE\Oculus] "UseSpud"=dword:00000000 But I also added the same value to the existing key [HKEY_LOCAL_MACHINE\SOFTWARE\Oculus VR, LLC] "UseSpud"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Oculus VR, LLC\LibOVR] "AswEnabled"=dword:00000001 This is mine: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Oculus] "UseSpud"=dword:00000000 I don't have the other 2 entries you have. Maybe its causing the non-response. Link to comment Share on other sites More sharing options...
kunterbunt Posted May 22, 2018 Share Posted May 22, 2018 This is mine: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Oculus] "UseSpud"=dword:00000000 I don't have the other 2 entries you have. Maybe its causing the non-response. Wait, you tell me that you do not have the “Oculus VR, LLC” key in your registry? That was generated by oculus, not me. I only added the UseSpud in that key. My Rig: AMD Ryzen 9 3950X | 64GB DDR4-3200 Ram | NVIDIA GeForce RTX 2080 Ti | Thrustmaster Hotas Warthog | MFG Crosswind rudder pedals | HP Reverb Link to comment Share on other sites More sharing options...
fitness88 Posted May 22, 2018 Author Share Posted May 22, 2018 This is what my reg looks like: Capture.JPG Link to comment Share on other sites More sharing options...
skouras Posted May 22, 2018 Share Posted May 22, 2018 nicely done [sIGPIC][/sIGPIC]W10(64bit)Asus Rog Strix Z370-F - i7 8700K - Dark Rock Pro 4 - 16 giga ram Corsair vengeance 3000 - MSI RTX 2070 Super - Asus Rog Phobeus soundcard - Z906 Surround speaker - Track ir5 - HOTAS Warthog Link to comment Share on other sites More sharing options...
HawkeyeHHDF Posted July 2, 2018 Share Posted July 2, 2018 Just tried it, it looks so much better at night , somewhat better during day but a huge difference, good find Hawkeye VF-213 CO VCVW-11 http://www.vcvw-11.com Heatblur F-14 SME Link to comment Share on other sites More sharing options...
kunterbunt Posted July 2, 2018 Share Posted July 2, 2018 Wow, never got this to work for me. My Rig: AMD Ryzen 9 3950X | 64GB DDR4-3200 Ram | NVIDIA GeForce RTX 2080 Ti | Thrustmaster Hotas Warthog | MFG Crosswind rudder pedals | HP Reverb Link to comment Share on other sites More sharing options...
hansangb Posted July 2, 2018 Share Posted July 2, 2018 Wow, never got this to work for me. With registry edits, I find that people get the location wrong when creating the value. HKLM vs HK Current User, for example. Or not setting it as DWORD (although it's the default, I believe). Regardless, you have you made sure your registry setting is where it should be? I would double check that first. hsb HW Spec in Spoiler --- i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1 Link to comment Share on other sites More sharing options...
Recommended Posts