HMD display is black, but gyro input works???

Hi I have the exact same problem like above.

With the native unity integration. And builds! not in editor.

It appeared after I changed my office and changed my displays also
the sequence they are connected to the machine.

So maybe it has something to do with that ?!

My System is also win7 64bit + intel + GTX 970 but not mobile.
6.0.1 - same issue on 6.0.0 all tested. Unity 5.1.1 p3.

Hello, yes I'm having the same issue as this, a couple of forums seem to be dealing with the same problem.

Everything came up on the headset when I used the old Unity Integration solution, but now with the Unity First Party support, nothing is coming up on the headset. I have a GTX 560 Ti and I'm using the suggested drivers 350.12, Unity v5.1.1.1 but I'm about to test with v5.1.1.4. I updated the oculus SDK and config utility yesterday 0.6.0.1.

Some people have said they get intermittent results, but I've tried a couple of test scenes and nothing is coming up.

Hello guys, I had sometimes this problems and found many things that cause that

First of all:

• If you changed your workstation remember that on Windows 7 you need to do ALL THE UPDATES not only service packs, have some things that you need to update on Windows Update I dont know exactly what updates need to be installed to it works fine, so better update everything. Probably is something like .NET, C++,Visual Studio, etc
  


• Update your GPU Driver, I worked with 550ti and now I'm using 970GTX
  


• Try to use a HDMI to DVI adaptor on your Oculus or on your Monitor, I performed some problems with 2 HDMI, do this trying the two Rift display modes (Direct HMD Access and Extended Desktop to HMD
  


• Check on Configuration Utility if the Oculus and Camera are connected.

I'm using the same system them yours Intel + win7 64bits + GTX 970 + 6.0.1 + Unity 5.1.1 all working fine.

On last case try to reinstall Oculus and try to run a 6.0.1 Demo Scene or the Configuration Utility Demo Scene, check if it works fine

Cheers =)

Thanks for the suggestions, no results so far I'm afraid, the demo scene isn't working either (see below).

- using Windows Update I installed all optional and recommended updates (apart from the 2GB optional language packs)
- I updated to the latest Nvidia GPU drivers
- I tried using a HDMI to DVI adapter
- Oculus Config doesn't show any errors at any point
- I re-installed the oculus runtime

I've mostly been trying things in "direct HMD" display mode. I've just tried a number of things in extended mode, but no results and I REALLY CAN'T STAND extended mode. The best I got in extended mode is a version of the build with the eyes flipped in the headset (so left and right were swapped). That's after trying multiple monitor combinations and squinting down the lenses to see my desktop so I could launch things until I felt dizzy (why extended mode? why?).

At the moment, I can't get either the Oculus World (tuscany) demo or the config utility demo scene to work in either display mode. Both demos just load a black window on my desktop. I used to be able to run Tuscany in extended mode, but no longer. Perhaps this is relevant.

I can however still load the Colosse demo without a problem and see it working in the headset (direct mode).

Can you guys provide these log files (the first 2 if you can):

viewtopic.php?f=34&t=23521

Hello, I think this is what you mean, but please tell me if there's anything else.

oculus_logs.zip

Very sorry, the issue is that your GPU is too old. For Nvidia GPUs you need at least a Keler chip. I'd recommend getting a GTX 970 so that it will last for the consumer Rift.

Balls.

I knew this day would come I just didn't think it'd be so soon :cry: :cry: :cry:

Seriously if anyone has one they'd be willing to part with then I'll build you something in 3D.

@cybereality -

I've been able to get some things to work on the rift (Like the Colosso demo, Oculus World demo) and I feel like I could have gotten away with using the 560ti this time last year, so is this related to Unity 5.1 and/or Oculus 0.6?

Basically if I roll everything back and pretend its still 2014, I can hopefully get a simple scene to work, although I'd need the desktop version of the OculusIntegration for unity, which I can't find anywhere (is it even available?).

Edit - so far the Oculus journey has involved buying the headset and a pro unity licence and its fun but I've now run out of money.

It's a requirement of the 0.6 SDK/runtime. You can roll back to 0.5, but then you won't be able to play any new content, or develop using the new Unity 5.1 VR support. The old files are on the downloads page (click Platform:PC, then the old version).