05-15-2015 04:05 PM
06-27-2015 10:22 AM
06-27-2015 01:41 PM
07-04-2015 12:15 AM
07-04-2015 02:10 PM
This issue as a regression from 0.4.4 should be solved in 0.6. Note that the majority of users seeing this error message are not actually experiencing the issue as a regression, but fortunately customer support can help with such cases.
If you're getting this error message, please do the following:
Uninstall the Oculus Runtime, Display Drivers, and Tracking Driver (you can just uninstall everything made by Oculus from "Programs and Features").
Reboot.
Log into your machine and give it several minutes. This will make sure that it picks up default drivers for your hardware.
Install the 0.6 Runtime. This can be found at https://developer.oculus.com/downloads/. If something newer happens to available by the time you see this, use the newer version.
Reboot again after installation.
Switch to Extended mode with Rift Saver off.
Reboot once more.
Open up Config Util and enter into the demo scene. If you can see the demo scene, then the issue is resolved.
If the above steps do not resolve your issue, then do the following (same as above, but this time installing 0.4.4):
Uninstall the Oculus Runtime, Display Drivers, and Tracking Driver (you can just uninstall everything made by Oculus from "Programs and Features").
Reboot.
Log into your machine and give it several minutes. This will make sure that it picks up default drivers for your hardware.
Install the 0.4.4 Runtime. This can be found at https://developer.oculus.com/downloads/ ... 0.4.4-beta.
Reboot again after installation.
Switch to Extended mode with Rift Saver off.
Reboot once more.
Open up Config Util and enter into the demo scene. If still you can not see the demo scene, then you are experiencing a different issue than the main one being discussed here. There can be many causes for this, so please contact Customer Support (https://support.oculus.com/hc/en-us/requests/new) and they should be able to get you sorted out.
If both of the above fail, please contact Customer Support. If the first fails and the second succeeds, then please reply back so we know there's an on-going regression. Thanks everyone for your patience with this!
07-06-2015 11:18 PM
"thatdude90210" wrote:
I just started seeing this issue today. I've had the DK2 since july/aug last year and it's worked fine til today. I was using runtime 5.0.1 and suddenly got the "HMD not detected, tracking camera connected." So I decided to try the latest 6.0.1 runtime, and upgrade my videocard driver. Same issue, only now the error message is "HMD powered off, check HDMI connection." I tried reconnecting the hdmi and usb cables but no difference. And either extended or direct mode makes no difference.
Then I tried a different HDMI cable, and it worked. But it's a short cable so obviously it's not a workable solution. Plus I don't want an extra wire hanging off my DK2. So if my issue is the hdmi cable, how do I go about getting a replacement?
My system is i5 2500k, amd r9 290, windows 7 64-bit. And I don't have teamviewer, plus tried some of the trouble shooting like restarting ovr service that I found googling around.
09-03-2015 05:17 AM