IsaacSim 4.5 freezes + not finding files mentioned in documentation

Isaac Sim Version

4.5.0

Operating System

Ubuntu 22.04

GPU Information

  • Model: 5070 Ti
  • Driver Version: 570.124.04
  • NOTE: I had to install nvidia-driver-570-open for the card to work at all, and I use a chip with amd64 architecture.

Isaac loads but freezes most of the time I try to launch examples, and on top of that many files/folders mentioned in the documentation simply do not exist on my machine.

Detailed Description

The simulation loads, but as soon as I try and load a robot, it freezes. I can create basic things such as a ground plane and prims without crashing (at least, in my limited experience), but as soon as I try complex examples, or even looking into physics properties of the robot in the second quickstart tutorial (https://docs.isaacsim.omniverse.nvidia.com/4.5.0/introduction/quickstart_isaacsim_robot.html), IsaacSim freezes.
I have read on forums that the Blackwell architecture is not currently supported, so that might be it - but then agian maybe it is not. There is probably little to do until my RTX is supported, but I still find it weird that IsaacSim should freeze even at the quickstart tutorial…

Another concern is that I cannot even follow the documentation as several folders seem to be missing from my install (e.g., standalone_examples). For information, I used the pip install with a conda environment by following the instructions provided here: Python Environment Installation — Isaac Sim Documentation

While eagerly awaiting an update that will allow RTX cards with Blackwell architecture to be used with IsaacSim, I would be grateful is anyone could at least 1) let me know that either there is something wrong with my install, or the documentation is incorrect regarding files and file paths; 2) confirm that the freezing issues encountered with the provided examples will be solved by the update.

Many thanks in advance for your time.

Steps to Reproduce

  1. Follow second quickstep tutorial
  2. Go to Tools > Physics > Physics Inspector. In the newly appeared window on the left, select Franka to inspect.
  3. IsaacSim freezes

Error Messages

From the logs:
2025-04-07 11:40:40 [112,619ms] [Warning] [omni.usd] Warning: in SdfPath at line 81 of /builds/omniverse/usd-ci/USD/pxr/usd/sdf/path.cpp – Ill-formed SdfPath <>: syntax error

Additional Information

Related Issues

Additional Context

I need some form of confirmation that the pip installation is supposed to be correctly working.

I have the same problem. The Isaac sim freeze when I load the Franka robot

nVidia shoud have checked this issue earilier

@fomorin Does this issue occur only when installing Isaac Sim via PIP, and not when using the workstation installation method?

The issue is the same with the workstation installation method. Still impossible to use IsaacSim, basically.

Important note: the files and folders seem to align fully with the online documentation when using the workstation installation method.

Note 2: I spent a full day trying with different drivers, but failed to actually get any result. I even could not get 570.86.15 to work at all.

I assume this implies the instructions mentioned in Quickstart with Isaac Sim — Isaac Sim Documentation work on your setup. Could you provide the full log for the issue from the second Quickstart instructions on your workstation setup?

The first quickstart tutorial with the prims works indeed. I can also load stages and add prims (at least, as far as I can tell). The freezing issue seems to arise with robots.

I attach the log obtained with the workstation installation.

Thanks for your help!
kit_20250409_212712.log (1.3 MB)

I’m not sure if the following log snippet is related to the issue, but you may want to check or explain why omni::anim::navigation::INavigation v3.2 is in your system.

