Hey guys,

I was just wondering/ hoping someone else also had this experience.

Here's the story:

- I've upgraded the Oculus Rift runtime from v0.6 to 0.7

- the positive thing is that there's no more switching between direct mode and extended display

(Always direct now)

-- with the side effect that most applications compiled for v0.6 wont run anymore, but I've accepted that

(there are ways to switch realtime between 0.6 and 0.7 but I wont bother)

The problem I'm expiriencing, is that sometimes when I startup my PC, I don't get a signal to my primary display. Because the desktop is sent to the Rift (DK2). When I shutdown (ALT+F4, enter) and startup the PC again, my display works fine again.

Till now it seems random, I can't find any pattern yet.

Any thoughts or similar expierences?

I've had so many problems with my DK2 conflicting with my main monitors in countless ways that I've just given up at this point. I hope they eventually get things figured out before the consumer edition releases, because this is just intolerable.

Thanks for the confirmation.
As long as I used runtime 0.6 it went quite well, accepting I had to switch to extended desktop every once and a while. Going for only direct mode in 0.7 sounds like a step in the right direction. But unfortunately drivers are messing up with each other. I've also read something about a newer version, but probably no applications wont run when I install that version (unless they introduce some sort of backwards compatibility)

Huh, haven't had any problems myself with 0.7, or 0.8 (which just came out, I did need to update my driver for that one). What OS?

Windows 7, 64bit

I'm on Win 10, so maybe it's an OS issue? Supposedly 0.8 is backwards compatible, but I haven't tested to thoroughly beyond seeing that Unity still worked =)

I was having problems on both Windows 8.1 64-bit and Windows 10 64-bit. GeForce 980 GTX. DisplayPort for my two monitors and HDMI for the DK2 simultaneously. The video card can (supposedly) drive all three ports at the same time. One of my monitors is in portrait orientation at 60Hz. The other is landscape at 144Hz. The portrait monitor's desktop X coordinates are negative, and Y coordinates extend above and below the span of the primary (landscape) monitor -- incidentally, this layout causes a bug in Visual Studio's status bar getting cut halfway off.

No idea if any of that affects the DK2. I didn't have the patience to trial-and-error my way through tracking down the root cause.

This might sound stupid, but after about a year I recalled that you can actually turn the HMD off. This helps a lot for this issue. Just turn it on only if you want to actually use it :)