Here’s the old mapping node:
Here’s the current (2.83) mapping node:
This is substantially different: the additional inputs and the lack of the MIN/MAX functions.
I’m following this tutorial (watch at 0.25X speeds for convenience):
And wondering which inputs to use, and what to do about the lack of MIN/MAX functions.
Secrop
(Secrop)
June 14, 2020, 8:38am
2
The inputs are vectors with the 3 components for your Location , Rotation and Scale . No change at all, in this matter, except for the fact that your values can now originate outside the mapping node.
The Min/Max functions were removed from the Mapping node, but they are now in the VectorMath node. All you need is to clamp the Mapping node output with the Minimum and Maximum operations, to get the same result.
1 Like
Secrop:
The inputs are vectors with the 3 components for your Location , Rotation and Scale . No change at all, in this matter, except for the fact that your values can now originate outside the mapping node.
So, and specifically for the tutorial in question, just continue to use the Vector input and ignore the others?
Secrop:
The Min/Max functions were removed from the Mapping node, but they are now in the VectorMath node. All you need is to clamp the Mapping node output with the Minimum and Maximum operations, to get the same result.
So, you need to use TWO (?) Vector Math nodes between the Mapping node and the Image node? Because it looks like it only does one operation at a time.
Secrop
(Secrop)
June 14, 2020, 4:51pm
4
The same happens in 2.79. Just because the operations are performed internally, it doesn’t mean that they are done simultaneously!
Here’s a similar setup that i use often (the empty’s Z is aligned to the surface’s normal):