Showstopper problem trying Omniverse tutorial

JonJingleberry · March 23, 2023, 8:54pm

So, I thought I’d try the demo for omniverse (Cesium for Omniverse Quickstart – Cesium), but also running into no love :-(. Step 1.6 in the tutorial shows the omniverse plugin 0.3.0 should be ok. However, in reality, I’m seeing a red-triangle with exclamation point, which seems like it is trying to say it is some problem in loading (attached)–no place to explain what the icon means. The omniverse plugin for USD seems to be loaded fine. I can’t seem to proceed with the demo without this.

-jonathan

sean_lilley · March 23, 2023, 10:45pm

Hi Jonathan - thanks for reaching out.

Could you check if there are any errors in the console?

Also could you post more details about your environment - OS, GPU, and Create version?

JonJingleberry · March 23, 2023, 11:48pm

Hi Sean, thanks for checking. I am using the Omniverse app with Create v 2022.3.3, Windows 11 Home build 22621.1413, 11th Gen Intel(R) Core™ i9-11900H, with NVIDIA GeForce RTX 3050 Ti Laptop GPU.

I tried removing the cesium extensions from the exts folder after disabling the USD extension from the Extensions window. When I opened Create, I got this message in the Console:

2023-03-23 23:36:24 [Warning] [omni.ext.plugin] [ext: omni.kit.scripting-104.2.2] 'c:/users/kayej/appdata/local/ov/pkg/create-2022.3.3/extscache/omni.kit.scripting-104.2.2+104.2.wx64.r.cp37/bin' in '[[native.plugin]]' was not found.

For the fun of it, I removed omni.kit.scripting-104.2.2 and then Create would not launch, so I put it back. I also then put the 2 cesium folders from version 0.3.0 into place in Documents\Kit\Shared\exts, and got these 3 messages when I launched Create:

2023-03-23 23:42:29  [Warning] [omni.ext.plugin] Extension with the same id is already registered. ext_id: 'cesium.omniverse-0.3.0', ext 1: 'c:/users/kayej/appdata/local/ov/data/kit/create.next/2022.3/exts/3/cesium.omniverse-0.3.0+wx64.r.cp37', ext 2: 'c:/users/kayej/documents/kit/shared/exts/cesium.omniverse'
2023-03-23 23:42:29  [Warning] [omni.ext.plugin] [ext: omni.kit.scripting-104.2.2] 'c:/users/kayej/appdata/local/ov/pkg/create-2022.3.3/extscache/omni.kit.scripting-104.2.2+104.2.wx64.r.cp37/bin' in '[[native.plugin]]' was not found.
2023-03-23 23:42:44  [Warning] [omni.ext.plugin] Extension with the same id is already registered. ext_id: 'cesium.omniverse-0.3.0', ext 1: 'c:/users/kayej/appdata/local/ov/data/kit/create.next/2022.3/exts/3/cesium.omniverse-0.3.0+wx64.r.cp37', ext 2: 'c:/users/kayej/documents/kit/shared/exts/cesium.omniverse'

Then I went into Extensions and tried to activate the 2 Cesium plugins. Back in the console, I got the following messages:

2023-03-23 23:45:30  [Error] [carb] loadPlugin: Library path doesn't exist: c:/users/kayej/appdata/local/ov/data/kit/create.next/2022.3/exts/3/cesium.omniverse-0.3.0+wx64.r.cp37/bin/cesium.omniverse.plugin.dll
2023-03-23 23:45:30  [Error] [omni.ext.plugin] [ext: cesium.omniverse-0.3.0] failed to load native plugin: c:/users/kayej/appdata/local/ov/data/kit/create.next/2022.3/exts/3/cesium.omniverse-0.3.0+wx64.r.cp37/bin/cesium.omniverse.plugin.dll
2023-03-23 23:45:30  [Error] [omni.ext._impl.custom_importer] Failed to import python module cesium.omniverse. Error: No module named 'cesium.omniverse.bindings.CesiumOmniversePythonBindings'. Traceback:
...

I tried to uninstall Create app from the launcher and from Windows Add Programs, but for the life of me I can’t see where to uninstall it. I tried uninstalling the Omniverse launcher, but when I reinstalled that, the Create app was ready to launch. I am reluctant to uninstall other NVIDIA apps on my system because I do have an NVIDIA graphics card and I might mess stuff up there.

I also tried installing the Cesium plugins from the Extensions window directly (i.e., not putting the files in the Documents folder as instructed in the tutorial). I got more errors than before.

Thanks for any help!

adam_morris · March 24, 2023, 2:28pm

Hi Jon, sorry to see that you’re having issues. Let’s get you to a clean install of Create.

To uninstall Create you can click the “hamburger menu” next to the launch button in the Omniverse Launcher. It’s the button my mouse is hovering over in the screenshot below.

omniverse_hamburger_menu

That will open a little menu and you can click “Settings” which will open the screen where you can uninstall Create. Go ahead and uninstall it, then before you reinstall, make sure the “$HOME/Documents/Kit/shared/exts/” path is empty.

Once you do that, run Create once just to verify everything is working again. Then, close Create, and reinstall Cesium for Omniverse to the “Documents/Kit/shared/exts/” path and run Create again. If you’re still having issues please share the errors you’re having in the console at that time.

vsnappy · March 28, 2023, 5:45pm

Would love to try this out, but I’m experiencing the same issue. Create 2022.3.3 …

2023-03-28 17:42:20  [Warning] [omni.ext.plugin] [ext: omni.kit.scripting-104.2.2] 'c:/users/ksnapka/appdata/local/ov/pkg/create-2022.3.3/extscache/omni.kit.scripting-104.2.2+104.2.wx64.r.cp37/bin' in '[[native.plugin]]' was not found.
2023-03-28 17:42:49  [Error] [omni.ext.plugin] Could not load the dynamic library from c:/users/ksnapka/appdata/local/ov/data/kit/create.next/2022.3/exts/3/cesium.usd.plugins-0.1.0+wx64.r.cp37/bin/InMemoryAssetResolver.dll. Error: The specified module could not be found.
2023-03-28 17:42:49  [Error] [omni.ext.plugin] 
2023-03-28 17:42:49  [Error] [omni.ext.plugin] Could not load the dynamic library from c:/users/ksnapka/appdata/local/ov/data/kit/create.next/2022.3/exts/3/cesium.usd.plugins-0.1.0+wx64.r.cp37/bin/CesiumUsdSchemas.dll. Error: The specified module could not be found.
2023-03-28 17:42:49  [Error] [omni.ext.plugin] 
2023-03-28 17:42:51  [Error] [carb] loadPlugin: Library path doesn't exist: c:/users/ksnapka/appdata/local/ov/data/kit/create.next/2022.3/exts/3/cesium.omniverse-0.3.0+wx64.r.cp37/bin/cesium.omniverse.plugin.dll
2023-03-28 17:42:51  [Error] [omni.ext.plugin] [ext: cesium.omniverse-0.3.0] failed to load native plugin: c:/users/ksnapka/appdata/local/ov/data/kit/create.next/2022.3/exts/3/cesium.omniverse-0.3.0+wx64.r.cp37/bin/cesium.omniverse.plugin.dll
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer] Failed to import python module cesium.omniverse. Error: No module named 'cesium.omniverse.bindings.CesiumOmniversePythonBindings'. Traceback:
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer] Traceback (most recent call last):
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]   File "c:/users/ksnapka/appdata/local/ov/pkg/create-2022.3.3/kit/kernel/py\omni\ext\_impl\custom_importer.py", line 76, in import_module
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]     return importlib.import_module(name)
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]   File "c:\users\ksnapka\appdata\local\ov\pkg\create-2022.3.3\kit\python\lib\importlib\__init__.py", line 127, in import_module
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]     return _bootstrap._gcd_import(name[level:], package, level)
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]   File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]   File "<frozen importlib._bootstrap>", line 983, in _find_and_load
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]   File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]   File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]   File "<frozen importlib._bootstrap_external>", line 728, in exec_module
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]   File "c:\users\ksnapka\appdata\local\ov\data\kit\create.next\2022.3\exts\3\cesium.omniverse-0.3.0+wx64.r.cp37\cesium\omniverse\__init__.py", line 1, in <module>
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]     from .extension import *  # noqa: F401 F403 F405
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]   File "c:\users\ksnapka\appdata\local\ov\data\kit\create.next\2022.3\exts\3\cesium.omniverse-0.3.0+wx64.r.cp37\cesium\omniverse\extension.py", line 1, in <module>
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]     from .bindings import acquire_cesium_omniverse_interface, release_cesium_omniverse_interface
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]   File "c:\users\ksnapka\appdata\local\ov\data\kit\create.next\2022.3\exts\3\cesium.omniverse-0.3.0+wx64.r.cp37\cesium\omniverse\bindings\__init__.py", line 1, in <module>
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer]     from .CesiumOmniversePythonBindings import *  # noqa: F401 F403
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer] ModuleNotFoundError: No module named 'cesium.omniverse.bindings.CesiumOmniversePythonBindings'
2023-03-28 17:42:51  [Error] [omni.ext._impl.custom_importer] 
2023-03-28 17:42:51  [Error] [carb.scripting-python.plugin] Exception: Extension python module: 'cesium.omniverse' in 'c:\users\ksnapka\appdata\local\ov\data\kit\create.next\2022.3\exts\3\cesium.omniverse-0.3.0+wx64.r.cp37' failed to load.
2023-03-28 17:42:51  [Error] [carb.scripting-python.plugin] 
2023-03-28 17:42:51  [Error] [carb.scripting-python.plugin] At:
2023-03-28 17:42:51  [Error] [carb.scripting-python.plugin]   c:/users/ksnapka/appdata/local/ov/pkg/create-2022.3.3/kit/kernel/py\omni\ext\_impl\_internal.py(189): startup
2023-03-28 17:42:51  [Error] [carb.scripting-python.plugin]   c:/users/ksnapka/appdata/local/ov/pkg/create-2022.3.3/kit/kernel/py\omni\ext\_impl\_internal.py(285): startup_extension
2023-03-28 17:42:51  [Error] [carb.scripting-python.plugin]   PythonExtension.cpp::startup()(2): <module>
2023-03-28 17:42:51  [Error] [carb.scripting-python.plugin]   c:\users\ksnapka\appdata\local\ov\pkg\create-2022.3.3\kit\exts\omni.kit.window.extensions\omni\kit\window\extensions\ext_commands.py(29): do
2023-03-28 17:42:51  [Error] [carb.scripting-python.plugin]   c:\users\ksnapka\appdata\local\ov\pkg\create-2022.3.3\kit\extscore\omni.kit.commands\omni\kit\undo\undo.py(80): execute
2023-03-28 17:42:51  [Error] [carb.scripting-python.plugin]   c:\users\ksnapka\appdata\local\ov\pkg\create-2022.3.3\kit\extscore\omni.kit.commands\omni\kit\commands\command.py(459): execute
2023-03-28 17:42:51  [Error] [carb.scripting-python.plugin]   c:\users\ksnapka\appdata\local\ov\pkg\create-2022.3.3\kit\exts\omni.kit.window.extensions\omni\kit\window\extensions\common.py(287): toggle_extension
2023-03-28 17:42:51  [Error] [carb.scripting-python.plugin]   c:\users\ksnapka\appdata\local\ov\pkg\create-2022.3.3\kit\exts\omni.kit.window.extensions\omni\kit\window\extensions\ext_components.py(89): toggle
2023-03-28 17:42:51  [Error] [carb.scripting-python.plugin] 
2023-03-28 17:42:51  [Error] [omni.ext.plugin] [ext: cesium.omniverse-0.3.0] Failed to startup python extension.

JonJingleberry · March 28, 2023, 6:23pm

Hi Adam, thanks for the help, just to close the loop I was able to uninstall Create but when reinstalling, just got the same error about the id already being used. Unfortunately, I have to move on so I can’t spend more time on this.

-jonathan
BTW FYI trying to uninstall the Ominverse Launcher is a bear (nothing to do with Cesium) – going through typical Windows install tells me it’s no longer there, but on my computer reboot, hey-yo! there it pops up. I turned off the app to launch when Windows starts, so I’m pretending that I really uninstalled it, but I know deep down it is still lurking. Problem I have deleting folders/files in my NVIDIA folder is I don’t know which folders/files are needed for my graphics driver and its gui.

sean_lilley · March 28, 2023, 10:05pm

Hi @vsnappy @JonJingleberry, we think we know the problem here. If you tried installing Cesium for Omniverse from the extensions window without first installing the release zip it won’t work. Make sure to follow the instructions in the Cesium for Omniverse Quickstart by downloading the release zip and copying the extensions into Documents/Kit/Shared/exts.

If done correctly, you should see the image on the right

Installed from repo	Installed from release zip
flag1628×692 143 KB	flag1628×692 105 KB

The reason that installing from repo doesn’t work is because our extension consists of C++ code that is compiled into several DLLs. We don’t include prebuilt DLLs in our github source tree, only in the release zip.

