-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
expose an interface for detecting HDMI will be better... #357
Comments
OSVR Core deals with auto-detection of devices does based on USB signatures, and because the HMDs we've encountered also have associated USB devices for tracking, we can detect the presence of these devices outside of the RenderManager interface, leaving RenderManager to just handle the display portions. The mechanisms for making new HMDs work in "direct mode" vary from graphics-card vendor to vendor and sometimes involve changes to the video drivers themselves so that is not something that we can provide an interface to because it is not something that we have access to. Complicating this is the fact that some HMD vendors require special interaction with their devices to keep them powered on once they have been plugged in. We've been able to incorporate all of this into OSVR but it is sort of a case-by-case process. Can you specify what it is that you as a developer want to do that you are unable to do with the current OSVR Core + RenderManager interface? Maybe we'll be able to figure out a way to provide it within the constraints of the current fragmented state of things. Meanwhile, we're part of the https://www.khronos.org/openxr working group that is trying to develop an industry-standard approach. |
Appreciate for your comment! I just want to confirm whether HMD(HDK2) is in direct mode or not when HMDI plug in. |
@JeroMiya How do we detect the state of and HDK2 (direct or otherwise) in the Sensics control panel? |
hi sensics,
could you plz consider to expose an interface for detecting HDMI in RenderManger? it may be flexible for developers relate to NDA with NVIDIA or others.
The text was updated successfully, but these errors were encountered: