DK2 not work in direct display mode

[yangjiudan]

when I use my dk2 hmd to test OSVR with this OSVR-Oculus-Rift plugin,
I try the RenderManagerD3DExample3D.exe, and works fine in extend display mode.
but failed in direct display mode, with error:
RenderManagerNVidiaD3D11::OpenDisplay: Invalid display mode index: -1 (mode not found based on either index or parameters).
the related source code is public, so I cound not figure out what the problem is.
any one has met this problem? or know how to fix this?
notes: my dk2 works fine with oculus demo in direct mode.

[grobm]

What version of runtime are you using?

-Mark

------ Original Message ------
From: "yangjiudan" [email protected]
To: "OSVR/OSVR-Oculus-Rift" [email protected]
Sent: 6/16/2016 10:02:56 PM
Subject: [OSVR/OSVR-Oculus-Rift] DK2 not work in direct display mode
(#17)

when I use my dk2 hmd to test OSVR with this OSVR-Oculus-Rift plugin,
I try the RenderManagerD3DExample3D.exe, and works fine in extend
display mode.
but failed in direct display mode, with error:
RenderManagerNVidiaD3D11::OpenDisplay: Invalid display mode index: -1
(mode not found based on either index or parameters).
the related source code is public, so I cound not figure out what the
problem is.
any one has met this problem? or know how to fix this?
notes: my dk2 works fine with oculus demo in direct mode.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[yangjiudan]

thanks for help.
0.8 runtime.
after some test, when I change renderManager.direct.landscape.json to renderManager.direct.portrait.json, my dk2 works now.
but my another dk2 compatible HMD failed again, with erro:
OSVR RenderManager Warning: Got error from NVIDIA API: NVAPI call returned -180
(hex: ffffff4c) [NVAPI_INVALID_CONFIGURATION]
RenderManagerNVidiaD3D11::OpenDisplay: Could not acquire display access for vend
or ID 0xd23e for display 0
Could not open display

any suggestion?

[russell-taylor]

If the DK2 is working and a different "compatible" one is not, I'm guessing that it is not as compatible as it claims to be. At that point in the code, the nVidia driver has recognized that it has a DirectMode-compatible display from the vendor and it is attempting to acquire the display. Not sure how to debug this, because it is basically down inside an nVidia driver call that this is failing. There must be some subtle incompatibility with the device. Does this device work with the Oculus demos in DirectMode? If so, there may be hope that something can be done.