Describe the bug
When a .usd file is loaded and resaved either via kick or AiSceneWrite directly if a shader is only linked via a custom primvar the the shader is removed from the ArnoldUnassignedShaders prim
To Reproduce
Steps to reproduce the behavior:
- download the example test_custom_shader.usda.zip
- run the kick comand:
kick -i test_custom_shader.usda -resave test_custom_shader_resaved.usda
- the resulting usda file removed the
ArnoldUnassignedShaders nodegraph
Expected behavior
All shaders in and ArnoldUnassignedShaders Prim should remain on resaving the USD file via AiSceneWrite
Used Software Versions
Additional context
If I remove the line
string inputs:name = "myRefShader"
The nodegaph remains when re-saving
Describe the bug
When a .usd file is loaded and resaved either via kick or AiSceneWrite directly if a shader is only linked via a custom primvar the the shader is removed from the
ArnoldUnassignedShadersprimTo Reproduce
Steps to reproduce the behavior:
kick -i test_custom_shader.usda -resave test_custom_shader_resaved.usdaArnoldUnassignedShadersnodegraphExpected behavior
All shaders in and
ArnoldUnassignedShadersPrim should remain on resaving the USD file via AiSceneWriteUsed Software Versions
Additional context
If I remove the line
The nodegaph remains when re-saving