-
Notifications
You must be signed in to change notification settings - Fork 214
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
STL meshes can't be rendered using WSL2 ROS Galactic Rviz2 #804
Comments
@iuhilnehc-ynos This is the collision, not the visual mesh model. Sorry that I forgot to update the expected behavior. And I am quite sure that it is not the urdf problem. |
@sink0918 I'm not familiar with WSL2. After installing it (Ubuntu20, WSL2, galactic), I tried to( use Could you confirm whether it can work in your environment? If yes, I'll continue to use another robot |
The problem seems to be meshes using By the way, I'm using And I also tried realsense-description, the stl mesh can't be seen either. |
I have also reported this issue to microsoft/WSL, here is the link: microsoft/WSL#7788 |
I can confirm experiencing this issue as well. |
+1 here, tried on Win11 with iGPU and also nVidia GPU systems. |
This appears to still be an issue in rolling, rviz2 v9.1.1. Any ideas what could be the culprit? |
Did anyone find a solution to this issue? I am using ROS2 foxy on WSL2 Ubuntu 20.04, and could not see a rendering of either the dae file or stl files. There are no related errors in the terminal. I'm following the tutorial on this page: https://docs.ros.org/en/foxy/Tutorials/Intermediate/URDF/Building-a-Visual-Robot-Model-with-URDF-from-Scratch.html , where grippers are expected to show up at the end of the red cylinder. Below is my output on RVIZ2: |
Also, does anyone know why the sphere (head of robot) surface isn't smooth? |
It works well with ROS2 Humble with WSL Ubuntu 22.04 now. |
rviz2
does not have any error outputs.can't see robot model(stl file) in rviz2, the one can be seen is the collision box:
when using real ubuntu 20.04 in NUC, it can be shown correctly:
The text was updated successfully, but these errors were encountered: