I'm sure this has being post before, but this is my particular case.
I'm planning to start a game development project in the last week of March.
The final use of the Oculus Rift will be done by the end of June, so I will start integrating it at the end of May.
We don't know when will the Crescent Bay will be release, but I'm planning buying the DK2 right now, should I wait? This is because I have the thought that maybe you should first understand the hardware and even the software before taking the next step (Crescent Bay). I am a programmer, so I see this like a "learn first C before C++" case.
Crescent Bay will never be released. It's a internal dev kit only for Oculus. The consumer release might come out in December. Stop being so cheap and buy a dk2.
i7 skylake, EVGA Classified, 2 EVGA 980 sc's, Thermaltake TR2 RX(1000W), 32GB DDR4, Win 10 on an SSD
I didn't write this in the initial post, but money is not an issue, I could by both if necessary.
Considering that this prototype has been described as a huge step from DK1 and 2, but at the same time is not the CV, I thought this might be a new version that we can have to continue working on our developments.
I will be digging more into this and I will wait for a little more.
I didn't write this in the initial post, but money is not an issue, I could by both if necessary.
Considering that this prototype has been described as a huge step from DK1 and 2, but at the same time is not the CV, I thought this might be a new version that we can have to continue working on our developments.
I will be digging more into this and I will wait for a little more.
Some official announcements already said that there will be NOT any DK3 or Crescent bay available. If you want to develop something i think you should buy the DK2.
Can't believe I'm actually recommending this! First time for everything I guess.
You should probably purchase the DK2 as the CV1 won't be released by the time you're ready for developing for the platform. On a sidenote, there have been a few decent / more than decent demoes created by people that didn't even have a Rift. As long as everything is "to scale", and you're using the Best Practices for VR, with some common (or not so common) sense in UI development, then you could develop for the platform without purchasing..
Current WIPs using Unreal Engine 4:Agrona - Tales of an Era: Medieval Fantasy MORPG
"saviornt" wrote: You could develop for the platform without purchasing..
I thought about this too. The use of the OR is actually an extension of your actual application. For some developers (including) will need to use it only at the end of the development process.
In that case, what do you think about the SDK? For what I see, there is not a "simulator" that can help you create the connections before actually buying/using it. This will Very useful. Or is there a way to understand the usage of the software and the OR before using it? Again, like a simulator? (third party perhaps?)
Crescent bay wont be released ..that because the final version will be very the same or better, so is no point make a dk3 when consumer version will be more or less the same.
CV1 will come from summer to winter 2015, just buy a DK2 like i did ,I ordered mine 1 week ago and I will have time to test it in the next months.
PS: The final version wont be light years better than Crescent Bay as some may think, but of course it may be better.
I saw somewhere that there will be like an 'upgraded' version of the DK2 from its first release, how about this?
According to Oculus, there will be no DK3. There will be made available an input dev kit and an audio dev kit released for the DK2, but no new versions of the HMD itself.
Not a Rift fanboi. Not a Vive fanboi. I'm a VR fanboi. Get it straight.
