Nvblox Mesh Visualization Problem - Release 3.2

Robotics & Edge Computing Robotics - Isaac Isaac ROS
1

Hi all,

I’m testing nvblox ROS wrapper in a x86_64 machine using the updated docker devel environment for release 3.2 following the quickstart section here, where I’m running using the debian pkgs.

After following the instructions and running the example launch file for Isaac Sim I find myself having issues to visualize the generated mesh.
For my setup the RViz node launched from the launch process has always given me problems (this is not the issue I’m currently focused on), so I join to a second docker session of the container (using the run_dev.sh script) where I run a new RViz node via rviz2. However, when adding the topic and trying to visualize the mesh RViz returns the following message

Nvblox plugin did not detect a geometry shader capable GPU. Using fallback rendering.

and not mesh is displayed at all.

I tested all the package functionality in release 3.1 1+ months ago with no issues. I’ve noticed there’s been changes to the visualization plugin but I’m not familiar with OGRE as to realize what change could be bringing this issue.
I’ve tested the packages in two different host machines for the container:

  1. Ubuntu 20.04, nvidia driver 560.35.03, Geforce RTX3070 Ti Laptop GPU
  2. Ubuntu 22.04, nvidia driver 565.77, Geforce RTX4060 Laptop GPU

running into the rviz message and no mesh is visualized. All other topics seem to be displayed as expected.

Screenshot from 2025-01-30 14-10-04
Screenshot from 2025-01-30 14-10-041920×994 147 KB

Has anyone come across a similar issue? Any suggestions where to start would be appreciated! Thanks.

2

Update: The issue seemed to be related to the openGL renderer. I managed to set up the engine to point to my Nvidia GPU and I am now able to visualze the mesh. However, if my understanding is correct, when using the Intel integrated graphics card the rviz plugin should roll to a fallback visualizer, which I believe is not working properly for the mesh message (it does work for the VoxelBlockLayer message).