[QUESTION] Why is Physics missing?

[DataJuggler]

Question

I followed the instructions and ran the app, and selected USD Composer option. The app launches, but Physics is missing from both Preferences and the Create and Add menus.

What happened to Physics? Physics is the main thing I use Omniverse for.

Additional Context

No response

[Administrators-0001]

I'm having problems with my device's web IDs and haven't loaded. Nvidia from the beginning it seems that there is a hack of my device can you trace the device ID to make sure

+966566200911

بتاريخ ٠٥‏/١٠‏/٢٠٢٤ ١٢:٣٧ م، كتب Data Juggler @.***>:

Question

I followed the instructions and ran the app, and selected USD Composer option. The app launches, but Physics is missing from both Preferences and the Create and Add menus.

What happened to Physics? Physics is the main thing I use Omniverse for.

Additional Context

No response

— Reply to this email directly, view it on GitHubhttps://github.com/NVIDIA-Omniverse/kit-app-template/issues/28, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLI533QIR6WPC32P5VUDBOTZZ6XM7AVCNFSM6AAAAABPNGBBDSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3DONZXHA3DQOI. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[ericcraft-mh]

I can confirm that there is an issue with Physx in 106.2. Trying to build with "omni.physx.bundle" will generate a list of version incompatibility. The only way I could get physx to work in 106.2 and as a temporary workaround is to inject omni.physx.bundle 106.1.7 before building. Any attempts to do a clean build or rebuild, even deleting the _repo and _build folders fails with errors.

1. Clone main branch: git clone https://github.com/NVIDIA-Omniverse/kit-app-template kit-physx-106.1.7
2. Create template (only tested with Composer): .\repo.bat template new
3. Edit the .kit file comment out "omni.physx.stageupdate" (~line 136): # "omni.physx.stageupdate" = {}
4. Edit the .kit file to add physx (~line 151): "omni.physx.bundle" = {version = "=106.1.7"}
5. Edit .kit disable Fabric (~line 163): useFabricSceneDelegate = false
6. Build: .\repo.bat build

[DataJuggler]

Thanks for the reply. Sorry to ask this in more than one place. I will try this over the weekend.

[SchultzC]

There was a delay in publishing some of the extensions. Physx 106.2.0 was one such extension. The issue should now be resolved (without requiring a version lock). Please reopen this issue if you have any other problems.

[DataJuggler]

I just cloned the repo today, and Physics was not included. Do I still have to run the instructions where I set the version 6.1.7?

Why is the Extension Manager missing also?

[ericcraft-mh]

I just cloned the repo today, and Physics was not included. Do I still have to run the instructions where I set the version 6.1.7?

Why is the Extension Manager missing also?

Physx and the Extension Manager are not included by default. Use launch -d then enable extension manager on autoload same with physx bundle.

[DataJuggler]

OK, the -d showed the Extension Manager. I still don't see Physics as an option on menus. Is there something I need to do?

Thanks

[SchultzC]

@ericcraft-mh is correct. Niether of these things are enabled by default in the Composer template. Looks like you have the extension manager now.

To add omni.physx.bundle in a persistent way to your application add:

omni.physx.bundle = {}

to the [dependencies] section of the .kit file located in source/apps and rebuild the application.

[DataJuggler]

That worked. I am going to make a video about this so I don't forget. Thanks

[DataJuggler]

Last question and I will leave you alone. How do I get the Array tool to show up? Is there a list of all the extension names somewhere so I can which ones I need to add?

[DataJuggler]

I figured out the Array. I will try adding it the same was as Physics.

Was surprised to see a message Physics can't run with Fabric. That was the magic of Fabric, it enabled Physics to handle large amounts of objects. Is there a reason they don't work together anymore.

Thanks again.