Niklas Harrysson

Ah I see! Yes, obfuscating the struct type names with a suffix sounds like a good idea then.

@ld-kerley Aha, yes that's a roadblock indeed! :) A codegen added static suffix feels a bit awkward, since as you note, node authors need to be aware of this and...

@ld-kerley About validation of a naming convention, I'm not sure we need to do that, since even if we do there is no guarantee that this will help to resolve...

Since the `thin_walled` input is uniform it doesn't work to connect a network with a varying / non-uniform parameter upstream. In order for this to work the `thickness` input must...

Thanks for the report @mkuo-lucasfilm. This is a case we have not run into before, where the concept of front and back shader assignment needs to be wrapped up in...

This sounds good to me. Besides the performance improvement, being able to blend in the thin-film effect feels very useful for artists. Since this effect is achieved by switching in...

Thank you for finding this @fnRaihanKibria, and for your proposed fix. I will investigate this further, and see if I can find the cause for the loop being created.

The cause of this issue is a limitation in the support for cascading nodegraphs. When there are multiple nodegraphs connected to each other these may be flattened into a single...

Hey @kwokcb , thanks for investigating. And yes, this will be resolved when we get to updating the ShaderGraph to keep all graph hierarchies.

(copied from Slack thread) I think there are two separate issues that could be fixed: One issue is the connection logic where by using only string names to reference another...