scaling down geometry with the copy node feels a bit weird: with 'scale' node I would set scale to 50 and get a half sized object, with copy node that needs to be -0.5 to get the same results, I'm sure there is some good logic behind this, that's why I ask.. thanks!
The new NodeBox forum is live! Everything from support.nodebox.net moved here: sign in with the same email to pick up your old posts. Something not working? Write to forum-support@nodebox.net.
General DiscussionFrom the old forum
Copy node scaling question
-
-
NodeBox team You're right this is an inconsistency in NodeBox.
The copy node uses the actual scaling values, which is that 2 means 200%. The scale uses something akin to percentages and divides by 100 internally.
I prefer the approach of the scale node since dragging values is easier there. I've added a GitHub issue that tracks this.