Is there any information Oculus can give as to the status of the updated SDK? Or maybe something I missed recently? I can't recall reading anything on this in quite some time and it is such a vital part of the developer's kit.
"treebolt" wrote: I assume if you tried to compile anything with it now, you wouldn't have any hardware that's compatible to test it with anyway.
It's possible to use the sdk without having a rift (I developed, released and tested my first rift demo without having one myself, got other people with rifts to test it), however there's not much to do with a DK2 if you don't have the sdk too.
So I'd say the sdk is the important bit, no point getting a dk2 until the matching sdk is public.
I had a hunch this delay had to do with the SDK and not the hardware since things have been so quiet about the SDK and there are always improvements that can be made all the time for software so they probably want to polish it as much as possible. So dare I say, I nailed it! Thanks for the updated info though for sure! We all really appreciate the openness of Oculus. 😄
Hoping to get an update on the SDK since we're shipping now. I was hoping to at least download the new SDK and start toying around with it in Unity before my DK2 comes next month. Thanks much 😃
