DK2 Development kit

I've warned dalematthews. That was some opening post.

For a second, I thought Cleverusername was back.

Mike

I like the way oculus team see us argue on a potentiel devkit v2, they have the answer, are in the middle of us but they just prefer look at us figthing, with popcorns.

"spire8989" wrote:
Why would you come to a developer forum, get legit responses from developers to a very well known question and then be whiny about it? Geekmaster told you the truth, we all know there is no 1080p kit. Common knowledge here.

"There is no B3 Bomber" -Wag The Dog

I still think they are making or are considering making a DK2, and here is my reasoning.

1. If they were sure they weren't going to make another DevKit, they would publicly announce it so people on the fence would buy DK1. I'm sure there are a lot of people holding out for DK2. Not knowing if there's going to be another rev creates unnecessary confusion if they're sure they're not going to make one.

2. If they are planning another DevKit, they wouldn't announce it until it's ready or it would cannibalize DK1 sales. So you would just go the "no comment" route. This is common practice with technology.

Now I do think it's possible that they're considering it now, but will run the numbers at some point and find it doesn't work. At this point, I would expect them to announce there is going to be no DK2.

I haven't seen any quotes where it's been confirmed or denied? All I've seen is Palmer, on reddit, saying that there would not be an upgrade for DK1, because all new parts would be needed. Have I missed something?

Road to VR speculate on DK2.

http://www.roadtovr.com/2013/08/20/oculus-rift-hd-dev-kit-dk2-7575

"tappa" wrote:
Road to VR speculate on DK2.

http://www.roadtovr.com/2013/08/20/oculus-rift-hd-dev-kit-dk2-7575

Thank you, this quote should make things (unfortunately) very clear:

Update: At Gamescom 2013, Road to VR’s Paul James spoke with Oculus VR Inc Founder, Palmer Luckey and VP of Product Nate Mitchell, who confirmed that there would be no Oculus Rift HD dev kit before the consumer version ships sometime in 2014.

Sounds a little bit strange to me, because developers will not be able to adapt their content to the consumer version (and it's presumed positional tracking) in time then.

Maybe the consumer version is in fact the DK2 as well and devs will get access to it a few weeks before the official consumer launch.

spyro

"Tgaud" wrote:
I like the way oculus team see us argue on a potentiel devkit v2, they have the answer, are in the middle of us but they just prefer look at us figthing, with popcorns.

Do you really think these people have time to sit around and watch you have a flame war over some non-existant thing?

These kinds of stupid arguments are supposed to come with a retail version when they have a team dedicated to dealing with PR and stuff. If you were actually a developer, you wouldn't give 2 shits if the thing is 1080p or not, the head tracking is the most important feature to be able to test for development, and you know anything you do on the 720p version will only look better when the, probably 1080p, retail version does come out.

if you're a real developper, you would care about resolution.
or you're just a shit of developper like we see this time, not caring about the optimization and performance of his code.
We have computer 100 time better than ten years ago, and the game are getting more and more laggy.
Cuz they just dont care about optimization.

I want to test, to be aware of what need to be improved, optimized, i dont want to spent processor time in useless calculation of effects, if thoses effect won't be visible in the rift because of bad resolution.

You're doing "fast food" of game developpment, stop judging me.

But yeah, i'm also agreed on the positional tracking, that is important too.

You care that much about the resolution that its worth getting into a flame war over? Odd...

...if that's the case though then when you create the render target that you're drawing your scene too, y'know the one you distort for the Rift, create it with 1920x1080 resolution instead of 1280x800. Tada, now you're rendering to the HD versions resolution and can assess it's performance.

That's why the Developer Kit doesn't need to be updated to HD, because it's irrelevant to "real" developers.
The devices resolution does not equal the resolution you are forced to render your game/program/title/video/etc at.

I think you're worrying about nothing, certainly nothing relevant to things you listed as wanting to test and optimise etc.