OSVR / OSVR-Docs

Unified documentation for the OSVR projects.
Apache License 2.0
89 stars 49 forks source link

hdk2 - screen / display device (HDMI) mostly not detected #131

Open emrum opened 4 years ago

emrum commented 4 years ago

-- got it working a few times, randomly,
but usually the screen (device) is NOT detected . usb device (HDK2) sometimes detected, sometimes errors. firmware hdk2svr-2.00.hex sample scene starts on display 1 (because there is no 2)

is there any particular method that WORKS ? makes me mad.

russell-taylor commented 4 years ago

There were problems with the connectors on the junction box where the HDK plugs into the cables on some of the units. They were very sensitive and sometimes worked intermittently. That may be what you are seeing.

emrum commented 4 years ago

great info , thanks. that part is called (hdk2 osvr) "hmd belt box module" i could try to re-solder ... but ... at that scale (smd), easily happens more harm than good. i wonder where i would get (re-buy) that part !? will try to contact razer support.

russell-taylor commented 4 years ago

These devices are no longer supported, I'm afraid. They are also no longer being manufactured.

emrum commented 4 years ago

-- "repairability score 9 of 10" LOL >-))

MulanVR commented 4 years ago

Before blaming hardware, do turn on display mirror first. If that works solidly then you have a version mismatch in drivers support for direct mode which is controlled by GPU driver, which can also cause intermittent behavior depending on changing drivers version and hardware support strategies from your graphics provider. This actually turned out in the past to be the major issue. All the hardware design is documented in detail on github (hence the reparability score) and there are wiki pages that detail all steps for troubleshooting black screens. As far as you don't grab the unit by the cable, you will actually be fine. Also the belt box shows up on device manager because it has a audio card built in for headphones support.

Hope it helps.

On Mon, 16 Dec 2019, 04:43 emrum, notifications@github.com wrote:

-- "repairability 9 of 10" LOL >-))

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/OSVR/OSVR-Docs/issues/131?email_source=notifications&email_token=ACW223DV3SXDL2RV4PQJMQ3QY2JF5A5CNFSM4J24NTPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG5BXRI#issuecomment-565844933, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACW223A6RWWSBM25TEYXBLLQY2JF5ANCNFSM4J24NTPA .

emrum commented 4 years ago

what , where is "display mirror" ? mirror for what ? and why would that change any HDMI device recognition ?

"hardware support strategies from graphic-card provider " ? sorry, but the rest of my graphics card and driver is working as expected !

"All the hardware design is documented" that is indeed great practice, but still does not mean that I myself with limited budget, time and skills should be debugging any devloper or manifacturer error.

I did not grab , rip any cable at all - don't start blaming me.

thanks for input