ArnoldUSD Exported USD/USDA does not package well with USDZip
See original GitHub issueDescribe the bug When you run ArnoldUSD export from Maya, the USD contents will use string instead of asset for inputs:filename. The result is that when running USDZip, your files don’t get packaged when they should.
def Shader "file3"
{
uniform token info:id = "arnold:image"
string inputs:color_space = "sRGB"
string inputs:filename = "D:/images/someimage.png"
bool inputs:ignore_missing_textures = 1
color4f inputs:missing_texture_color = (0.5, 0.5, 0.5, 0)
string inputs:name = "file3"
color4f outputs:out
}
that string should be
asset inputs:filename = @D:/images/someimage.png@
Steps to reproduce the behavior:
- Create a shader, attach a texture to it
- Export from ArnoldUSD In Maya
- Run USDZip -a {import-path}.usda {export-path}.usdz
- List the contents of the USDZ (usdzip -l). The usdz will not reference any of the linked textures that we were expecting.
Expected behavior
- If you change the string -> asset in a usda file, and run step 3. It’ll package all the textures properly and when running usdzip -l will show all of them in the usdzip
Not Working (string inputs:filename):
>usdzip -a D:\scenes\export-with-strings.usda D:\scenes\export-with-strings.usdz
>usdzip -l D:\Scenes\export-with-strings.usdz
scenes/export-with-strings.usda
– vs – Working (asset inputs:filename)
>usdzip -a D:\scenes\export-with-assets.usda D:\scenes\export-with-assets.usdz
>usdzip -l D:\Scenes\export-with-assets.usdz
scenes/export-with-assets.usda
scenes/15/projection1-BP_001__backplate.png
scenes/15/projection2-BP_002__backplate.png
scenes/15/projection1-BP_003__backplate.png
scenes/15/projection4-BP_004a__backplate.png
scenes/15/projection5-BP_004b__backplate.png
scenes/15/projection6-BP_004c__backplate.png
scenes/15/projection7-BP_004d__backplate.png
scenes/15/projection8-BP_005__backplate.png
scenes/15/projection9-BP_006__backplate.png
scenes/15/projection10-BP_007__backplate.png
scenes/15/projection11-BP_008__backplate.png
scenes/15/projection12-BP_009__backplate.png
scenes/15/projection13-BP_010__backplate.png
scenes/15/projection14-BP_011__backplate.png
.....
Used Software Versions
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
USD export options, Bumps, Normals, Displacements and ...
I've been testing passing a whole project to Katana through the USD export plugin. Only to find there are plenty of attributes that...
Read more >Products Using USD - Pixar Graphics
Shapr3D is a CAD application that supports USD export on iPads, Mac and Windows. SideFX Houdini . Houdini is a 3D package...
Read more >HoudiniLops - cgwiki - Tokeru
Are you interested in USD, understand Vex fairly well, and want to get a more tech focused ... Once you get familiar with...
Read more >Arnold + USD = Love - YouTube
Maximize the power of Pixar's USD with Arnold software in production scenarios. We'll show examples of exporting and importing USD ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Right, we do know that these tokens are frequently used, from the debug scenes we receive from customers. So it’s something we must keep supporting. I created #1163 for that. We also had a ticket for a custom file resolver, which could perhaps also help. Cheers
Awesome, glad to see this is still being considered.