@Benjamin Bass It is currently still in heavy development and meant to eventually replace the old vertex color painting system. There are some features that the new system is missing still to be up t par, that's why they still both exist next to each other. But as soon as those are there it will be all-around better than the old system.

*@Huân Lê-Vương* Can you give me a timestamp in the video, so I know where to look?

*@Simon Thommes* 5:59 and 10:52

*@Huân Lê-Vương* Ah, I see what you mean now. Yes, that seems reasonable to do!

*@Simon Thommes* I also use MixRGB instead of maximum/minimum so I can use less a node at the dispacement part from 18:47 to 25:35

My file: https://drive.google.com/file/d/1YEBmfHHtgDJXr9ngVLprEMCKAIuFcHqi/view?usp=sharing

then the diplacement just doesn't work properly. don't know how. i should go back to your method.

*@Huân Lê-Vương* You can also use Mix nodes with a greater/less than mask, but then you have to make sure to mix between exactly the same maps you used for the mask as well.

About the node-count: Using fewer nodes is not always better. Even for performance it matters more which nodes you use than how many.

*@Simon Thommes* thanks!

*@Simon Thommes* ah, actually I plugged the bolt's Map Range (24:10) to the "To Max" value of the horizomtal Map Range instead of using a Minimum node. I thought it only worked with MixRGB but it also works with Maximum too.

*@Aron* What you can see there is just the displacement of the shader not having enough geometry to work with. If you enable the subdivision modifier for viewport display you can see how it comes together with more geometry. You are on the right track :)

Also setting the shading to smooth will help a bit.

*@Simon Thommes* Thanks to replying my question, it's work!

*@kroneborge* You can also do that. The only difference I see right now is that the way I set it up the transparency is not affected by the backface-culling. I think that was the reason I did it this way.

Here it does not really matter but if you wanted light to be able to go through the gaps to the outside, you would have to set it up this way.

*@victor p* I would get more membership time for his courses

*@Gary* when we use the maximum, we take in account the high value of the both functions without changing the value as the space where they overlapping each other.

now for example, we have a plane of value from 0 to 10. we add a map range node and turn off the clamp.

we can use from min = 0, from max = 10. then to min = 0, to max = 10. it's from (0 to 10) to (0 to 10), the value remains the same, and that makes sense, right?

now use to max = 1, now it's from (0 to 10) to (0 to 1). still makes sense, right?

so for every steps of (0 to 10) will be scaled to ("to min" to "to max"). for the value that goes from 0 to 10, there is only 1 (0 to 10) step.

now with from min = 0, from max = 1, we use the step of (0 to 1) for our value. for the value of 0 to 10, we have 10 steps of (0 to 1). and every of them will be scaled the range of ("to min" to "to max").

for example, from min = 0, from max = 1, to min = -3, to max = -1. so the first step will be -3 to -1. the 2nd is will continue from -1 to 1 and goes on.

to know how the "clamp" work, you should take a value from Geometry>Position coordinates and scale the mesh bigger, then turning on/off the clamp. The bigger the mesh, the more position value it covers. turning on clamp will stop the value at the to min to max.

@Michael Schwarz Your RGB Curves node for the horizontal bars has a point in (0,0). This prevents it from going far into the negative and because of that the clipping does not make much of a difference. You can just remove that point in the Curves node and it should be fine.

@Simon Thommes sorry, but I can't see that point and neither I could delete it. I played around with the RGB curves a bit and actually I came sometimes to a point where ir worked as it should but I was not able to reproduce this. Please have a look at this commented screenshot and please advice how to find and delete that point in 0,0. File: https://1drv.ms/u/s%21AkArx_WkEuwAhY0NrL-HyYnbhyEMXw?e=bsZRRa

@Simon Thommes OK. I think I've got. I have to reset the curve and then set the 3 points again. My question is: how have seen that there was a point in 0,0 ? Or was that just an assumption concluded from the behaviour?

@Michael Schwarz It was an assumption, but I can simply select it by clicking in the general area in the file that you provided. Maybe you have to reset the view of the curve, if you zoomed in and can not see it because of that.

@Simon Thommes Oh. I see. Thanks!

@Emmanuel I just went further in the tutorial, and I understood why. His mesh was already subdivided in addition of the modifier.

@Itay Sharon Correction:

X = ((Object's X scale) * ((Frequency of bars horizontal) / (Frequency of bars vertical))) * 2 Or more simply: (Scale.X * (H / V)) * 2