Closed stephantual closed 6 months ago
Hm the problem with rgthree reroute exactly just like the native reroute node, as both cannot determine the output type of Junction
since inherently the actual type can be changed.
Since both reroute and Junction
have dynamic types, this will cause chicken and egg problem since both needs type to but cannot provide types.
CastReroute
does exactly that which is to pin the Junction
output to the desired type and give some type to work on with.
Thank you and Happy New Year! Makes sense - The reason I was asking was to 'display' what was going where within a group as part of super large worflows , in order to make sense of the inputs which aren't standards (say, arbitrary ints or floats). Thank you for making this so flexible! I appreciate your help.
Trying to make my layout looks nice . Imagine a standard junction node with model, latent, and a few ints etc. Let's imagine i want to output just the clip, but i want to route it first. Can I do that?
Right now i'm using collapsed junctions or 'cast reroutes' as reroutes but it doesn't feel 'right', becaues one carries the whole context and the other is, correct me if i'm wrong, purely intended for casting.
Thank you. Amazing nodes 💯