I have a sample codebase which worked perfectly fine on DK1 & SDK 0.2 combination. However, same piece of code is not working with DK2. Old sample fails to create the device itself. Just to cross verify I wrote a sample code for device initialization using both SDK 0.2 & latest SDK 0.4.3. Surprisingly, Dk2 gets detected just fine on code using latest SDK but DK2 fails to create the device itself for SDK 0.2. Is this natural? I do know that lot has changed over from sdk 0.2 to 0.4, but just wondering if there is any known solution to this or porting the old code using new SDK is the only way out?
ovrHmd_Create(0) returns proper device handle in latest SDK, but CreateDevice() does not return valid handle & fails.
Yeah I don't know how we could expect this to work - 0.2 was released a long time ago. I'm too lazy to check, but I think it was before DK2 even was announced, so it certainly does not recognize it. 0.3 doesn't even recognize DK2 unless you add the USB id manually.
The solutions are either: - heavily, heavily modify 0.2 SDK yourself to recognize and talk to DK2 (A TON OF WORK) - upgrade to 0.4 SDK (a days work +/- depending on experience)
The first option, after all your work, you still won't even have positional tracking.
