Composer not loading assets from Nucleus

[Jan4]

Hi there,
In the screenshot you can see the exact same model exported from Vred, on the left it is running from the Nucleus server, on the right I loaded it from my local disk, in the middle (outlined in red) you can see the Nuclesus Navigator.
All three views should show the same things, but although the data is available on the Nucleus server, the Composer does not load it from the Nucleus server. Yet It has no problem with the local version.

In the Nucleus Navigator it is clear that the files are on the server, hence it is the composer that is having trouble.

Here are some Logs:
2024-09-27 10:15:43 [Warning] [omni.usd] Warning (secondary thread): in _ReportErrors at line 2890 of W:\ac88d7d902b57417\USD\pxr\usd\usd\stage.cpp – In </XYC_showcar_Root/ME_SHOWCAR/EXT_MODEL/_3_MODEL_LED/MODEL_PO_03/ME_EXT_BBCenterTrans/ME_EXT/A_SYS/WHEELS/ME_Showcar_WHEELS_PFA_20210426/EXT/E40_WHEELS/WHEEL_ASSYM/E43_RIM_FL_wings_Assym/N2_2>: Could not open asset @omniverse://nucleus.CUSTOMER.io/Projects/XYCShowcarTestRun_V01/assets-XYC_showcar_Root/N2#2/N2%232.usd@ for reference introduced by @omniverse://nucleus.CUSTOMER.io/Projects/XYCShowcarTestRun_V01/XYC_showcar_Root.usd@</XYC_showcar_Root/ME_SHOWCAR/EXT_MODEL/_3_MODEL_LED/MODEL_PO_03/ME_EXT_BBCenterTrans/ME_EXT/A_SYS/WHEELS/ME_Showcar_WHEELS_PFA_20210426/EXT/E40_WHEELS/WHEEL_ASSYM/E43_RIM_FL_wings_Assym/N2_2> – Cannot determine file format for @omniverse://nucleus.CUSTOMER.io/Projects/XYCShowcarTestRun_V01/assets-XYC_showcar_Root/N2#2/N2%232.usd@. (instantiating stage on stage @omniverse://nucleus.CUSTOMER.io/Projects/XYCShowcarTestRun_V01/XYC_showcar_Root.usd@ <000002829EE41030>)
2024-09-27 10:15:43 [Warning] [omni.usd]
2024-09-27 10:15:43 [Warning] [omni.usd] Warning (secondary thread): in _ReportErrors at line 2890 of W:\ac88d7d902b57417\USD\pxr\usd\usd\stage.cpp – In </XYC_showcar_Root/ME_SHOWCAR/EXT_MODEL/_3_MODEL_LED/MODEL_PO_03/ME_EXT_BBCenterTrans/ME_INT_EXPORT/ME_Show_CAR_Master_EXT_n_INT_210118/INTERIOR_MODEL/HEADLINER_SWTransform/ME_Showcar_EXT_INT_Missing_Parts_2_PFA_WIP_20210427_1500/I80_HEADLINER/node_44649127>: Could not open asset @assets-XYC_showcar_Root/node#44649127/node#44649127.usd@ for reference introduced by @omniverse://nucleus.CUSTOMER.io/Projects/XYCShowcarTestRun_V01/XYC_showcar_Root.usd@</XYC_showcar_Root/ME_SHOWCAR/EXT_MODEL/_3_MODEL_LED/MODEL_PO_03/ME_EXT_BBCenterTrans/ME_INT_EXPORT/ME_Show_CAR_Master_EXT_n_INT_210118/INTERIOR_MODEL/HEADLINER_SWTransform/ME_Showcar_EXT_INT_Missing_Parts_2_PFA_WIP_20210427_1500/I80_HEADLINER/node_44649127>. (instantiating stage on stage @omniverse://nucleus.CUSTOMER.io/Projects/XYCShowcarTestRun_V01/XYC_showcar_Root.usd@ <000002829EE41030>)

THX jan

[Jan4]

Here is the screenshot:

[Richard3D]

Hi there and thanks for posting. Sorry you are having issues. I am pretty confident that this is a pathing issue with Nucleus. Your path on Nucleus is not ideal. You have “.” and " " and special characters. Omniverse does not support special characters. You can see this where you see this in “N2#2/N2%232.usd” among others.

Those red listings in your stage tree on the left side show it is failing to find the assets because of the path. If you copy those elements to much more simple paths on Nucleus, everything may work. This does not affect local machines as much. However as a good practice never use “.” or " " in a filename or any other special characters.

[Jan4]

Thx!

…it is the simple things… → like ‘are you sure it is plugged in?’

Anyway…, what sucks about it is, that those are Vred exports…so it is out of my control…, it might even be the Alias Imports into Vred. So either I have to deal with the naming convention inside the showcar design team of an OEM…, or with automated namings within the Autodesk realm…

…but here is something for you @Richard3D to chew on:

Here we have a screenshot of the same project, Local and on Nucleus:

1. • 2. → on my Local machine → no issues, loads with special characters #
2. • 4. → on Nucleus → fails to load special characters # + is ‘renaming’ the usd files inside Omniverse, while naming is fine in ‘omniverse Navigator’

N7#2.usd → N7.usd …which is bad, as the folder above is already called ‘N7’, therefore the contains of folder ‘N7#2’ and Folder ‘N7’ now have different contains named with the exact same names.

Conclusion: I need clean VRED files to export from, naming being one Issue, unjoined geometry / joined with ‘jagged seams’ being another…

Cheers Jan

[Richard3D]

And you need to use Nucleus ? It is not required. You can still work over a corporate server and network, even without Nucleus.

[Richard3D]

You could try “Collecting” the scene on your local machine and then just copying it up to your Enterprise Nucleus folder. Collecting will strip and rebuilt relative paths for everything which may solve your problem. Try FILE > COLLECT

[Jan4]

Thx, Richard

• I will try Collecting,
• but the other approach is to build a script to do it. I am using my new ‘buddy’ NIM USDcode.

cheers Jan

[Jan4]

Yes, cause I am freelancing and they are using the nucleus server and it actually saved us last week, when we had to do last minute changes, with another project. The Startup CEO being onside, and me sitting at home, working simultaneously.