Why doesn't my Kinect for Xbox 360 work?


#62

We’re not sure how well the Xbox 360 Kinects work on Windows 10. We haven’t yet tried them outside Windows 7 / Windows 8.1, so it’s possible something is broken there. On OS X, the problem is most likely with El Capitan and the version of libusb we are linking against. Have you tried this version on Mac?

Other than that, if you have other sensors available (Xtions, PrimeSense, Kinect for Windows v2, RealSense) you could try those.


#63

Hi Folks, My 1414 is working ok with OSX Yosemite, but recently, the range has decreased a lot - I used to be able to work in an area about 6m deep, now i only get anything from 2m - 3m. i’m using Live View and syphoning it out to Isadora. I’ve reset NI Mate and have Activation Area turned off, but can’t get back to a useful range - any ideas what might have happened?
John


#64

Was the range larger earlier with the same version of NI mate (2.12?) or did this change happen after an update? Have the condtions in your work area changed (lights, window curtains, that kind of things)?

To be honest, this sounds like a hardware problem to me, but we should make sure it’s not something simple first.


#65

sorry Jesse - I wasn’t clear - i’m using NIMate v1, so nothing’s been updated for a long time. I can’t get v2.12 to recognise my 1414 on my Mac running El Capitan (USB3 port issues)
I can’t get 2.12 to work on my Yosemite machine - it crashes on startup. so i’m stuck with v1 on an old machine - which was ok until i started losing range.
its definitely not an environmental issue, i use the kit in workshops so i’m taking it to different studios


#66

Have you tried this on other computers? I don’t see how the range could change if there hasn’t been any kind of update for your software. Usually the problems related to OS X USB drivers and that kind of things either result in the sensor utterly crashing or working just fine, not in the camera range changing.

Do you have any other sensors you can test?


#67

Hi i’ve a xbox 360 kinect (1414),win10,i7,gtx850m,8gbram,i’ve also installed kinect sdk1.8,while my kinect is blinking a green light in device manger i see system trying to install drivers in a loop,says driver error in settings->devices->conected devices.Do you know something about it?


#68

Have you tried installing the unsigned driver with driver signature enforcement disabled? See this reply: Why doesn't my Kinect for Xbox 360 work?


#69

I tried the driver signature enforcement but the problem remains


#70

We’ve seen this problem occasionally ourselves when the Kinect was plugged in a USB3 port. Generally, you should always use USB2 ports, for which the USB port is not colored blue and doesn’t have the SuperSpeed (ss) logo above the port. Sometimes this type of problems fixed themselves when we simply used a different USB port, even if moving from USB2 to USB2.


#72

Hi,
I’m having problems getting NI Mate to recognise my kinect.

Here’s some more info:

  • Windows 7 SP 1 (x64)
  • Kinect model 1517 (Kinect for Windows 1)
  • Intel NUC (USB 3.0 ports only)

I’ve previously gotten my kinect to work with the Kinect for Windows SDK 1.8 without issue, however to get NI Mate working I’ve opted to uninstall all the official drivers and the SDK. So from the perspective of the kinect I’m starting fresh.
During installation of NI Mate I installed OpenNI 1 and 2 drivers. (OpenNI appears to be the drivers installed on the Kinect model 1517)

Opening NI Mate shows no devices connected, rescan doesn’t change that.

The NI Mate log only reads:

10:57:24: Qt WebEngine ICU data not found at D:/Qt57/5.7/msvc2013_64/resources. Trying parent directory…
10:57:24: Qt WebEngine ICU data not found at D:/Qt57/5.7/msvc2013_64. Trying application directory…
10:57:24: Installed Qt WebEngine locales directory not found at location D:/Qt57/5.7/msvc2013_64/translations\qtwebengine_locales. Trying application directory…
10:57:24: Qt WebEngine resources not found at D:/Qt57/5.7/msvc2013_64/resources. Trying parent directory…
10:57:24: Qt WebEngine resources not found at D:/Qt57/5.7/msvc2013_64. Trying application directory…

When I run the Delicode_Sensor_OpenNI.exe sensor_test in cmd.exe I get the following

Creating QApplication
Sensor test started for 200 frames:

Using websocket for data
Feed transmission is disabled
OpenNI sensor
progress: initializing device context
progress: USB enumeration
progress: USB open
Error with USB open: USB device not found!.
progress: enumerating connected devices
Starting live sensor: PrimeSense SensorKinect
progress: creating sensor device
progress: accessing depth stream
progress: setting depth format
progress: setting depth mirror
progress: accessing RGB stream
progress: setting RGB format
progress: setting RGB mirror
progress: creating user generator
progress: starting live streams
Sensor started
progress: updating all sensor data
1: progress: updating all sensor data
2: progress: updating all sensor data
3: progress: updating all sensor data
4: progress: updating all sensor data
5: progress: updating all sensor data
6: progress: updating all sensor data
7: progress: updating all sensor data
8: progress: updating all sensor data
9: progress: updating all sensor data
10: progress: updating all sensor data
11: progress: updating all sensor data
12: progress: updating all sensor data
13: progress: updating all sensor data
14: progress: updating all sensor data
15: progress: updating all sensor data
16: progress: updating all sensor data
17: progress: updating all sensor data
18: progress: updating all sensor data
19: progress: updating all sensor data
20: progress: updating all sensor data
21: progress: updating all sensor data
22: progress: updating all sensor data
23: progress: updating all sensor data
24: progress: updating all sensor data
25: progress: updating all sensor data
26: progress: updating all sensor data
27: progress: updating all sensor data
28: progress: updating all sensor data
29: progress: updating all sensor data
30: progress: updating all sensor data
31: progress: updating all sensor data
32: progress: updating all sensor data
33: progress: updating all sensor data
34: progress: updating all sensor data
35: progress: updating all sensor data
36: progress: updating all sensor data
37: progress: updating all sensor data
38: progress: updating all sensor data
39: progress: updating all sensor data
40: progress: updating all sensor data
41: progress: updating all sensor data
42: progress: updating all sensor data
43: progress: updating all sensor data
44: progress: updating all sensor data
45: progress: updating all sensor data
46: progress: updating all sensor data
47: progress: updating all sensor data
48: progress: updating all sensor data
49: progress: updating all sensor data
50: progress: updating all sensor data
51: progress: updating all sensor data
52: progress: updating all sensor data
53: progress: updating all sensor data
54: progress: updating all sensor data
55: progress: updating all sensor data
56: progress: updating all sensor data
57: progress: updating all sensor data
58: progress: updating all sensor data
59: progress: updating all sensor data
60: progress: updating all sensor data
61: progress: updating all sensor data
62: progress: updating all sensor data
63: progress: updating all sensor data
64: progress: updating all sensor data
65: progress: updating all sensor data
66: progress: updating all sensor data
67: progress: updating all sensor data
68: progress: updating all sensor data
69: progress: updating all sensor data
70: progress: updating all sensor data


#73

We got a report about this a while back. The Kinect for Windows v1 is an OpenNI2 device, but we apparently haven’t bundled the required driver for it. Please download this and place it in /Delicode_Sensor_OpenNI2/OpenNI2/Drivers. Then see if the sensor works in NI mate.


#74

It didn’t seem to work unfortunately. I tried uninstalling everything again, then installing only the OpenNI 2 during the NI Mate install. I put the kinect.dll file into the drivers folder then after that I plugged in my Kinect. The drivers didn’t install automatically, and after directing the kinect to the driver folder it couldn’t find any drivers to install. Earlier I had tried installing OpenNI 1 only during the installation and that automatically installed. Interestingly, I saw mention of there being a ‘Kinect Motor’ under the Primesense heading if the drivers installed correctly but only Kinect for Windows Camera and Audio appear. That may be just for Kinect 360 versions though.


#75

I resolved the issue. According to another forum OpenNI 2 only works with Kinect for WIndows v1 (model 1517) if the official Kinect for Windows SDK 1.8 drivers are installed (I didn’t really understand this as my understanding was that OpenNI 2 had it’s own drivers that conflicted with the Windows for Kinect SDK 1.8 drivers). Here’s the link.

So there is no requirement to switch to any other drivers. This is what I was doing before but the file you sent seems to have resolved the issue (I guess OpenNI 2 doesn’t need the drivers installed on the Kinect to function, or something like that). Thank you!


#76

Excellent, good to know. We’ll have to adjust our installer a bit for that.