New to the forums? Click here to read the "How To" Guide.
Developer? Click here to go to the Developer Forums.
Developer? Click here to go to the Developer Forums.
HMD Sensor Detected, check HDMI connection
Lol new runtime and sdk new error message in the config util
with version 4.4 and 5.01 I had the "No HMD detected" error
now with version 6 I get a new error message "HMD Sensor Detected, check HDMI connection"
I cannot make sense of this message as it seems a little contradictory. I tried connecting the hdmi cable to another port with the dvi adapter and it still showed the same message. Very frustrating as I have not been able to get the rift to run on my new high end computer I purchased in January. BTW the hdmi cable is fine as the rift works on another family members computer with runtime 5.01 but as it is somebody else's computer I have very limited access to it.
with version 4.4 and 5.01 I had the "No HMD detected" error
now with version 6 I get a new error message "HMD Sensor Detected, check HDMI connection"
I cannot make sense of this message as it seems a little contradictory. I tried connecting the hdmi cable to another port with the dvi adapter and it still showed the same message. Very frustrating as I have not been able to get the rift to run on my new high end computer I purchased in January. BTW the hdmi cable is fine as the rift works on another family members computer with runtime 5.01 but as it is somebody else's computer I have very limited access to it.
0
Comments
Still awaiting help.
Is your Rift being detected in Windows while in extended mode? That is, can you see it in Windows' "Screen Resolution" configuration? Mind posting a screenshot with the DK2 display selected if so? This will give us some info to go on.
The message itself (now more specific in 0.6) can mean anything from incompatible 3rd party drivers, to bad cables, to loose cables, to a hardware failure. The easiest place to start is with a different set of cables plugged into different video and USB ports.
Cleak with my problem specifically, I am having this issue only while in extended mode. I am posting two pics for you one when in direct and on with extended selected.
http://imgur.com/j6tuZn3 (extended)
http://imgur.com/OCDiFYt (direct)
http://imgur.com/7MHf7xR (direct showing the headset working)
As you can see for me at least this would rule out it being a cable or hardware issue. I am about to bash my head against a wall trying to figure out how to make this work. If anyone on the Rift team would like to remote into my computer I would be fine with that as well.
Other forums and reddit have said the only way they have fixed this issue in the past is a complete windows wipe and reinstall. (Which seems quite dramatic.) but if that has worked for others, I dont know if that means hardware or cable failure.
I've tried different ports. but since it works flawlessly in direct mode, that means the hardware is fine right?
EDIT: I've just installed 4.4 runtime, and it seems to work fine on extended mode there. The hardware is running okay. seems to simply be an issue at 5.0.1 and above.
To plug in to another computer. The rift wakes up, get detected and then I plug it back to my original PC. I can play for about 4h and then the rift gets back to "HMD Sensor Detected, check HDMI connection"
I am using the rift on an ASUS ROG G750JH (Gforce GT780M 3go / 16Gb DDR3)
{ "Time": "2015-05-20_17:57:21", "SDK Version": "0.6.0.0", "Service Protocol": { "Major": 1, "Minor": 5, "Patch": 0 }, "RemoteProtocolVersion": { "Major": 1, "Minor": 5, "Patch": 0 }, "Service Running Time": { "Hours": 0, "Minutes": 8, "Seconds": 39 }, "System Specifications": { "Operating System": "Microsoft Windows 7 Home Premium ", "Processor": "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz", "Graphics Adapters": [{ "Name": "NVIDIA GeForce GTX 980", "Video Controller RAM (MB)": 4095, "Driver Version": "9.18.13.4788", "Video Mode": "1680 x 1050 x 4294967296 colors" }, { "Name": "Intel(R) HD Graphics 3000", "Video Controller RAM (MB)": 2108, "Driver Version": "9.17.10.3347", "Video Mode": "1080 x 1920 x 4294967296 colors" }], "Total RAM (GB)": 16, "USB Tree": [{ "name": "Etron USB 3.0 Extensible Host Controller", "deviceid": "PCI\\VEN_1B6F&DEV_7023&SUBSYS_50071458&REV_01\\4&18803EC9&0&00E4", "caption": "Etron USB 3.0 Extensible Host Controller", "manufacturer": "Etron Technology Inc.", "Devices": [{ "manufacturer": "Etron Technology Inc.", "name": "Etron USB 3.0 Extensible Root Hub" }] }, { "name": "Etron USB 3.0 Extensible Host Controller", "deviceid": "PCI\\VEN_1B6F&DEV_7023&SUBSYS_50071458&REV_01\\4&1B0D22A2&0&00E5", "caption": "Etron USB 3.0 Extensible Host Controller", "manufacturer": "Etron Technology Inc.", "Devices": [{ "manufacturer": "Etron Technology Inc.", "name": "Etron USB 3.0 Extensible Root Hub" }, { "manufacturer": "(Standard system devices)", "name": "USB Input Device" }, { "manufacturer": "Microsoft", "name": "HID-compliant mouse" }] }, { "name": "Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C26", "deviceid": "PCI\\VEN_8086&DEV_1C26&SUBSYS_50061458&REV_05\\3&13C0B0C5&0&E8", "caption": "Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C26", "manufacturer": "Intel", "Devices": [{ "manufacturer": "(Standard USB Host Controller)", "name": "USB Root Hub" }, { "manufacturer": "(Generic USB Hub)", "name": "Generic USB Hub" }] }, { "name": "Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C2D", "deviceid": "PCI\\VEN_8086&DEV_1C2D&SUBSYS_50061458&REV_05\\3&13C0B0C5&0&D0", "caption": "Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C2D", "manufacturer": "Intel", "Devices": [{ "manufacturer": "(Standard USB Host Controller)", "name": "USB Root Hub" }, { "manufacturer": "(Generic USB Hub)", "name": "Generic USB Hub" }, { "manufacturer": "(Generic USB Hub)", "name": "Generic USB Hub" }, { "manufacturer": "(Standard USB Host Controller)", "name": "USB Composite Device" }, { "manufacturer": "(Standard system devices)", "name": "USB Input Device" }, { "manufacturer": "(Standard keyboards)", "name": "HID Keyboard Device" }, { "manufacturer": "(Standard system devices)", "name": "USB Input Device" }, { "manufacturer": "Microsoft", "name": "HID-compliant consumer control device" }, { "manufacturer": "(Standard system devices)", "name": "HID-compliant device" }, { "manufacturer": "(Standard system devices)", "name": "HID-compliant device" }, { "manufacturer": "(Standard system devices)", "name": "HID-compliant device" }, { "manufacturer": "(Standard USB Host Controller)", "name": "USB Composite Device" }, { "manufacturer": "Oculus VR", "name": "Oculus DK2 Tracker" }, { "manufacturer": "(Generic USB Hub)", "name": "Generic USB Hub" }, { "manufacturer": "(Standard system devices)", "name": "USB Input Device" }, { "manufacturer": "(Standard system devices)", "name": "HID-compliant device" }] }] }, "Drivers": [{ "Path": "\\system32\\OVRDisplay64.dll", "Version": "1.2.5.0" }, { "Path": "\\system32\\OVRDisplayRT64.dll", "Version": "1.2.5.0" }, { "Path": "\\syswow64\\OVRDisplay32.dll", "Version": "1.2.5.0" }, { "Path": "\\syswow64\\OVRDisplayRT32.dll", "Version": "1.2.5.0" }, { "Path": "\\system32\\drivers\\RiftEnabler.sys", "Version": "1.2.5.0" }, { "Path": "\\system32\\OVRDisplay32.dll", "Version": "1.2.5.0" }, { "Path": "\\system32\\OVRDisplayRT32.dll", "Version": "1.2.5.0" }, { "Path": "\\system32\\drivers\\OCUSBVID.sys", "Version": "1.0.10.0" }], "Video Device Tree": [{ "Name": "NVIDIA GeForce GTX 980", "VRAM (MB)": 3072, "Monitors": [{ "Name": "\\\\.\\DISPLAY1", "Width": 1680, "Height": 1050, "Refresh Rate": 59 }, { "Name": "\\\\.\\DISPLAY2", "Width": 1920, "Height": 1080, "Refresh Rate": 75 }] }], "Devices": [] }Unplugging everything and replugging everything seemed to work. Strange that the connection issue only affects extended mode.
i have also the same problem on 0.6.0.0 on "Extended Mode" .. everything works fine with older runtimes both Direct and Extended.
using gtx980 on asus VH238 monitor with Win 7 64bit. ... for dedails see dxdiag.txt attached.
also running all sorts of software like skype, steam, nvidia experience, evga precision etc.
regards
The issue came up again. I tried turning off g-sync, swapping usb ports (I can't swap HDMI ports since the 980 only has one), and even replacing the HDMI cable with another but I still get the same issue. Attached are my DxDiag.txt and screenshot. Any help would be appreciated.
lol and it mysteriously went away. Extended mode works fine again. Seems like an intermittent issue. Maybe cabling? But then why does direct to rift always work.
here is the rift diag
My configs:
1. Windows 7, Aero Disabled.
2. Asus Graphics Card
3. Logitech Wireless keyboard and mouse (Read somewhere there is a conflict with these drivers)
3. SDK: 0.6.0.0
When in direct mode - HMD is detected and shown in config-utility tool. However, in extended mode it says - HMD sensor detected check HDMI connection. Please note that I can still experience VR in extended mode by running content in main desktop and then pressing windows+P repeatedly to select extended mode in display settings.
Another strange thing that has happened along with this is that the demo and the measure IPD no no longer work in either mode and I just get a blank screen.
I tested an older version of runtime 0.4 and it worked perfectly but since it is not compatible with many tools like virtual desktop had to revert back to find the problem persists. Has anybody find a solution to this strange behavior?
In Extended Mode it's possible the display configuration is wrong. Make sure the DK2 is set to 1920x1080 @ 75Hz in portrait orientation. Also be sure that the position of the Rift is to the right and on the same level as your monitor (none of the coordinates can be negative).
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
I installed WebVR enabled versions of both chrome and firefox and tried to test the mozvr demos. If I am on the direct display mode in config tool head tracking does not work but the screen shows up in HMD. On the other hand, in the extended mode no screen shows up since HMD is not detected - but the head tracking works. Not sure if this is a bug related to the thread's topic but it seems so.
I am guessing, the HMD not being detected in both the direct and extended modes is a big problem as many others have been reporting this and if a sure shot solution can be ascertained it will possibly lead to solutions of many other problems as well.
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.
I had the same problem, directmode = HMD works fine, Extended - it doesn't power up.;
Elite Dangerous's performance in DirectHMD mode is apalling on a phenom II x4.
here is team oculus's most recent responce from another thread;
viewtopic.php?f=34&t=22006&start=80
MY FIX;
i followed the instructions
(installing the runtime with the rift turned on seemed to be the only thing i hadnt tried)
I also unplugged an unused monitor from my graphics card (750ti, 3 ports)
Either unplugging the monitor or installing the runtime with the dk2 turned on.. fixed the issue.
I hope this helps someone
(unfortunately now, in extended mode, the HMD powers up but the headset doesn't.. amber light, staring at me.
which has happened many times before.
too tired to tackle the issue. Least the HMD is working.)
http://res2.windows.microsoft.com/resbo ... e92_52.jpg
Oculus was accidentally set to disabled