Rviz does not display meshes with GPU enabled
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11.9k
- Forks
- 429
- PR merge metrics
- No merged PRs in 30d
Description
Environment
Windows build number: 10.0.22000.0
Your Distribution version: Ubuntu 18.04
Your WSLg version: 1.0.26
ROS version: Melodic
Steps to reproduce
Launch any MoveIt demo launchfiles. Open Rviz, load the RobotModel plug-in.
WSL logs:
pulseaudio.log
weston.log
versions.txt
Expected behavior
Rviz would display the 3D meshes.
Actual behavior
Rviz opens up using the Nvidia GPU. See below for the logs from Rviz. I then load the RobotModel and TF plug-ins. As seen in the screenshot, the coordinate frames get displayed correctly, but the meshes from the robot model do not.

[ INFO] [1635847601.963606500]: rviz version 1.13.19
[ INFO] [1635847601.963664900]: compiled against Qt version 5.9.5
[ INFO] [1635847601.963704800]: compiled against OGRE version 1.9.0 (Ghadamon)
[ INFO] [1635847601.973562500]: Forcing OpenGl version 0.
[ INFO] [1635847604.867335000]: Stereo is NOT SUPPORTED
[ INFO] [1635847604.867490400]: OpenGL device: D3D12 (NVIDIA GeForce GTX 1050 Ti with Max-Q Design)
[ INFO] [1635847604.867577100]: OpenGl version: 3.1 (GLSL 1.4).```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by launching a MoveIt demo, opening Rviz, and loading the RobotModel and TF plug-ins with GPU acceleration enabled. Start by reviewing the supplied weston.log, versions.txt, and Rviz output, then trace the WSLg graphics path implicated by the D3D12/NVIDIA OpenGL device; done means Rviz displays the robot meshes as well as coordinate frames.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, ubuntu
- Domain
- computer-graphics, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100