Everything is working fine but DK2 never gets a video signal

[lohan]

Yes I know there are some threads already touching this or a very similar issue. But since this issue is affecting so many users and there still is not a single official word on this issue I guess it shouldn't be a bad thing to add another thread.

I am on Win 7 64-Bit Home Premium using a GTX-690 graphics card (beside the Oculus DK2 there is the Sony HMZ-T3 plugged into the GTX-690 as well as my main monitor Samsung Syncmaster 2233rz).
I was able to install Oculus Runtime without any problems. The Runtime-application runs flawlessly: My DK2 is detected, camera is working just fine (blue LED always on). I can even launch the desk-demo scene. Since it is displayed on my monitor I even can confirm that headtracking seems to work just fine.

Now here comes the problem: Since I first opened the DK2 I never saw the DK2 screen active. It just never gets a video signal, the specific LED stays orange all the time.

To this point I even didn't get it to work in extended mode.

Right now I am desperate to the point where I will buy a USB 2.0 hub with additional power adapter today because my PC only has USB 3.0 ports which could cause problems according to cyber and some other sources (a USB 2.0 hub plugged into a USB 3.0 port seems to solve this problem).

Any idea?

[CAS]

Same issue. Permanent orange light and no video in the rift. Re installed multiple times, uninstalled then re-installed without restarting, deleted the .sys file, uninstalled the oculus video driver, added power, forced NVIDIA settings. I have NVIDIA 780M running on Win 7 Ultimate. Any suggestions?

[cybereality]

Can you guys try stopping the service (you can do this in Config Util menu) and the manually starting OVRServer_x86.exe in Program Files(x86)/Oculus/Service?

[PacalB]

"cybereality" wrote:
Can you guys try stopping the service (you can do this in Config Util menu) and the manually starting OVRServer_x86.exe in Program Files(x86)/Oculus/Service?

Thank you Cyber, gave this a try, it's a no go this end I'm afraid. It seems to reset the camera but not the HMD.

[ColinB]

Butting in here but my original DK2 did this and I tried multiple fixes.
The only way a signal got through to the headset was with a smart tap to the headset but even that didn't last.
All I had was an orange light !
In the end they sent me out another DK2 which worked fine straight away and has continued to.
So it might be time to bite the bullet and ask for a replacement?

[PacalB]

"ColinB" wrote:
Butting in here but my original DK2 did this and I tried multiple fixes.
The only way a signal got through to the headset was with a smart tap to the headset but even that didn't last.
All I had was an orange light !
In the end they sent me out another DK2 which worked fine straight away and has continued to.
So it might be time to bite the bullet and ask for a replacement?

Guh! I hope it doesn't have to come to that (UK here :cry: ), I just wish I could isolate or get a lead on where the problem is coming from here, whether it's a software or hardware issue? Cybereality, any other suggestions that come to mind perchance?

[dmeeks]

In support of CAS here. I was on a train from Ripon to London with him and tried to get his system to work. Was following this thread and others, looking for solutions. I did every possible action mentioned, including restarting services. And I did them in every possible order! Here's the deal: we know it isn't a bad Rift. During the train ride, I was using mine--which has been working as advertised. Worked fine again on my laptop afterwards. Another problem for CAS, this has been the same issue on two identical laptops and with two separate Rift's (one as mentioned, confirmed operational) The problem lies with the laptop. I know a rig is ideal, but for the traveling VR evangelist--that's not viable. So, what the heck is keeping these laptops from yielding the rift an extended display?

http://imgur.com/PbfM1ez I look like I'm accomplishing something, but then again, the desperation hasn't set in. Gave up by London.

Dan

[ColinB]

"PacalB" wrote:

"ColinB" wrote:
Butting in here but my original DK2 did this and I tried multiple fixes.
The only way a signal got through to the headset was with a smart tap to the headset but even that didn't last.
All I had was an orange light !
In the end they sent me out another DK2 which worked fine straight away and has continued to.
So it might be time to bite the bullet and ask for a replacement?

Guh! I hope it doesn't have to come to that (UK here :cry: ), I just wish I could isolate or get a lead on where the problem is coming from here, whether it's a software or hardware issue? Cybereality, any other suggestions that come to mind perchance?

Well I am here in Australia and the unit came really quickly. Was sent more or less immediately after a few Emails.
But all the best in your efforts.
I know I tried everything possible just like you.
But who knows?

[Anonymous]

Just FYI, if anyone's interested: Forget everything I said earlier! I thought I had some kind of handle on this. I'm reverting back to the "it's magic!" statement.

Disconnecting the HMD and HDMI cable entirely from the PC and each other, then reconnecting them, all while the PC is off, then turning on the PC, don't work. Might be worth noting that the HMD starts up in the "on" state with the constant orange led light after the computer has started up. But turning the HMD off, then disconnecting and reconnecting the HDMI from the back of the PC while the PC is on, works. (So far..).

Just thought I should mention this.

(TTT..)

[PacalB]

"raron" wrote:
Just FYI, if anyone's interested: Forget everything I said earlier! I thought I had some kind of handle on this. I'm reverting back to the "it's magic!" statement.

Disconnecting the HMD and HDMI cable entirely from the PC and each other, then reconnecting them, all while the PC is off, then turning on the PC, don't work. Might be worth noting that the HMD starts up in the "on" state with the constant orange led light after the computer has started up. But turning the HMD off, then disconnecting and reconnecting the HDMI from the back of the PC while the PC is on, works. (So far..).

Just thought I should mention this.

(TTT..)

Thanks for the heads up Raron, tried this also .... all that happens is the HMD no signal light comes back on, (either in extended or direct mode). Tell me, if you have it in extended mode, when you plug it back in is it a blue light you are getting? If so, that's not what I'm seeing here, I just get constant orange.

[ColinB]

"PacalB" wrote:

"raron" wrote:
Just FYI, if anyone's interested: Forget everything I said earlier! I thought I had some kind of handle on this. I'm reverting back to the "it's magic!" statement.

Disconnecting the HMD and HDMI cable entirely from the PC and each other, then reconnecting them, all while the PC is off, then turning on the PC, don't work. Might be worth noting that the HMD starts up in the "on" state with the constant orange led light after the computer has started up. But turning the HMD off, then disconnecting and reconnecting the HDMI from the back of the PC while the PC is on, works. (So far..).

Just thought I should mention this.

(TTT..)

Thanks for the heads up Raron, tried this also .... all that happens is the HMD no signal light comes back on, (either in extended or direct mode). Tell me, if you have it in extended mode, when you plug it back in is it a blue light you are getting? If so, that's not what I'm seeing here, I just get constant orange.

Just keep hoping you don't need another DK2??
Just for interest, do you have a timeframe until you giveup on this and ask for a replacement?
You are certainly a very patient customer !