I didn't know there was any confusion about the sdk being made available to peasant developers, if oculus are moving towards locking down the system to their store then i would be well out. Is it staying free for all to use and do as they like with?
"smilertoo" wrote: I didn't know there was any confusion about the sdk being made available to peasant developers, if oculus are moving towards locking down the system to their store then i would be well out. Is it staying free for all to use and do as they like with?
I also wish Oculus would answer this question. Am I going to be able to try demos/experiences people make freely available or am I going to be locked down to what is "approved by Oculus" in the Home storefront?
SDK is staying free for everyone, but the SDK 1.0 apparently won't work without a final Rift, so they aren't letting people download it unless they have a prototype Rift (Oculus is sending Rifts to people who are releasing quality titles in 2016).
And yes, they've said you'll be able to play games gotten elsewhere than Oculus Home. Otherwise there wouldn't be a way to play Elite Dangerous, since that game's minimum requirements are higher than what Oculus put out.
The only "lock" oculus is making is that if you want (as devloper) your game on oculus store you have to build it with the oculus SDK. You can make it compatible with other systems or release it for free if you want no problem, no locking, but if is on the oculus store, it have to be "oculus ready" Thats all 🙂 Or at the least is what i've understood from the last Q&A 🙂
"Dreamwriter" wrote: SDK is staying free for everyone, but the SDK 1.0 apparently won't work without a final Rift, so they aren't letting people download it unless they have a prototype Rift (Oculus is sending Rifts to people who are releasing quality titles in 2016).
And yes, they've said you'll be able to play games gotten elsewhere than Oculus Home. Otherwise there wouldn't be a way to play Elite Dangerous, since that game's minimum requirements are higher than what Oculus put out.
Wait... SDK 1.0 won't work with the DK2? That would mean the DK2 is useless after CV1 comes out?
Oculus software architect Tom Forsyth confirmed the completed 1.0 Rift Software Development Kit should be compatible with the second development kit (DK2) that started shipping in mid-2014. This means the pioneering but aging developer headset could still run some VR experiences well into the launch of consumer hardware.
It's not very reassuring that the only thing we have to go on is this single tweet "Nope, 1.0 supports DK2." by a random Oculus programmer "Tom Forsyth".
There are a lot of serious developers here and we could really do with some clarity.
Oculus are not allowing us to use the latest SDK although we bought a developer kit. No proper reason has been given for this. Despite being asked, they have given no rough estimate of when the SDK will become available, or even confirmation that it will be released to us before the CV1 is shipped.
