Hi Omniverse team,
I was testing the sbsar textures, I download a few from the link below and it seems like omniverse composer have problems reading the files, thinking there could be problems with the sbsar file i tried loading the file in 3dsmax2023 and it managed to load. Attached the sbsar file and the error log. Thanks
CarpetSubstance001.zip (356.7 KB)
kit_20240403_093006.log (2.6 MB)
We are aware that this website you have mentioned is not conforming to standard Adobe Substance / SBSAR node graph formatting. USD Composer is made to read the sbsar file format in the exact official node structure specified by Adobe. I will send you some correctly formatted sbsar texture files that work well with USD Composer, just by dragging and dropping them in. We work with Adobe to make sure we read sbsar textures correctly, but we cannot control 3rd party vendors that are making textures that are not formatted correctly.
Here is a texture that work great, that are correctly formatted.
odd_stones_01.sbsar (73.5 MB)
Hi Richard,
This is Lennart, the owner of ambientCG, the website from which the CarpetSubstance001.sbsar in this thread originally came. I have also been contacted by another user of my website who experienced a similar problem with practically identical error messages in the log. Hearing about a potential compatibility issue with my files was of course concerning and I hope we can find a solution to this compatibility issue.
These reports have lead me to investigate the problem a bit closer and I would now like to share two very simple Substance Graphs which I created using nothing but Adobe Substance 3D Designer 2023 which trigger the same error message when being loaded into the USD Composer (tested with 2023.2.5).
reproduction.zip (886.0 KB)
reproduction.zip contains 4 files, representing two substance packages (“root” and “subpath”). Both of these graphs display some matching text when opened in Substance Player. Here is how to reproduce the error message from @DavidDPD using these example files.
2024-06-09 15:53:24 [Error] [omni.ui.python] Error in 'pxrInternal_v0_22__pxrReserved__::parsePath' at line 89 in file C:\Users\bbarran\project\omniverse\kit-extensions\usd-sbsar-plugin\source\extensions\omni.usd.fileformat.sbsar\plugins\sbsarassetpathparser.cpp : 'Path format error, invalid path count 4: graphs/some_subpath/sub-graph/images?usage=roughness#packageHash=58e99640b5dc3836#params={"$outputsize":[9,9]}'
To me this error message suggests that the program has trouble reading the second SBSAR file because it contains a sub-graph inside a folder (and therefore one path element), which I would consider a perfectly normal use-case. I was able to trivially create these files in Designer without any kind of warning or trickery:
Opening the SBSAR in Adobe’s own Substance Player or Designer yields absolutely no errors or warnings, not even in the console. The sub-path is displayed properly in the software.
In fact, I chose this structure specifically to ensure that materials from ambientCG get their own folder in the content browser when loaded as a library in Substance 3D Designer.
I am therefore a bit lost about what I am supposed to do (apart from removing the sub-path from all my SBSAR files which, as I demonstrated, would cause issues elsewhere) and I’d appreciate it if you could maybe pass this on to the right department to take another look at this issue. Please let me know if you have a link to documentation regarding Substance Graph structuring from Adobe so that I can make the necessary adjustments.
Thank you for your time.
-Lennart