Oculus Announces Release Date For SDK 0.7; Developers Be Warned

  • Thread starter Thread starter Guest
  • Start date Start date
Status
Not open for further replies.
So Oculus just basically burned their developers again. First by delaying forever the release, which in itself can be costly. But now, the vaporware just killed any effort that has been made. Not delayed, but made incompatible.

Disrespecting your developers is a bad idea.
 
So Oculus just basically burned their developers again. First by delaying forever the release, which in itself can be costly. But now, the vaporware just killed any effort that has been made. Not delayed, but made incompatible.

Disrespecting your developers is a bad idea.
It's not as bad as you think. This only affects a small number of devs that aren't using the latest versions for the games they will release in 2016.
If you aren't a developer yourself then i suggest keeping your ignorant comments to yourself. You have no idea what this update does and how much it affects others. In my opinion the only vaporware here is you.
Being ignorant and naive is a bad idea.
 
So Oculus just basically burned their developers again. First by delaying forever the release, which in itself can be costly. But now, the vaporware just killed any effort that has been made. Not delayed, but made incompatible.

Disrespecting your developers is a bad idea.

They haven't delayed the release of any hardware at all. Everything is still on schedule and they are the only VR firm to already have plenty of VR devices in people's hands. Hell I have a DK2 sat right next to me and it works great.

It's going to be trivial for developers to update to the newer SDK as the engines will be updated quickly due to developers of those working closely with Oculus. Unity 5 and UE4 already support 0.6 which is fully compatible in 0.7 right now and 0.7 support will be there in no time.

The only developers who will be affected are those that are stuck on Unity 4 or UDK and they've known their days are numbered for a long time so if they're worth their salt, they will already have begun transitioning to the new engines. Anyone using a custom engine is obviously going to have their work cut out but that's the nature of engine design and cutting edge technology.
 
So Oculus just basically burned their developers again. First by delaying forever the release, which in itself can be costly. But now, the vaporware just killed any effort that has been made. Not delayed, but made incompatible.

Disrespecting your developers is a bad idea.

Oculus was very clear that DK1 and DK2 were pre-release hardware and that the SDK is in a beta stage and will be going through changes. I have both the DK1 and DK2 and expect the transition for my small projects to require very little to adjust to the 0.7 SDK. Any and all major changes to the SDK and engine support that they can work out before the 1.0 release and retail product is smart, get it out of the way now before it will have customer and/or major developer impact post release.
 
This is good extended mode needs to disappear and direct mode needs to work better. It sucks having to switch it around when you are showing people the OCULUS.
 
Status
Not open for further replies.