How can I use the latest version of warp inside omniverse?

Omniverse Isaac Sim
1

I want to use warp 1.4.1 inside omniverse, the the current version of warp inside omniverse is 1.1.0. If I pip install warp-lang using the kit pip api specifying the version, it will install the package but will still using the warp extension with version 1.1.0

I tried pip installing into the python env before starting omniverse: ./python.sh -m pip install warp-lang
But this has the same problem.

I also tried disabling the extension using the gui. But that did not work, warp was still present and it was version 1.1.0

I tried going to the extension itself in extscache/omni.warp.core-1.1.0 and renaming it so that it will find the other version of warp I pip installed but it seems somehow hard-coded to search for the extension.
AttributeError: partially initialized module ‘warp’ has no attribute ‘config’ (most likely due to a circular import)
/home/me/.local/share/ov/pkg/isaac-sim-4.0.0/extscache/omni.warp.core-1.1.0/warp/init.py(108):

Any help on this would be greatly appreciated!

Isaac Sim Version

4.2.0
4.1.0
4.0.0
2023.1.1
2023.1.0-hotfix.1
Other (please specify):

Operating System

Ubuntu 22.04
Ubuntu 20.04
Windows 11
Windows 10
Other (please specify):

GPU Information

  • Model: rtx4090
  • Driver Version: 535
2

May we know why you need warp 1.4.1? Isaac Sim version 4.2.0 has only warp version 1.2.1.

3

Thanks for asking, I love using warp and I want to use the new VBD integrator, it is a very stable simulation backend that prevents my sim from exploding and it is only available in the latest version of warp.

4

Hi @VickyNV, thank you for responding. Do you know if there is any way I can update warp or at least uninstall the warp 1.1.0 so I can use the pip installed one? This is a blocking issue for me, and I could really use your help!

5

Would Warp1.2.1, included in Isaac Sim 4.2.0, be suitable for your needs?

6

Unfortunately no, the VDB_integrator is only available in 1.4.0 or later.

8

Please wait for the upcoming release which will include Warp 1.4.x.

9

Are you sure there is nothing I can do in the mean time? I’m doing my best here to find some sort of work around.

Also do you know what the timeline is on the next release?

10

While it’s possible to update extensions through the Extension Manager if a newer version is available in the public extension registry. But there is no guarantee it will work.

11

Thank you for this suggestion, I can update the extension but it only goes to 1.2.1. This seems a bit weird since I see the updated extension on the Warp github at 1.4.2 warp/exts/omni.warp.core/config/extension.toml at main · NVIDIA/warp · GitHub look at line 3 in the config.

To be clear I don’t even need the omniverse extension, if I could uninstall it so the pip installed version could take priority that would solve all my problems. But even after I disable the extension through the gui, I still see the package installed.

12

Thank you for your follow-up and for providing more details about your situation. I appreciate your persistence in trying to resolve this issue.

I’ve discovered that omni.warp 1.4.1 is actually available for upgrade in the Extensions window:

  1. disable the current Warp extension through the GUI.
  2. check the Extensions window again. You should now see the option to upgrade to version 1.4.1.

After following these steps, I was able to successfully update and run the newer version. Here’s a snippet from my log that confirms this:

[5.151s] [ext: omni.warp-1.4.1] startup
…
2024-11-15 18:29:31 [5,178ms] [Warning] [omni.replicator.core.scripts.annotators] Annotator PostProcessDispatch is already registered, overwriting annotator template
Warp 1.4.1 initialized:
CUDA Toolkit 11.8, Driver 12.2
Devices:
“cpu” : “x86_64”
“cuda:0” : “NVIDIA RTX 6000 Ada Generation” (47 GiB, sm_89, mempool enabled)
Kernel cache:
/home/vyu/.cache/warp/1.4.1

13

WOW that was convenient! Thank you @VickNV!

14

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