You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Loading the same MaterialX file in to MaterialXView displays the material as expected. MaterialXView --material triplanar.mtlx renders
Investigations
Taking a cursory look at the code it appears that Storm expects there to only be one input port of type filename per shader node. Here the triplanar node has three.
Fixes:
- MaterialX: Storm fails to reuse GLSL shaders for networks differing only on node names PixarAnimationStudios#2330
- Storm shader compilation errors when using MaterialX triplanarprojection node. PixarAnimationStudios#3004
- Improve transparency detection and fix generation
Using a topo-trimmed network resulted in all shaders being generated
with opaque semantics. The shaders are now created with the right
transparent hardware settings.
Also improved transparency detection at the _GetMaterialTag level by
adding more checks for known surfaces and delegating to MaterialX when
dealing with custom shaders, but without generating the full MaterialX
document.
Description of Issue
When using the MaterialX
<triplanarprojection>
in a material, then Storm reports shader compilation errors.Steps to Reproduce
usdview triplanar.usda
(from attached zip file)Loading the same MaterialX file in to MaterialXView displays the material as expected.
MaterialXView --material triplanar.mtlx
rendersInvestigations
Taking a cursory look at the code it appears that Storm expects there to only be one input port of type
filename
per shader node. Here the triplanar node has three.triplanar_bug.zip
The text was updated successfully, but these errors were encountered: