0

Im currently trying to get a new Kinect for Windows to run on OSX 10.7 with AirKinect 2. So far i had no luck.

Here is what i did until now :

Then i wanted to verify if the device works. I used this app http://www.thingiverse.com/thing:18425 but it does not recognize the device.

In FDT 5.5, i have a sample project which uses the AirKinect Native Extension/ane.

All it does is to check for Kinect.isSupported() but i constantly get the following error:

Error #3500: The extension context does not have a method with the name applicationStartup.

Currently im stuck here. Are there any drivers missing? Anybody got AirKinect + Kinect for Windows on OSX 10.7 to work?

chris

chris
  • 171
  • 3
  • 10

1 Answers1

0

First, confirm that OpenNI works correctly. It should come with some very basic non-AIR samples. If the samples don't work, there is probably something wrong with the driver.

As far as I can gather from the information on GitHub, avin2's branches of SensorKinect don't have support for the Kinect for Windows sensor yet. There is a pending pull request which apparently adds the missing features. You can find a Kinect for Windows-enabled binary here.

By now, the OpenNI samples should work. Try your AIRKinect Test again. If it fails, consider using an ANE from the AIRKinect development repository - the builds there are updated more frequently than in the main branch.

But keep in mind: Neither have I tried this approach, nor do I have the facilities to do so. I'm just naming some common problem sources and their solution.

Chris Ortner
  • 806
  • 6
  • 11
  • it seems that the driver does not work yet. i got Device: PrimeSense/SensorKinect/5.1.0.25: The device is not connected! Device: PrimeSense/SensorV2/5.1.0.25: The device is not connected! Device: PrimeSense/SensorKinect/5.1.0.25: The device is not connected! Device: PrimeSense/SensorV2/5.1.0.25: The device is not connected! – chris Jul 16 '12 at 14:55
  • It's also a common problem that there is not enough USB bandwidth available to the device. Make sure that the Kinect is the only device connected to the USB controller. To be extra sure, disconnect all other USB devices from your computer, if possible, since it's often not obvious, which ports belong to the same controller. – Chris Ortner Jul 16 '12 at 16:46
  • it seems that the SensorKinect driver is the problem. i tried the binary but it didn't work. so either i have to write my own driver or stick with windows for the time being. – chris Jul 17 '12 at 08:24