Make muted nodes not affect values
A muted node that has a different socket type from input to output will change value types despite being muted. This is apparently intentional , although I fail to see why anyone would want this.
Consider the case of the "Float to Integer" node, set to Truncate:
Because truncating is the default conversion from float to int, whether this node is active or muted makes no difference. In this case the geometry will still not move to 0.99.
I think muted nodes should let values pass through unchanged.
While the node's appearance properly reflects the current behavior, it could easily be changed to reflect the proposed one, by leaving the line color unchanged and making the sockets semi-transparent like the rest of the node:
1 Comment
It makes no sense that the output of a muted node is still actively modifying the input result.
If the downstream connection is not compatible with the output further up the chain (due to the mute), then at the very least the entire downstream connections should turn red to indicate that the result cannot be properly evaluated.