Adding extension

Omniverse General Discussion
1

Hello, I am attempting to create my own “hello” extension for Create.

I’ve copied the omni.example.hello and have renamed occurrences of “example” to ahfx. eg “omni.ahfx.hello”

I’ve made an attempt to add my extension folder with kit.exe --ext-folder. It complains that it cannot find my extension.toml (see below), and Create does not show the extension in the extension manager.

Create loads the extension fine If I copy my extension to $HOME\AppData\Local\ov\pkg\create 2020.3.2_build\windows-x86_64\release\exts

I am running Create 2020.3.2

2021-03-02 16:52:29 [229ms] [Warning] [omni.ext.plugin] [ext: PACKAGE-LICENSES] Extensions config 'extension.toml' doesn't exist anywhere in 'c:/users/administrator/projects/omniversernd/extensions/omni.ahfx.hello/PACKAGE-LICENSES/**'
2021-03-02 16:52:29 [232ms] [Warning] [omni.ext.plugin] [ext: data] Extensions config 'extension.toml' doesn't exist anywhere in 'c:/users/administrator/projects/omniversernd/extensions/omni.ahfx.hello/data/**'
2021-03-02 16:52:29 [233ms] [Warning] [omni.ext.plugin] [ext: docs] Extensions config 'extension.toml' doesn't exist anywhere in 'c:/users/administrator/projects/omniversernd/extensions/omni.ahfx.hello/docs/**'
2

Hello adharder,
Thank you for posting, I will bring your inquiry to the proper channels for review.
Thank you for your patience.

3

Hi,

I might not have all data here, but it is likely that you pass actual extension with --ext-folder. Instead pass c:/users/administrator/projects/omniversernd/extensions - one folder up, folder with extensions (it will consider all subfolder being extensions). Or use --ext-path and provide exactly your extension path.

Also you can use C:\Users\[username]\Documents\Kit\shared\exts folder for hacking your extensions, it is always added.

If you run kit with -v or look into log file it writes (first line of stdout prints the location) you can see where it searches for extensions. You can also see that in properties page of extensions manager UI.

You can also run like that: kit.exe --empty --ext-path c:/users/administrator/projects/omniversernd/extensions/omni.ahfx.hello --enable omni.ahfx.hello to only enable your extension and run in as minimal configuration as possible.

4

Ah yep, you’re spot on with the --ext-folder vs --ext-path mistake.

Thanks for the search path tips. Id actually prefer to use that method.