search

sensics / OSVR-RenderManager

Apache License 2.0
64 stars 45 forks source link

Direct Mode w/ DK1 results in [NVAPI_RESOURCE_NOT_ACQUIRED] after 12 seconds of rendering #367

Closed kaisparkle closed 6 years ago

kaisparkle commented 6 years ago

Hi, I'm currently trying to get Direct Mode working with the Rift DK1 and OSVR-OpenHMD, as Extended has always felt off to me and made me feel dizzy. The D3D sample renders properly, with some strange jitter and a ~50fps framerate, but only for ~12 seconds before I receieve this error:

Apr 04 22:34:45.499 error [RenderManager]: OSVR RenderManager Warning: Got error from NVIDIA API: NVAPI call returned -203 (hex: ffffff35)
Apr 04 22:34:45.500 error [RenderManager]:  [NVAPI_RESOURCE_NOT_ACQUIRED]
Apr 04 22:34:45.500 error [RenderManager]: RenderManagerNVidiaD3D11::PresentFrameFinalize: Could not present surface 0 to display 0
Apr 04 22:34:45.501 error [RenderManager]: RenderManager::PresentRenderBuffers(): PresentFrameFinalize failed.

My RenderManager config is here. With the SteamVR plugin, SteamVR exhibits the same behaviour - renders perfectly fine, but drops after around 12 seconds. I'm using a GTX 1050 Ti.

kaisparkle commented 6 years ago

Weird, after rebooting and leaving my PC on all day it works...?
Odd.

russell-taylor commented 6 years ago

Worrisome. I was going to ask whether you were using the VRPN driver to read the position, because at least the DK2 will go into power-down on the display if it is not being driven from the USB port.

If the SteamVR plug-in you are talking about is the non-OSVR one, then I suspect the hardware.

kaisparkle commented 6 years ago

Yeah, seems to be with my system config. After consecutive power cycles of the Rift box, it'll exhibit the same behaviour. Letting a sample crash then power cycling seems to fix it.