Bump Height Confusion Tweet

[Andreas_Resch]

While with the implementation of the Bump Height parameter, the bump map scaling issue was solved, the parameter itself creates some new questions. Maybe the devs can clear the math up a bit for us so we can decide how to best set the parameters.

Somehow the Bump Height parameter seems to influence the crispness of the input texture. This is both visible in procedural textures as well as image-based ones. Below are two examples. One of a Noise texture used as a bump map and one using an image texture. On the left, the Bump Height value is set to "0.001" and the Multiply node before the Bump input socket is set to 10. On the right, the Bump Height value is set to "0.01" (10x the value as the other material) while there's no Multiply node used here. As you can see, the bump effects on the multiplied textures are much more detailed. So a bit of insight would be nice here.

[linograndiotoy]

Yeah, in theory the two versions should look the same.

I'll check this in Standalone.

[linograndiotoy]

By the way, I've tested it in Blender and it works as it should considering what could be a real project situation, with the same material applied to scaled and not scaled meshes. Maybe the math behind this function somehow works differently than what we may think.

Please check those 2 scenes:

Bump.blend

(1.11 MiB) Downloaded 30 times

Bump1.blend

(1.11 MiB) Downloaded 35 times

[Andreas_Resch]

Not sure what I'm supposed to check here. That's a different issue. But it looks as if scaling an object scales the bump height as well. Whether that's desirable or not can be debated. As I always have my objects at scale 1, it doesn't affect me too much.