We’ll think about how to improve this workflow so it doesn’t cause confusion for others. Hopefully this helps get you up and running.

vsnappy · March 29, 2023, 12:55pm

Thanks Sean,

That helped immensely. I did need to track down the previous repo based install and remove it from my /AppData/Local/ov/data/Kit/Create.Next/2022.3/exts/3 directory.

I think the confusion is based on the “Install” button in the Omniverse Extensions browser and no mention of the Quickstart or need to use the zip files in the Extensions description presented in the Omniverse Extensions browser.

sean_lilley · March 29, 2023, 2:48pm

@vsnappy glad to hear it helped. And thanks for posting those extra steps. I think that explains the “Extension with the same id is already registered” error that @JonJingleberry was running into.

I agree that it’s confusing and we’re seeing what changes we can make for how Cesium for Omniverse appears in the extension registry.

sean_lilley · April 10, 2023, 7:20pm

Just to give an update here, the reason Cesium for Omniverse appears in the extension registry as a community extension is because we were using the omniverse-kit-extension tag. Nvidia automatically scans GitHub for all repos with that tag and adds them as community extensions.

We’ve since removed the tag and are waiting for the extension registry to be updated. Once that happens you’ll no longer see the community extension; the extension will only appear if you install it according to the Cesium for Omniverse Quickstart.

sean_lilley · April 17, 2023, 3:26pm

This issue is now fixed. Cesium for Omniverse no longer appears as a community extension.