-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Openni2 does not handle oni files #69
Comments
Comment by mikeferguson I'm guessing it is due to this commit: 17c1072 -- in the past it would have probably fallen through and returned the string name, now it returns the empty string -- you could try adding an extra case before the matching attempt which checks if the file ends with .oni and if so, returns the device_id as-is. If that works, we can gladly accept a PR to fix this regression. |
Comment by rastaxe It worked! Thanks.
|
Comment by lianera Same issue here, does anyone has a fixed fork? |
Comment by rastaxe If you add the above two lines to line 682, it fixes the problem. |
Issue by rastaxe
Tuesday Feb 23, 2016 at 08:37 GMT
Originally opened as ros-drivers/openni2_launch#26
I am not able to load a oni file (OpenNI record file) with openni2 in Indigo. In Hydro I was able to load it simply with: roslaunch openni2_launch openni2.launch device_id:=/path/to/your/file.oni
but in Indigo openni2 still tries to open the real device. Do you have the same problem?
The text was updated successfully, but these errors were encountered: