Hacker News new | comments | show | ask | jobs | submit login

Keep in mind that there's no report of the processing power required to do this in the video. It very well could be an algorithm that is extremely accurate, but at the expense of many CPU cycles. While it's obvious, remember that for use in games, you have to perform the detection and run the game in realtime. Whether or not this can be done with current hardware is what I'm interested in.

On the website he claims it's a fairly standard dual core setup and you can see the number of frames per second in the video. I noticed at one point it was staying around 15fps. It may not work at this point for an FPS (Especially because it would have to be done in conjunction with graphics and other game-related processes), but it would likely be fine with other less fast-paced games.

At least some of the processing could also be off-loaded to an accessory device. How much work is the Kinect doing vs. the actual 360?

Yesterday I bodged together something that's maybe half as good by gluing various OpenCV components together with numpy, and that runs at 15fps on an Atom netbook. I get the impression that this is just a lot more clever with the algorithms it uses, rather than specifically relying on the CPU grunt.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact