Removed Tools and Replacements#
Some Isaac Sim 6.0 changes do not have a drop-in migration API. For these dependencies, remove the extension, move the workflow into project-owned code, or adopt the listed replacement.
Removed or Deprecated Tools#
Tool or extension |
Migration decision |
Replacement |
|---|---|---|
|
Isaac Sim 6.0 removes this tool. Delete dependencies and launch the intended app directly from the project workflow. |
None. |
|
Isaac Sim 6.0 removes this extension. Move any copied sample logic into project-owned benchmark scripts and migrate to benchmark services recorders. |
|
|
Isaac Sim 6.0 removes this extension. Keep generated assets under project ownership or rebuild the workflow with supported Replicator APIs. |
None. |
|
Isaac Sim 6.0 splits this extension into separate core and UI
extensions. Update |
|
|
Isaac Sim 6.0 splits this extension into separate core and UI
extensions. Replace the dependency with
|
|
|
Isaac Sim 6.0 removes this extension. Update app dependencies and user instructions to use the SimReady content browser. |
|
|
Isaac Sim 6.0 removes this extension and the
|
|
|
Isaac Sim 6.0 deprecates this extension with no replacement package. Install PyTorch and related ML dependencies directly in the project environment. Enable the deprecated extension only as a temporary legacy bridge. |
Project-owned Python environment. |
|
Isaac Sim 6.0 deprecates this extension. Generate new extensions from repo templates. |
|
|
Isaac Sim 6.0 deprecates this extension. Split the workflow across supported robot setup tools. |
|
|
Isaac Sim 6.0 deprecates this Kit command. Replace
|
|
Manifest Migration#
Search every app and extension manifest for these dependency names. A migrated manifest should either delete the dependency or replace it with a documented replacement. Do not keep a removed extension in a dependency list because a local checkout still has stale generated files; the extension is not available in the 6.0 package.
Validation Checklist#
Verify the following after updating manifests:
App and extension manifests do not enable removed extensions.
Startup logs do not contain missing-extension errors for removed tools.
Any project workflow that copied behavior from a removed example has an owner, tests, and CI coverage in the project repository.
Project documentation does not reference the removed app selector, asset browser, benchmark example extension, or Scene Blox extension.
ML dependencies resolve from the project Python environment without relying on
omni.isaac.ml_archive.