+1
Planned

Component mask per node

msperling 10 years ago updated by Freya Holmér (Developer) 10 years ago 0
Hi Joachim,
have you thought about adding component masks directly to each and every node?
That way we could more easily pick the XYZW-components of say an arithmetic operation. And we wouldn't need to plug a component mask after that operation.
The same could be useful for vector nodes as well.
And while we are at it - adding input nodes (aka input component masks) to a vector node would make the creation of temporary vector variables a breeze.
Append or Swizzle nodes may be rendered useless by this feature. Not sure.
In the end it all would boil down to how the Texture2D node works, currently.

This would reduce the node tree size inside the editor alot I guess.

Answer

Answer
Planned
Good idea!
I thought of it, but was concerned that it may look too cluttered with too many colored RGB outputs everywhere, but, I think it can be solved by making them show up when the cursor is near or while connected :)
Answer
Planned
Good idea!
I thought of it, but was concerned that it may look too cluttered with too many colored RGB outputs everywhere, but, I think it can be solved by making them show up when the cursor is near or while connected :)