Forum Discussion
Future SDK Speculations?
Hi guys, We all know that the first DK2 batch is hold one week for waiting new SDK release. So, I was asking myself what the new SDK may add in term of functionality (not bug fixes and stuff) ...
I think the delay is being caused by something already hinted at in the current 0.3.2 SDK:
(From OVR_CAPI.h, line 132)
Cybereality has referenced it a bit before too. I don't know 100% what it is, but it seems to be some custom solution to bypass the OS and make the Rift more than a dumb monitor. This is very exciting because it should mean a much more user-friendly experience. I started to add some stuff to my game to make monitor configuration and mirroring (in the game, rather than the OS) more user-friendly - but it is looking like Oculus is developing a more engine-agnostic solution instead. Hopefully this driver (if they meant "driver" in the traditional sense) is going to be open source with the rest of LibOVR.
// These flags are intended for use with the new driver display mode.
/*
ovrHmdCap_ExtendDesktop = 0x0004, // Read only, means display driver is in compatibility mode.
ovrHmdCap_DisplayOff = 0x0040, // Turns off Oculus HMD screen and output.
ovrHmdCap_NoMirrorToWindow = 0x2000, // Disables mirrowing of HMD output to the window;
// may improve rendering performance slightly.
*/
(From OVR_CAPI.h, line 132)
Cybereality has referenced it a bit before too. I don't know 100% what it is, but it seems to be some custom solution to bypass the OS and make the Rift more than a dumb monitor. This is very exciting because it should mean a much more user-friendly experience. I started to add some stuff to my game to make monitor configuration and mirroring (in the game, rather than the OS) more user-friendly - but it is looking like Oculus is developing a more engine-agnostic solution instead. Hopefully this driver (if they meant "driver" in the traditional sense) is going to be open source with the rest of LibOVR.