MaterialX mtlx mix BSDF node bug

   2018   5   1
User Avatar
Member
37 posts
Joined: March 2017
Offline
Just wanted to see if nyone else has noticed a bug when mixing BSDFs with mtlx mix

when set to 0 it shows input1



and when set to 1 it also shows input 1



if you use a value of 0.001 it does show input0



this seems to occur specifically with the BSDF mode.

this makes shader building difficult. It seems when a constant is plugged in with the value of 0 the issue does not occur



would be great to see if anyone else has had this issue?

Best,
Rich
Edited by Hypershader - May 4, 2022 09:51:59

Attachments:
0.png (460.3 KB)
1.png (715.4 KB)
0.001.png (644.8 KB)
constant.png (707.7 KB)

User Avatar
Member
729 posts
Joined: July 2005
Offline
I'm seeing the same thing. It works fine when driven by inputs like your constant or a noise, but yeah, it seems like the Mix parameter on its own is borked.
User Avatar
Member
8043 posts
Joined: Sept. 2011
Offline
I think there was a bug that was recently fixed for nodes with inputs at default values not triggering an update.
User Avatar
Member
37 posts
Joined: March 2017
Offline
Can you send me over the release note describing the fix please?
User Avatar
Member
8043 posts
Joined: Sept. 2011
Offline
Hypershader
Can you send me over the release note describing the fix please?



Fixed a bug with retranslating a shader node parameter when it's set back to adefaule value, which would not get reflected in the USD shader on the stage.
Wed. April 27, 2022
User Avatar
Member
8043 posts
Joined: Sept. 2011
Offline
jsmack
Hypershader
Can you send me over the release note describing the fix please?



Fixed a bug with retranslating a shader node parameter when it's set back to adefaule value, which would not get reflected in the USD shader on the stage.
Wed. April 27, 2022

I guess it hasn't been backported
  • Quick Links