2025-04-09 19:27:18 [6,022ms] [Info] [omni.ext.plugin] About to startup: [ext: omni.anim.navigation.recast-106.4.0] (order: 0) Triggered by: isaacsim.exp.full-4.5.0 (path: /home/fom/.local/share/ov/data/Kit/Isaac-Sim Full/4.5/exts/3/omni.anim.navigation.recast-106.4.0+106.4.0.lx64.r.cp310)
2025-04-09 19:27:18 [6,022ms] [Info] [omni.kit.app.plugin] [6.032s] [ext: omni.anim.navigation.recast-106.4.0] startup
2025-04-09 19:27:18 [6,023ms] [Info] [carb] Registered plugin: omni.anim.navigation.recast (interfaces: [omni::anim::navigation::INavMeshProviderRecast v2.2],[omni::ext::IExt v0.1]) (impl: omni.anim.navigation.recast)
2025-04-09 19:27:18 [6,023ms] [Error] [carb] Interface: [omni::anim::navigation::INavigation v2.3] requested but default plugin [omni::anim::navigation::INavigation v3.2] cannot provide requested version
2025-04-09 19:27:18 [6,023ms] [Error] [carb] [Plugin: omni.anim.navigation.recast] Dependency: [omni::anim::navigation::INavigation v2.3] failed to be resolved.
2025-04-09 19:27:18 [6,024ms] [Info] [omni.ext._impl._internal] Searching for classes derived from 'omni.ext.IExt' in 'omni.anim.navigation.recast' ('/home/fom/.local/share/ov/data/Kit/Isaac-Sim Full/4.5/exts/3/omni.anim.navigation.recast-106.4.0+106.4.0.lx64.r.cp310')
2025-04-09 19:27:18 [6,024ms] [Info] [omni.ext._impl._internal] Found class `Extension` derived from `omni.ext.IExt` in module: 'omni.anim.navigation.recast' in '/home/fom/.local/share/ov/data/Kit/Isaac-Sim Full/4.5/exts/3/omni.anim.navigation.recast-106.4.0+106.4.0.lx64.r.cp310'. Calling `on_startup`.
2025-04-09 19:27:18 [6,024ms] [Error] [carb] Interface: [omni::anim::navigation::INavigation v2.3] requested but default plugin [omni::anim::navigation::INavigation v3.2] cannot provide requested version
2025-04-09 19:27:18 [6,024ms] [Error] [carb] [Plugin: omni.anim.navigation.recast] Dependency: [omni::anim::navigation::INavigation v2.3] failed to be resolved.
2025-04-09 19:27:18 [6,024ms] [Error] [carb] Interface: [omni::anim::navigation::INavigation v2.3] requested but default plugin [omni::anim::navigation::INavigation v3.2] cannot provide requested version
2025-04-09 19:27:18 [6,024ms] [Error] [carb] [Plugin: omni.anim.navigation.recast] Dependency: [omni::anim::navigation::INavigation v2.3] failed to be resolved.
2025-04-09 19:27:18 [6,025ms] [Error] [carb.scripting-python.plugin] RuntimeError: Failed to acquire interface: omni::anim::navigation::INavMeshProviderRecast (pluginName: nullptr)

At:
  /home/fom/.local/share/ov/data/Kit/Isaac-Sim Full/4.5/exts/3/omni.anim.navigation.recast-106.4.0+106.4.0.lx64.r.cp310/omni/anim/navigation/recast/scripts/extension.py(9): on_startup
  /home/fom/isaacsim/kit/kernel/py/omni/ext/_impl/_internal.py(164): _startup_ext
  /home/fom/isaacsim/kit/kernel/py/carb/profiler/__init__.py(101): wrapper
  /home/fom/isaacsim/kit/kernel/py/omni/ext/_impl/_internal.py(224): startup
  /home/fom/isaacsim/kit/kernel/py/omni/ext/_impl/_internal.py(328): startup_extension
  PythonExtension.cpp::startup()(2): <module>

2025-04-09 19:27:18 [6,025ms] [Error] [omni.ext.plugin] [ext: omni.anim.navigation.recast-106.4.0] Failed to startup python extension.
2025-04-09 19:27:18 [6,187ms] [Info] [omni.ext.plugin] [ext: omni.anim.navigation.recast-106.4.0] started, startup time: 165 (ms)

The Ubuntu install is fresh from last week, I haven’t installed much besides IsaacSim and Nvidia drivers. As far as I can tell, this must have been installed through either the pip install or the workstation install.
Your question makes it seem like it shouldn’t be here, so… should I try and remove this? If so, how?

Have you tried redoing the workstation installation method?

I can try, of course, but I strongly suspect that it won’t matter as long as I don’t clean up whatever has been put in place by the pip install method. Do you have any suggestion how to wipe the slate clean, short of a fresh Ubuntu install (which I would like to avoid as I have been installing a few other things - successfully, I must say, as IsaacSim is the only issue)?

Reporting on corrective actions.
I did two things:

  1. from the previously created conda environment:
    pip uninstall isaacsim[all]
  2. rm -rf ~/.local/share/ov

I can now report that the physics inspector does not crash any longer. I will keep pushing through the various tutorials to see if everything works as intended.

My conclusion so far is that the workstation installation is the way to go at this stage of the 4.5 development lifecycle (especially considering that the documentation seems to be written for this approach), and that the pip installation should probably be considered broken and not usable.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.