Closed russell-taylor closed 8 years ago
When using RestartD3D example and letting it restart a number of times using an on-screen display, it eventually (different counts) gives an error inside GetRenderInfo() that seems impossible. Maybe stack trashing? Maybe related to the start-up issue with the server that happens on the Microsoft Surface?
The start-up issue on the Surface had to do with logging failing and throwing an exception, so that was not related.
Jeremy reports that this only happens with Asynchronous Time Warp enabled.
The code has since been changed to ask the underlying DirectMode RenderManager for the render info, rather than the wrapped one. This should avoid the race condition we were seeing.
Jeremy reports: I'm occasionally getting osvrRenderManagerGetNumRenderInfo return 0 render infos with this config. Not all the time. osvr_server_config.zip