Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Troubleshooting

Runtime Errors

Driver Incompatibility

If you encounter one of the following error messages:

[Error] [carb.graphics-vulkan.plugin] VkResult: ERROR_INCOMPATIBLE_DRIVER

XlaRuntimeError: UNIMPLEMENTED: /usr/local/lib/python3.11/site-packages/jax_plugins/xla_cuda12/../../nvidia/cuda_nvcc/bin/ptxas ptxas too old. Falling back to the driver to compile.

This indicates that your NVIDIA driver is incompatible with Omniverse or the learning frameworks. To resolve the issue, update your NVIDIA driver according to the Isaac Sim driver requirements and the specific requirements of the deep learning frameworks you are using.

GLXBadFBConfig Error

If your srb agent simulated workflow crashes and you encounter the following error message, this might indicate that your system’s OpenGL version is not compatible with the requirements.

X Error of failed request:  GLXBadFBConfig
  Major opcode of failed request:  150 (GLX)
  Minor opcode of failed request:  0 ()
  Serial number of failed request:  133
  Current serial number in output stream:  133
There was an error running python

To resolve this, you can set the MESA_GL_VERSION_OVERRIDE environment variable when running the srb agent command as shown below:

MESA_GL_VERSION_OVERRIDE=4.6 srb agent ...

Alternatively for users of the provided Docker setup, you can set the environment variable for the entire Docker container by running:

./.docker/run.bash -e MESA_GL_VERSION_OVERRIDE=4.6

Slow Startup

The first launch of Isaac Sim can take several minutes due to shader compilation and asset caching. Subsequent launches are significantly faster. If startup remains slow, see this issue for potential workarounds.

If a simulated workflow selects real terrain and the cache is cold, SRB may need to fetch and bake the selected terrain before launch. Disable terrain auto-fetch for interactive runs when you want SRB to warn once and fall back to the procedural surface instead of contacting remote terrain providers:

SRB_TERRAIN_AUTO_FETCH=0 srb agent teleop -e _ground

With the provided Docker development wrapper and a virtual display:

DISPLAY=:99 DOCKER_TTY=false .docker/dev.bash -e SRB_TERRAIN_AUTO_FETCH=0 srb agent teleop -e _ground

The Docker development wrapper defaults to LOG_LEVEL=info so expected Isaac and SimForge debug logs do not hide actionable warnings. For a one-off verbose run, prefix the command with LOG_LEVEL=debug.

Hidden Isaac Startup Logs

SRB suppresses several known noisy Isaac Sim and PhysX startup log sources during srb agent workflows so important warnings remain visible. If you are diagnosing an upstream Isaac or Kit startup issue and need the raw vendor logs, disable these filters for that run:

SRB_DISABLE_ISAAC_LOG_FILTERS=1 srb agent teleop -e _ground

With the provided Docker development wrapper and a virtual display, pass the same variable into the command environment:

DISPLAY=:99 DOCKER_TTY=false .docker/dev.bash -e SRB_DISABLE_ISAAC_LOG_FILTERS=1 srb agent teleop -e _ground

Unexpected Behavior

Teleoperation Stuck

During teleoperation with the keyboard, if you change your window focus, Omniverse may fail to register a button release, causing the robot to move continuously in one direction. To fix this, press the L key to reset the environment.

Haven’t found a solution to your problem? You can search for help or ask any questions by joining our Discord community or by seeking assistance through GitHub Issues.

Discord GitHub Issues