spikeyxxx Could you please explain why we need a second "Mapping Node" in order to stretch the "Volumetric Cloud" along "Local Y"? Aren't the scaling operations along the three axes independant from each other?
spikeyxxx And if it's still a sphere with one surface point at (0, 0, 7), how can this sphere intersect any axis at 1/7 ?
duerer the point (1, 0, 0) is being mapped to (7, 0, 0), but it is still called (1, 0, 0).
The distance from the Origin to the 'new' point (1, 0, 0) is 7.
The distance from the Origin to the 'new' point (1/7, 0, 0) is 1:
That is why the sphere intersects the X-axis at (1/7, 0, 0).
When we now rotate around the Y-axis by 90°, the original point (1, 0, 0) is being mapped to (0, 0, 7), but it is still called (1, 0, 0).
So the distance from the Origin to the (scaled and rotated) point (1, 0, 0) is 7.
That is why the sphere still intersects the X-axis at (1/7, 0, 0).
It is difficult to wrap your head around, I know ;)
duerer maybe this helps:
The Mapping Node (Type Point) doesn't move points, but 'maps' them to other points; meaning that when point A gets mapped to point B, it stays where it is, but gets 'all' the properties from point B (apart from Location...).
So, in our little example, point (1/7, 0, 0) gets first mapped to point (1, 0, 0), meaning it gets, amongst others, the property 'lies on a sphere with center (0, 0, 0) and radius 1'. Rotating it 90° around the Y-axis will map it to point (0, 0, 1), which happens to also have the property 'lies on a sphere with center (0, 0, 0) and radius 1'.
spikeyxxx Thanks for your patience 🙂! I think I'm getting closer to what you mean 😀. Now I have to practice a little bit 😉.
duerer with things like this, that seem hard to understand, I find it helpful to read/listen to several, different explanations and think about it a few times, until you suddenly get that 'Aha-moment' and it all becomes sooo obvious, that it is hard to remember how it was when you didn't 'get' it :-)
You don't have to thank me for my patience; as long as you don't understand my explanations, that means that I haven't explained it well enough and maybe even that I haven't understood it myself completely. In both cases, it's my rersponsibility to do something about it ;)