Incorrect handling of shaders referenced in multiple materials #1940
Labels
bug
Something isn't working
Comments
|
Issue synced internally to ARNOLD-15203 |
sebastienblor
added a commit
to sebastienblor/arnold-usd
that referenced
this issue
Jun 24, 2024
sebastienblor
added a commit
to sebastienblor/arnold-usd
that referenced
this issue
Jun 25, 2024
…rarchy of materials Autodesk#1940
sebastienblor
added a commit
that referenced
this issue
Jun 25, 2024
sebastienblor
added a commit
that referenced
this issue
Jun 26, 2024
* Ensure polymesh topology attributes are not written to USD when not set #1914 * Fix behaviour when the vidxs array is null #1914 (#1915) * Fix instance primvar indices with multiple prototypes #1923 (#1925) * Ensure subdiv_iterations is not set uselessly during procedural updates (#1931) * Ensure subdiv_iterations is not set uselessly during procedural updates #1929 (cherry picked from commit 1adc860) * Add changelog * check if the VtValue is empty before doing a UncheckedGet (#1934) * update changelog for 7.3.2.1 release (#1943) * Support shaders shared by multiple materials (#1945) * Support shader shared by multiple materials #1940 * Add changelog * Improve connection resolution for shaders which are not under the hierarchy of materials #1940 --------- Co-authored-by: cpichard <cpichard@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When several materials or shaders are referencing a shader that belongs to another material, the render delegate will assign the shader to only one material.
To Reproduce
Unzip the following scene and render with an arnold render delegate
test.usda.zip
Only one light has the light blocker where both should have it.
Used Software Versions
The text was updated successfully, but these errors were encountered: