Will putting kinect in every box really change anything?

[Adinnieken]

ChrolloLucilfer said:

Adinnieken said:

Once that code is generated, they need only implement it in a future game.

For instance.  If Microsoft paid for the Kinect features in Skyrim, so what?  If the features Bethesda implemented, such as voice commands, proved popular, then they need only implement the code in their next game.  Bethesda owns the code.  There's no cost to reusing code.  Sure, you might tighten and clean the code, but overall, as long as the code was 100% functional as it was originall implemented, then it's going to work.

I highly doubt there is a significant difference between the API for Kinect and Kinect 2, since you're quite literally just waiting for Kinect to tell you whether or not it received a desired/specified command, or in the case of gesturing, the x, y coordinates of the cursor.  It isn't much different from coding for a mic or game controller. 

Even with an existing made code it will take time to implement and test said feature for every game it used on. With the tightness of budgets and especially in the terms of getting games out on time. I don't see much demand on the part of Third party to bother with said features which have already been given a some what lukewarm demand from the majority dedicated gamer.

The time it takes to implement is equivalent to copying pasting code, because that's exactly what you're doing.  If you're smart, you've put all your code for such purposes in a library and the only thing you do is make a reference to that library in your code.  Since you've already used that library, you know it works, and if you're using a good IDE, it'll tell you if your code is broken before you compile it.  So, geez oh mighty, it isn't that big of a deal! 

Yes, you will need to test it, but it isn't as if you should expect broken code.  Fact is if you've done everything correctly it will work exactly as you expect it to.

Have you ever coded?  Have you not re-used code?  Is coding a such a challenge for you that once you get something to work properly, you're unable to get it to work properly again?  I'm confused as to how or why you see this as such a big challenge, because it isn't.  Smart coders code once, and reuse many.  What do you think a game engine is?  A series of code people copy and paste into a single document?  No!  It's a series of library files that you reference in your code and make calls to those library files.