theprof00 said:
they actually do operate the same way. rolls eyes. No....not what kind of camera it uses. smacks forehead* The cameras both interpret movements into "inputs". They don't go into such great depths as z-axis's and you distance. It's just, for example, 'thumb' or 'right leg'. Those are your "buttons". Then moving the right leg up, "pushes the button". Programming one and working on the other is like programming to use an xbox controller and then porting it to a pstation controller. |
Actually they do not work the same. MS has the infrared sensor so that no matter what lighting conditions you have kinect 2.0 can always see you. Sony just have two cameras and it will be very dependent on light just like the Eye. I have the current Eye and trying to do anything with motion that does not require the move controller and nub is mostly useless in my home.
Because Sony also does not have a true depth sensor, it will be harder or even just plain crappy to perform anything that require true motion of the limbs. It will be worse than Kinect 1 and frustration for developers trying to make it work the same as Kinect 2.0. The only solution is if you can map the move controller and nub but then again it would not be the same as complete body motion and tracking.
There are a lot of challenges to getting the new eye to operate on the same level as the Kinect 2.0 and as I stated before, if a developer isn't getting paid for it or cannot know what the install base is, going through the effort will probably not happen. Also MS has a complete API for their device including Voice recognition which up to this point I have not heard Sony have.
I am not saying that we will not see support for both, its just that it will be easier to support the device that comes with every console then to add extra development which may seem small to your might not be that small when actually doing the work.








