-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Drake visualizer problems on Ubuntu 16.04 #3070
Comments
Closing due to inactivity, and because lots of people are using 16.04 without complaint. Please reopen if this is still a problem. |
FTR, a workaround that was known to work is to open the defective |
I am having the same problem, vtkOBJReader fails at reading .obj files, raising errors such as this:
I am running Ubuntu 16.04. I tried with different .obj files, and also did as @liangfok suggested, opening the file in MeshLab and re-saving it. Though it didn'work. Any idea on this? @david-german-tri could you reopen the issue, please? Thanks |
Odd. As a quick test, can you try the open/save-as technique using |
@liangfok thanks for replying. Sorry I am really a newbie on these things, I have opened the .obj file with view3dscene but there is no option to save it again as an .obj file. Only options available are .x3dv and .x3d. |
Oops, sorry I did not realize |
@liangfok Uh, if this is going to be a real bug report, then it needs a proper title and diagnosis? The "VTK 7" in the error message makes me wonder if Gian is not using the most recent @GianMassimiani Please explain exactly the steps needed to reproduce the problem. Or at least, the steps you are trying that are not working. |
Ok, so I am using "the Director" (https://github.com/RobotLocomotion/director) and I get the error when using this module http://openhumanoids.github.io/director/_modules/director/ioUtils.html and in particular its
I downloaded a few .obj files from the Internet and
For example, here are the first few lines of the
@liangfok As you suggested in the last reply, I tried to convert from .obj --> .x3dv with |
I don't know if this might be relevant, regarding the error raised by
I searched for that |
I wonder if the problem has to do with Windows vs. Unix line endings. Can you confirm that your .obj file uses Unix line endings (\n instead of \r\n)? Since this issue appears to be Director-related and not Drake-related, I'm going to close this issue. Feel free to open a new issue in Director's issue tracker. |
FTR, another source of the problem is locale settings that result in a comma being used instead of a period in floating point numbers. See RobotLocomotion/director#541. |
The drake visualizer fails to render some of the examples and throws errors seen on the terminal.
The behaviour can be seen in this recording :
https://youtu.be/N7LasHpjod4
The vtk version :
Package: libvtk5.10
State: installed
Automatically installed: yes
Version: 5.10.1+dfsg-2.1build1
The obtained output for runQuadrotorLQR is :
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/IO/vtkOBJReader.cxx, line 219
vtkOBJReader (0x3632af0): Error reading 'vn' at line 12
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/Graphics/vtkTransformPolyDataFilter.cxx, line 84
vtkTransformPolyDataFilter (0x3632af0): No input data
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/Graphics/vtkTransformPolyDataFilter.cxx, line 84
vtkTransformPolyDataFilter (0x3632af0): No input data
The obtained output for run_kuka_iiwa_arm_dynamics are
Error locating link name: world
Error locating link name: iiwa_link_0
Error locating link name: iiwa_link_1
Error locating link name: iiwa_link_2
Error locating link name: iiwa_link_3
Error locating link name: iiwa_link_4
Error locating link name: iiwa_link_5
Error locating link name: iiwa_link_6
Error locating link name: iiwa_link_7
Error locating link name: iiwa_link_ee_kuka
Error locating link name: iiwa_link_ee
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/IO/vtkOBJReader.cxx, line 192
vtkOBJReader (0x2dee240): Error reading 'v' at line 12
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/Graphics/vtkTransformPolyDataFilter.cxx, line 84
vtkTransformPolyDataFilter (0x2e2eaf0): No input data
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/IO/vtkOBJReader.cxx, line 192
vtkOBJReader (0x2e41a90): Error reading 'v' at line 12
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/Graphics/vtkTransformPolyDataFilter.cxx, line 84
vtkTransformPolyDataFilter (0x2f3cc80): No input data
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/IO/vtkOBJReader.cxx, line 192
vtkOBJReader (0x2ff2390): Error reading 'v' at line 12
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/Graphics/vtkTransformPolyDataFilter.cxx, line 84
vtkTransformPolyDataFilter (0x2f55fe0): No input data
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/IO/vtkOBJReader.cxx, line 192
vtkOBJReader (0x2fba610): Error reading 'v' at line 12
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/Graphics/vtkTransformPolyDataFilter.cxx, line 84
vtkTransformPolyDataFilter (0x307e470): No input data
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/IO/vtkOBJReader.cxx, line 192
vtkOBJReader (0x30deb70): Error reading 'v' at line 12
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/Graphics/vtkTransformPolyDataFilter.cxx, line 84
vtkTransformPolyDataFilter (0x3129490): No input data
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/IO/vtkOBJReader.cxx, line 192
vtkOBJReader (0x31d3980): Error reading 'v' at line 12
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/Graphics/vtkTransformPolyDataFilter.cxx, line 84
vtkTransformPolyDataFilter (0x30e4a20): No input data
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/IO/vtkOBJReader.cxx, line 192
vtkOBJReader (0x319b640): Error reading 'v' at line 12
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/Graphics/vtkTransformPolyDataFilter.cxx, line 84
vtkTransformPolyDataFilter (0x327b7f0): No input data
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/IO/vtkOBJReader.cxx, line 192
vtkOBJReader (0x324e990): Error reading 'v' at line 12
ERROR: In /build/vtk-NWL3SN/vtk-5.10.1+dfsg/Graphics/vtkTransformPolyDataFilter.cxx, line 84
vtkTransformPolyDataFilter (0x333deb0): No input data
The text was updated successfully, but these errors were encountered: