Horizons VR experience (Windows 10, Oculus Runtime 8, DK2)

Tankero · Dec 20, 2015

o I've been struggling with Horizons, and there are some lessons I'd like to share. First, my specs.

i5 4670K 3.4gHZ
8 GB RAM
GTX 970 4GB
SSD drive (game saved here)

Now, the hard-earned lessons:

1. First and foremost -- the resolution you set in-game is pointless, it only affects the mirroring window that appears on your desktop.
2. The refresh rate of the main monitor gets inherited by the Oculus -- SET YOUR PRIMARY MONITOR TO 75hz through custom resolutions!
3.NVIDIA DRIVER 359.08 DOES NOT WORK. This driver isn't capable of saving custom resolutions, and therefore can't be used to set the Oculus' refresh rate. Attempting to use this driver leads to Oculus 0.8 Runtime crashes!!
4. DRIVERS 359.00 and 358.91 WORK. They're both stable and VR ready, at least for the EVGA GTX 970 cards.
5. Overclocking your cards is very very very unstable right now. My rig used to be able to run the DK2 with pre-VR (356.xx) drivers with the 0.5 runtime like a rock. Now it can crash if I turn my head too quickly while OCed.

hapklaar · Dec 20, 2015

Tankero said:
o I've been struggling with Horizons, and there are some lessons I'd like to share. First, my specs.

i5 4670K 3.4gHZ
8 GB RAM
GTX 970 4GB
SSD drive (game saved here)

Now, the hard-earned lessons:

1. First and foremost -- the resolution you set in-game is pointless, it only affects the mirroring window that appears on your desktop.
2. The refresh rate of the main monitor gets inherited by the Oculus -- SET YOUR PRIMARY MONITOR TO 75hz through custom resolutions!
3.NVIDIA DRIVER 359.08 DOES NOT WORK. This driver isn't capable of saving custom resolutions, and therefore can't be used to set the Oculus' refresh rate. Attempting to use this driver leads to Oculus 0.8 Runtime crashes!!
4. DRIVERS 359.00 and 358.91 WORK. They're both stable and VR ready, at least for the EVGA GTX 970 cards.
5. Overclocking your cards is very very very unstable right now. My rig used to be able to run the DK2 with pre-VR (356.xx) drivers with the 0.5 runtime like a rock. Now it can crash if I turn my head too quickly while OCed.

1. Totally agree. Too much wrong info about this one in the world

2. I read this everywhere, but strangely for me the DK2 always runs at 75Hz in this (win10, steamvr, rt 0.8) situation, no matter if my main monitor is at 60Hz. My fps counters and low persistence being active seem to support this claim.
..

I still use 0.5 to play. I can play on DK2 with one GTX970 enabled with most settings at high and supersampling ingame at x1.5. SLI is possible, with everything set to max, and supersampling x2.0 judderfree. Only problem is it introduces so much lag it's unplayable.

When I try the 0.8 method I almost get the same experience, but with a little judder now and then. I see no difference with SLI enabled.

Tankero · Dec 20, 2015

hapklaar said:
1. Totally agree. Too much wrong info about this one in the world
2. I read this everywhere, but strangely for me the DK2 always runs at 75Hz in this (win10, steamvr, rt 0.8) situation, no matter if my main monitor is at 60Hz. My fps counters and low persistence being active seem to support this claim.
..

I still use 0.5 to play. I can play on DK2 with one GTX970 enabled with most settings at high and supersampling ingame at x1.5. SLI is possible, with everything set to max, and supersampling x2.0 judderfree. Only problem is it introduces so much lag it's unplayable.

When I try the 0.8 method I almost get the same experience, but with a little judder now and then. I see no difference with SLI enabled.

What are your specs/drivers?

I'm trying to figure out what my bottleneck is.