EDIT: SOLVED, it turned out to be a faulty HDMI cable
As far as I know, I'm the only one having this problem. I already have a case opened with Oculus support, but I want to find out if there are more people with this issue (case #106813, if cyberealty wants to ask them).
My DK2 screen goes black when playing games or demos, even the Oculus Scene from the Oculus Runtime App. It usually takes between 5 and 10 minutes, but it always happens using the 0.7 runtime and nVidia 355.83 and 355.84 drivers. First time it happened in Windows 10, so to make sure it wasn't an OS problem, I installed Windows 8.1 on the same computer in a different partition, so now I can dual boot both, and I can reproduce the problem in both partitions. It's a completely clean OS install with all Windows Update patches, chipset drivers, GPU drivers, DirectX, Oculus Runtime and the neccesary C++ runtimes.
All VR apps start fine and run fine on the Rift, I can play for a while, but the DK2 screen turns black after some minutes. When that happens, the mirror screen starts crawling and the CPU usage goes down to 1% while it goes to low speed mode (around 1.2 GHz), the same behaviour than sitting on Windows desktop with no 3D apps launched. The DK2 light goes from blue to orange. If I launch a new VR app it starts fine, but again it goes black after a while, usually faster than before (1 minute or less). I've tested it with Doom 3, Dirt Rally, Ethan Carter and even the Oculus Scene from the runtime.
Under Windows 10 I can't try older nVidia drivers because they won't work with the 0.7 runtime, but under Windows 8.1, downgrading to 355.60 drivers, which don't support Gameworks VR and "direct to driver", make my DK2 runs flawlessly, I can play for hours with no problems at all. Using 355.84 also makes the problem happen in Windows 8.1.
I've sent the OVR service logs to Oculus support and they couldn't find any problems on it, so I'm guessing that there *might* be a problem with "direct to driver" mode on nVidia drivers under certain system configurations. My computer specs are the following:
- Asus Rampage IV Formula (Intel X79)
- Intel i7-3930K (hexa-core)
- 32 GB G.Skill DDR3 2133 Mhz (4x8 Mb quad channel)
- MSI GeForce 980 TI
- Samsung SSD 840 EVO 1 TB
- 1000W PSU
- 4K Crosswind monitor (display port)
I've tried to set my main monitor to 1080P and removed all unnecesary USB devices, but it didn't help. Everything is clocked at default speeds, and the system is completely stable. I've had the DK1 and the DK2 on this computer with no issues until the arrival of 0.7 runtime and the "direct to driver" mode. I've tried both the Intel USB 2.0 ports and the ASMedia USB 3.0 ports on my motherboard and the problem remains. The only way to have no problems is using Windows 8.1 with older nVidia drivers, where it's always rock solid.
Based on my previous experience as AMD driver betatester, the only think I can think of if some kind of incompatibility between "direct to driver" mode and my computer. I already suffered a nasty bug on AMD drivers that only happened on X79 motherboards with multiple cards and monitors. Thanks to the help of the comunity, we helped AMD to squash it, so if that happened in the past... why couldn't be happening again?
Anyone else here with Intel X79 platform? Any problems with "direct to driver" mode on nVidia cards?
Comunidad española de RV / Spanish VR Community