![\"Oculus](\"http:\/\/blogs.discovery.wisc.edu\/projects\/files\/2014\/09\/minimal-with-HSW.png\")
<\/a>HSW shown atop sample code from the Oculus forums.<\/p><\/div>\n
… which introduces something like a 4 second delay to the start of any application. \u00a0Which is a problem for a developer, who might run their app dozens or hundreds of\u00a0times in a few hours.\u00a0This is only an issue when using libOVR’s internal rendering engine (though I assume Oculus frowns on distributing software without something similar).<\/p>\n
It looks like at there’s some intention to allow it to be disabled at runtime, via:<\/p>\n
ovrHmd_EnableHSWDisplaySDKRender( hmd, false );<\/pre>\nA good candidate to be\u00a0triggered with a _DEBUG preprocessor define or something . . . but this isn’t currently exposed.<\/p>\n
The next easiest way seems to be toggling an a #define at line 64 of \/CAPI\/CAPI_HSWDisplay.cpp:<\/p>\n
#if !defined(HSWDISPLAY_DEFAULT_ENABLED)\r\n\u00a0 \u00a0 \u00a0#define HSWDISPLAY_DEFAULT_ENABLED 0 \/\/ this used to be a 1\r\n#endif<\/pre>\n… then recompiling LibOVR. \u00a0Which isn’t so bad —\u00a0VS project files are\u00a0provided, and\u00a0worked with only minor tinkering (I\u00a0had to add the DirectX SDK executables directory to the “VC++ directories” section of the project properties).<\/p>\n
Recompiling the SDK works for what we’re doing,\u00a0and it’s not hard, and we might need to modify libOVR eventually anyway . . . but it’s still a little silly.<\/p>\n
Now that libOVR is building alongside some sample code, there’s some spelunking to do through the OculusWorldDemo to find how the new API suggests we\u00a0modify eye parameters. \u00a0Digging too deeply into the new C API, it looked like there may be other new (C++?) classes inside . . . and that’s probably deeper than we’re meant to access. \u00a0Some shallower functions skimmed from\u00a0OculusWorldDemo are currently being investigated.<\/p>\n
(Note that this was actually tested with 0.4.1; I’ve to install the directX SDK on this other machine before testing against 0.4.2. \u00a0I’ll probably remove this note\u00a0once that’s done.)<\/p>\n","protected":false},"excerpt":{"rendered":"
Oculus Rift DK2 and\u00a0SDK 0.4.2 bring some exciting improvements,\u00a0and some small problems. The SDK has switched to a new C API, which probably means restructuring our existing Rift code. It also\u00a0shows this at the start of every app: … which … Continue reading