DILATE/ERODE should have a Value input on the Distance slider
DILATE/ERODE should have a Value input on the Distance slider At the moment its impossible to work with it in a node group since you have to open the group edit it and close it , and there is no way to have it outside the nodegroup because it would create a node loop , so yeah it just needs a way to connect teh DISTANCE to the Group Input
below how it is right now
6 Comments
YES expose all parameters on the Dilate/Erode node. Why are most node settings impossible to expose? That makes compositing LESS procedural. I often run into this while using the compositor.
Also, DID YOU KNOW this node is perfect for generating Photoshop like drop-shadows and glow effects? The issue is that even if you made an elegant group node to combine this with other nodes to make the final effect, you'd have to go INSIDE the group JUST to effect the size and spread which would then effect all other drop shadow effects, thus defeating the effectiveness of a group node. This is another point to add to what the OP was saying about input parameters being necessary.
How would that work? Since distance could be a pixel value or a percentage—and a scalar value at that—it doesn't make sense for it to have an arbitrary value socket.
What you're really looking for is a way to expose internal values on a group node. That's been proposed here a few times already... but making the Distance parameter a value socket isn't really the right answer.
* @Jason van Gumster * Hey thanks for the answer! yes what i meant was exactly that , make it useable from outside the NODE GROUP so i can just change the Distance value without opening the node group
cheers :)
* @Jason van Gumster * The "Rotation" node already accepts an input for a scalar value, despite not working on a per-pixel basis, so there's precedent. I think it just averages or sample a single pixel or something to get the angle. Plus the "Math" and "Value" nodes are obviously already able to effectively function as scalar operations. Or "Dilate/Erode" could just skip pixels as it already seems to work on an iterative per-pixel basis.
With a few greater than and mix nodes, you can make a custom node that acts like a Dilate/Erode node, but with a distance slider. Tutorial here: youtube.com/watch
Btw, generally the work around for this kind of issue is to use a driver, however, the user must set this up again every time it's appended to another blend file.