Omni.anim.navigation.meshtools start failed when start omni.anim.navigation.bundle

omni.anim.navigation.meshtools & omni.anim.navigation.bundle load failed !

I’m trying calib camera and add try setting the NavMesh.

A valid NavMesh is required. Camera Calibration (isaacsim.replicator.agent.camera_calibration) — Isaac Sim Documentation

Then, I try upgrade schema core to v106.5.*, the core ext is load failed again.


file omni.anim.navigation.meshtools-106.4.1+106.4.0.lx64.r.cp310/omni/anim/navigation/meshtools/bindings/_omni_navmeshtools.cpython-310-x86_64-linux-gnu.so
omni.anim.navigation.meshtools-106.4.1+106.4.0.lx64.r.cp310/omni/anim/navigation/meshtools/bindings/_omni_navmeshtools.cpython-310-x86_64-linux-gnu.so: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=329a9a51a240a807fe223a9cc15e17bd2e714b90, stripped


file omni.anim.navigation.core-106.4.0+106.4.0.lx64.r.cp310/omni/anim/navigation/core/bindings/_omni_anim_navigation_core.cpython-310-x86_64-linux-gnu.so 
omni.anim.navigation.core-106.4.0+106.4.0.lx64.r.cp310/omni/anim/navigation/core/bindings/_omni_anim_navigation_core.cpython-310-x86_64-linux-gnu.so: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=cb210a1baaf5e747a125c78bbd6cb667ae79b3ca, stripped

Isaac Sim Version

[-] 4.5.0

Operating System

[-] Ubuntu 22.04

GPU Information

  • Model:
  • Driver Version:

Topic Description

Detailed Description

(Describe the issue in detail, including what you were trying to do, what you expected to happen, and what actually happened)

Steps to Reproduce

(Add more steps as needed)

Error Messages

(If applicable, copy and paste any error messages you received)

Screenshots or Videos

(If applicable, add screenshots or links to videos that demonstrate the issue)

Additional Information

What I’ve Tried

(Describe any troubleshooting steps you’ve already taken)

Related Issues

(If you’re aware of any related issues or forum posts, please link them here)

Additional Context

(Add any other context about the problem here)

1 Like

Is this still an open issue? If yes, could you confirm at which step in the documentation or workflow you encounter this problem?