search

sensics / OSVR-RenderManager

Apache License 2.0
64 stars 45 forks source link

Added a new Vendor ID #359

Closed ifresco closed 6 years ago

ifresco commented 6 years ago

Added a new Vendor ID 'NEC' advertised by Lumus' dev kit.

Please merge! Thanks :)

russell-taylor commented 6 years ago

@ifresco Sorry this has taken so long to resolve. Changing the vendor ID of the display will confuse autodiscovery and may cause more troubles than adding the NEC display to DirectMode, so I'm going to go ahead and accept the pull request.

ifresco commented 6 years ago

Thanks a lot! Do I need to now wait for the new RenderManager.dll to show up at the OSVR developer portal in the next release of the runtime/SDK or is there a quicker way to get it?

russell-taylor commented 6 years ago

You can try opening an issue to build a new version but I don't know that it will speed things up. Note that you're still going to have to let the driver know that this device is okay to put into DirectMode. If you're using nVidia or AMD, the enable/disableDirectMode programs will turn it on and off only if it is available as such a display. On Intel, we don't have an enable/disable because you do that all using magic registry stuff.

ifresco commented 6 years ago

Thanks, got it. My target platform is Intel, and I'm looking for info on the registry stuff. Do you have any pointers as to what the procedure is like? I have searched through all of the OSVR documentation, but haven't found anything more specific than stray mentions of Intel requiring some work in the registry.

russell-taylor commented 6 years ago

That information is currently under NDA from Microsoft. You'll need to talk to them about their upcoming extensions for DXGI.