Doug Smythe

I've updated the v1.39 Spec document to mention support for per-channel operations: The Mix node takes two 1-4 channel inputs `fg` and `bg` plus a separate 1-channel (float) or _N_-channel...

Regarding @JGamache-autodesk 's thought about adding a hint for anisotropy, this is an interesting idea which I think the hint system might be able to accommodate, though not quite in...

I think the intended wording should be "Input values below `inlow` or above `inhigh` are extrapolated unless `doclamp` is true." E.g. if an input value is between `inlow` and `inhigh`,...

In the WIP v1.39 Specification, there is a new proposed node, that takes 3 vector3 or 4 vector4 row vectors, and creates a 3x3 or 4x4 matrix from them. Those...

If you provide a float value for "gamma", the more consistent-with-other-operations result would be to apply it to all four channels, including alpha, e.g. the current behavior, which I think...

While I was adding these documentation changes, I had a few questions that should be discussed and resolved: - randomfloat/randomcolor: why do these have an "in" input? They also have...

I think that arbitrarily choosing the "first" matching node definition could still not be deterministic enough- what if a site an another definition of a node in its own local...

This is exactly the situation I was thinking about when suggesting "use the simpler of the two matching definitions if both signatures match": in this example, ND_mix_color3 is "simpler" than...

Third!-DougOn Aug 24, 2023, at 8:49 PM, Nick Porcino ***@***.***> wrote: I second a vote for strict casing. —Reply to this email directly, view it on GitHub, or unsubscribe.You are...

Apologies for the ugly email-reply formatting above, but yes, the intent of the Spec is that all naming in MaterialX (nodenames, inputs, attributes, etc. etc.) is **case sensitive**.