Just noticed my title was too long so "and probably P7)."

I may have posted this here before (possibly recently) - if so I apologise for the repeat. But I was tidying up my HD, found this, and couldn't find a corresponding thread in the Poser forum.
Rather than delete the folder containg this tut, I decided to post (possibly re-post) it..
And anyway, I had to do something whilst waiting for the forum to calm down re: P7 & V4 (neither of which I can afford..) - I can't even afford 1 month's DAZ PC  membership.

Anyhow...

Some time ago in a thread not far from here, someone wanted to know how to tile a bitmap. At the time, I made some suggestions, but nothing was ever much resolved.

The problem is, that when you apply a texture to a tile, it expands to include the whole surface, so each tile gets a part of the image. (See attached image).

Now, that could be useful, but what if you want the same image on each tile?
In that case you have to do a little manipulation.

Before I continue - this tut assumes that the tiles are square and that the texture to be applied to each tile is also square. If that's not the case, be prepared to do some advanced math calculations to work out exactly how to match them..

And also, kudos to ktn3d for supplying the (free) textures I've used....

To get the textures to match the tiles, all that is needed is to match the size of the tile with the U & V scale of the Image Map (make sure that "Image Mapped" is set to "Tile" - the default). You will lose a little of the texture due to the tile node's mortar, but in most cases this shouldn't be noticable.

(Don't forget to click on the images to get a bigger view..)

A further example, this time with two image maps. I've changed the scaling of the tiles, and done the same for the U/V scales of both image maps.

And finally, a render....:-))

Cheers,
Diolma

I remember that thread. I think it's a good thing to repost this. There are many new users, especially after the P5 give away.

Thanks for the refresher.

Remember that you can set the Mortar_Width to zero, and put the mortar on the texturemaps. Not much point in doing that here, but it means you could then do larger tile-node tiles with a more complicated tesselation in the texturemap. How about no edge-mortar in the textures, zero mortar-width, the the two sorts of tiles using the same tile-colours but diagonal mortar? Though that sort of diagonal gridding could be done without a tile node or a texture. I suspect the tile-node is a pre-built version of what can be done with a whole shder-tree. Possibly an XOR on two bar patterns which feeds a blender node? Sorry, I'm going into my weird shader-trees mode, but you can get something like XOR out of a black-and-white input set with math nodes. AND is a simple multiply. NOT is subtracting the value from 1 OR would be an addition followed by clipping (Ceiling function?). I know. I'm a freak.

Diolma said,
"Some time ago in a thread not far from here, someone ...".--- Hee Hee:-)

nice mini tut, thanks very much i will bookmark it.