Getting the Best DK2/CV1/Vive VR Experience: Guide/Compendium
- Thread starter drkaii
- Start date
Sorry for being vague.
The color settings from the Nvidia Control panel (Digital Vibrance etc) were being overridden for the Rift.
Not sure what caused it, but I fixed it.
Also I've found the following. There is a distinct difference in Judder effects depending on what Monitor the Rift is set to.
If it's set to SECONDARY I either I have Judder or Stuttering... because when V-sync is Off I get judder, with V-sync off i get Stutter and in Adaptive it's just mildly better.
If it's set to Primary with V-Sync set to adaptive I can suddenly run the game silky Smooth in many instances, but I keep having the 'water-over-lens' effect sometimes. I think it's actually a form of Tearing.
However even when I do this I can't completely eliminate Judder in Asteroid Fields. As I spend pretty much 80% of my game time in RES zones.. that's really a dissappointment.
I know for SURE now that:
- Judder is not related to FPS, because I overclocked my GTX980 G1 and it tells me I'm always at max FPS for the Rift. (*although I need to try it without the mirror window and with a different FPS tracker just to be sure)
**Mind you I've read that Windows 8.1 could be effecting the FPS on Monitors not set to PRIMARY and this could be the reason for my woes with the Rift as Second monitor, not confirmed though.
Yesterday I reached a state that's very very nice to play.. and I'm kinda afraid to touch any settings now in fear or ruining it again. But we'll see if I can stand the itch. If I can't I'll keep reporting my findings
*Edit: I've proceeded to OC my Card with MSI Afterburner. I'd done it before but removed it as I was getting crashes. I now did it again, differently, less overclock, however the added Frames in ED allowed me to use DSR, which has
added to the Quality of the image quite a bit. If only i could find out why I keep getting slight Judder in Asteroid Fields even with Adaptive V-Sync.
Ok I'm convinced now that whatever you are using to measure fps is wrong. Get OBS, let it mirror the OR screen on your normal screen, and then in game hit ctrl-f. OBS will let you see what is just outside your field of view - the in game fps counter. It should never go above 75. If it goes below about 70 you will see judder.
Also, as has been discussed plenty, RES sites have judder because other ships. It's either bad network code, high AI processessing or a mixture of both. Nothing you can do.
If it's happening JUST in asteroid fields with no other ships, then it's probably DSR. It has to do a lot more work there, as does any anti-aliasing.
It makes a huge difference. 5 frames per second is the difference between pure smoothness and judder. Oculus rift is VERY sensitive to fps drops.
Just experiment until you get it right. Use a sorting method. Pick a definitely safe zone, a definitely crash zone, and go half way. Then if it works go half way towards the crash zone, or half way to the safe zone if it does crash, and keep repeating this until you get it spot on
Last edited:
You were right. I used Fraps today, as before this post I was not aware of that option in OBS. I'll use that today to check it too.
However FRAPS shows me FPS around 69 with my current settings.
Funny enough I have no judder currently. Only when I am in RES and it becomes very crowded do I start to get Judder.
However I can confirm this is when my FPS drops below 60 (according to Fraps.)
I'll use OBS to check again.
But it seems that it's an FPS issue afterall.
Words of wisdom, I just need to find a quick way to put it all back when ED updates as that seems to play bad with my settings.
If using ReShade do I still need SweetFx loaded in the ED folder? I noticed after this last update that it was gone yet the ReShade folder remained.
I can hereby confirm that the source of unfixable judder is the amount of ships in the same instance. It's definitely NOT AI code since I'm experiencing the same thing in a station instance with lots of other player ships.
My guess is it's either Netcode (unlikely) or unoptimized ship LODs displaying too much detail from too far away, even on low settings. I really wish Frontier would fix that.
My guess is it's either Netcode (unlikely) or unoptimized ship LODs displaying too much detail from too far away, even on low settings. I really wish Frontier would fix that.
I'm getting this weird green haze when using reshade. It's hard to explain but everything has a green haze except super black areas. It's really off putting visually, but reshade makes the game look amazing. Has anybody had this? I would prefer to keep using reshade, but I need that haze to go away. Any settings I can turn off?
Also, with all of these settings enabled. What are your in game settings?
Also, with all of these settings enabled. What are your in game settings?
I get it too, restart once maybe twice and all the sudden it will be gone. I really see it at the Frontier screen when it is first loading the entire border on all sides is an ugly green then restart and it is pitch black. Reshade is definitely worth the trouble of restarting as it really brings out textures better than anything I have tried.
Last edited:
Thanks for this
I've seen green haze before, but it wasn't ReShade, it was either a cable issue or a NVCP issue. Sorry I can't help but if you're using the ReShade settings I put up in the OP, then you're seeing something different to me
Maybe I'm losing my mind, but I'm running a GeForce 970 here, and I can't see any difference between antialiasing turned on or off. I can tell the difference very well when I use DSR (which looks lovely but is unusable due to latency). Wasn't ReShade's SMAA antialiasing supposed to be better than DSR? I know ReShade is working because I can switch ASCII on or off. Oh, if only I could use DSR.
Last edited:
The presence of ships does seem to influence latency a lot. I've also noticed that they don't have to be displayed on the screen, it's enough that they show up on the scanner!
The in game AA is very subtle but noticeable on things like ice world textures. ReShade had a better improvement than DSR but it's a different type of effect so both are great. The SMAA of ReShade is barely noticeable, it's the lumasharpening that does the miracle work. If you overclock your 970 you should be able to handle 1.2x DSR very well
Not sure - maybe I am just getting used to the display and my eyes and brain have adjusted - or my expectations are now lower!
It is certainly very playable in default now, GUI mod does of course make further improvements.
I have deactivated the pagefile on SSD - not sure it made much difference.
B-Z
It is certainly very playable in default now, GUI mod does of course make further improvements.
I have deactivated the pagefile on SSD - not sure it made much difference.
B-Z
Been reading and re-reading this thread in anticipation of my DK2 arriving. Finally got it on the weekend and been playing / tweaking away since.
My rig specs are as follows:
- Asus Maximus VII Formula motherboard
- i7 4790K CPU clocked at 4.8 GHz
- 2 x MSI 970s clocked at 1550/8000
- 2 x Intel 730 480GB SSDs in RAID 0
- AOC 28" 4K monitor - 60Hz
- Track IR
- Saitek X45 HOTAS
- Windows 10 preview - build 10049
Before the rift I played at 3840 x 2160 with all settings on max and planet detail increased via manual file editing. Performance was mostly buttery smooth except the odd RES slowdown and hyperspace glithcyness, GPUs were running around mid 80% usage.
So first things first, getting the oculus runtime to work on Win10 is no joke. Normal install doesn't install the display driver. I did various combinations of install / un-install / install in 8.1 compat mode / install without un-install and finally got it to work. Honestly I'm not sure what got it to work, in fact I still get the odd display driver not installed messsage but it works now so I'm not touching it.
Windows 10 with sweetfx is a PITA. I tried the 8.1 guide and got nowhere. Went the reshade route which launches the game without errors but honestly I'm not sure if it's actually doing anything. From other's responses I expected a big difference so need to dig into that a little more.
For my resolution I'm currently running 2560 x 1440 using a custom resolution (method 3). Like others I had missed the GPU scaling options of this setup. Enabled that this morning and it's made a noticeable difference.
My ingame settings are still cranked as they were when I played on my 4K display. For the rift I've disabled bloom and in game AA. All settings still cranked to HIGH/ULTRA and framerate seems to sit nicely at 75 FPS as measure by afterburner.
Haven't tried the HUD settings from above but been playing with these and text is crisp and legible (originally posted on reddit).
<Default>
<LocalisationName>Standard</LocalisationName>
<MatrixRed> -0.2, 0.42, 1 </MatrixRed>
<MatrixGreen> 0, 1, 0 </MatrixGreen>
<MatrixBlue> 0.73, 0, -0.04 </MatrixBlue>
</Default>
Pretty happy with my settings at the moment so won't be tweaking much unless I can enhance the experience much. New Win10 preview build is currently downloading so pretty sure it's all going to turn to crap again
Any questions feel free to ask.
My rig specs are as follows:
- Asus Maximus VII Formula motherboard
- i7 4790K CPU clocked at 4.8 GHz
- 2 x MSI 970s clocked at 1550/8000
- 2 x Intel 730 480GB SSDs in RAID 0
- AOC 28" 4K monitor - 60Hz
- Track IR
- Saitek X45 HOTAS
- Windows 10 preview - build 10049
Before the rift I played at 3840 x 2160 with all settings on max and planet detail increased via manual file editing. Performance was mostly buttery smooth except the odd RES slowdown and hyperspace glithcyness, GPUs were running around mid 80% usage.
So first things first, getting the oculus runtime to work on Win10 is no joke. Normal install doesn't install the display driver. I did various combinations of install / un-install / install in 8.1 compat mode / install without un-install and finally got it to work. Honestly I'm not sure what got it to work, in fact I still get the odd display driver not installed messsage but it works now so I'm not touching it.
Windows 10 with sweetfx is a PITA. I tried the 8.1 guide and got nowhere. Went the reshade route which launches the game without errors but honestly I'm not sure if it's actually doing anything. From other's responses I expected a big difference so need to dig into that a little more.
For my resolution I'm currently running 2560 x 1440 using a custom resolution (method 3). Like others I had missed the GPU scaling options of this setup. Enabled that this morning and it's made a noticeable difference.
My ingame settings are still cranked as they were when I played on my 4K display. For the rift I've disabled bloom and in game AA. All settings still cranked to HIGH/ULTRA and framerate seems to sit nicely at 75 FPS as measure by afterburner.
Haven't tried the HUD settings from above but been playing with these and text is crisp and legible (originally posted on reddit).
<Default>
<LocalisationName>Standard</LocalisationName>
<MatrixRed> -0.2, 0.42, 1 </MatrixRed>
<MatrixGreen> 0, 1, 0 </MatrixGreen>
<MatrixBlue> 0.73, 0, -0.04 </MatrixBlue>
</Default>
Pretty happy with my settings at the moment so won't be tweaking much unless I can enhance the experience much. New Win10 preview build is currently downloading so pretty sure it's all going to turn to crap again
Any questions feel free to ask.
Turns out it was MSI Afterburner. I uninstalled and switched to OC Guru and it's working fine now.
Thanks for the info
and @jvan008, thanks so much for win10 info. I'll try and find a way of incorporating it into the op at some point