0
$\begingroup$

The standard Brick Texture node doesn't have an input socket for the offset.

I found a solution here.

However, when I change the row height of the bricks in that setup, everything gets messed up.

How can I modify the setup so that I can still adjust all the other parameters of the Brick Texture?

Blender file in attachment here:

node setup

the problem

$\endgroup$

1 Answer 1

1
$\begingroup$

It is not only the Row Height which makes problems in this setup. If you change the Brick Width, the Offset will be broken too.

In the following example I have changed the Brick Width to 0.7, while the Offset is at 0.5 which should result in the alternating rows being offset half of the width - but they are not:

broken width setting

So as you see, the Row Height setting can not be used as you already discovered and the same goes for the Brick Width. The issue is caused by the fact that the mathematical operations there use fixed values in some parts which should actually be relative to Brick Width and Row Height:

relative values

Instead of leaving the fixed values there you could now add two Value nodes to the shader: one for the Row Height and one for the Brick Width.

The Row Height value needs to be multiplied by 2 for the first unused input socket in the upper Divide node, then you can plug it directly into the next unused socket in the other Divide node and into the Brick Texture's Row Height input. The other Value node you plug into the last unused input socket in the Multiply node and into the Brick Width input of the Brick Texture. Now you can change Brick Width and Row Height with those values.

improved nodetree

The whole nodetree setup seems very slow to me. Probably there are ways to build this more efficient by using a completely different method, but I was just focusing on repairing the issue in this specific setup. Here is the file with the modified nodetree:

$\endgroup$
1
  • $\begingroup$ Wow, thank you very much! This works. :-) I can see that it is a bit slower then the regular brick texture, but for me it reacts quite fast still. I wish there was a way to test the speed of a node setup in the shader nodes. $\endgroup$ Commented Oct 15 at 12:42

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .