The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
After exploring Stephane.M's suggestion of reinstallation, it turns out the fault was an unintentional curiosity that killed everything.
The culprit: http://www.openni.org/wp-content/uploads/2012/12/Sensor-Bin-Linux-x64-v5.1.2.1.tar.zip
The cure: https://github.com/avin2/SensorKinect/zipball/unstable
Despite being the exact same version, it appears the current SensorKinect build on the github works fine, while the one on the OpenNI website broke any application attempting to use my Kinect.
I hope this is a solution to anyone out there that curiously tried to install the OpenNI driver only to find it breaks something. :)
| | 2 | formatting links |
After exploring Stephane.M's suggestion of reinstallation, it turns out the fault was an unintentional curiosity that killed everything.
The culprit:
http://www.openni.org/wp-content/uploads/2012/12/Sensor-Bin-Linux-x64-v5.1.2.1.tar.zipOpenNI-compliant SensorKinect Linux-x64 driver on the OpenNI website
The cure:
https://github.com/avin2/SensorKinect/zipball/unstableGitHub snapshot of SensorKinect drivers
Despite being the exact same version, it appears the current SensorKinect build on the github works fine, while the one on the OpenNI website broke any application attempting to use my Kinect.
I hope this is a solution to anyone out there that curiously tried to install the OpenNI driver only to find it breaks something. :)
After exploring Stephane.M's suggestion of reinstallation, it turns out the fault was an unintentional curiosity that killed everything.
The culprit: OpenNI-compliant SensorKinect Linux-x64 driver on the OpenNI website
The cure: GitHub snapshot of SensorKinect drivers - look in Bin folder and use the package relevant to your OS to install the driver.
Despite being the exact same version, it appears the current SensorKinect build on the github works fine, while the one on the OpenNI website broke any application attempting to use my Kinect.
I hope this is a solution to anyone out there that curiously tried to install the OpenNI driver only to find it breaks something. :)
| | 4 | No.4 Revision |
After exploring Stephane.M's suggestion of reinstallation, it turns out the fault was an unintentional curiosity that killed everything.
The culprit: OpenNI-compliant SensorKinect Linux-x64 driver on the OpenNI website
The cure: GitHub snapshot of SensorKinect drivers - look in Bin folder and use the package relevant to your OS to install the driver.
Despite being the exact same version, it appears the current SensorKinect build on the github works fine, while the one on the OpenNI website broke any application attempting to use my Kinect.
I hope this is a solution to anyone out there that curiously tried to install the OpenNI driver only to find it breaks something. :)
| | 5 | No.5 Revision |
After exploring Stephane.M's suggestion of reinstallation, it turns out the fault was an unintentional curiosity that killed everything.
The culprit: OpenNI-compliant SensorKinect Linux-x64 driver on the OpenNI website
The cure: GitHub snapshot of SensorKinect drivers - look in Bin folder and use the package relevant to your OS to install the driver.
Despite being the exact same version, it appears the current SensorKinect build on the github works fine, while the one on the OpenNI website broke any application attempting to use my Kinect.the Kinect. If problems persist running the install script, do a sudo ./install.sh -u first before installing.
I hope this is a solution to anyone out there that curiously tried to install the OpenNI driver only to find it breaks something. :)
| | 6 | No.6 Revision |
After exploring Stephane.M's suggestion of reinstallation, it turns out the fault was an unintentional curiosity that killed everything.
The culprit: OpenNI-compliant SensorKinect Linux-x64 driver on the OpenNI website
The cure: GitHub snapshot of SensorKinect drivers - look in Bin folder and use the package relevant to your OS to install the driver.
Despite being the exact same version, having a very similar version number, it appears the current SensorKinect build on the github works fine, while the one on the OpenNI website broke any application attempting to use the Kinect. If problems persist running the install script, do a sudo ./install.sh -u first before installing.
I hope this is a solution to anyone out there that curiously tried to install the OpenNI driver only to find it breaks something. :)
| | 7 | No.7 Revision |
After exploring Stephane.M's suggestion of reinstallation, it turns out the fault was an unintentional curiosity that killed everything.
The culprit: OpenNI-compliant SensorKinect Linux-x64 driver on the OpenNI website
The cure: Avin2 GitHub snapshot of SensorKinect drivers - look in Bin folder and use the package relevant to your OS to install the driver.
Despite having a very similar version number, it appears the current SensorKinect build on the github works fine, while the one on the OpenNI website broke any application attempting to use the Kinect. If problems persist running the install script, do a sudo ./install.sh -u first before installing.
I hope this is a solution to anyone out there that curiously tried to install the OpenNI driver only to find it breaks something. :)
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
