|
|
My suggestion is, to make a small change on the BRICKS pattern to allow
- when stated inside a TEXTURE block - to accept textures and not only
pigments.
This would make it very easy to use the BRICKS pattern to generate
wooden planks for decks and floors. In fact, not only wooden planks are
then possible, but any texture, like stones, glasses, and so on.
It could be this way:
texture
{
brick // this pattern is just ideal for planks
MyWoodTexture
MyTarInbetweenTexture
brick_size < 5.00, 0.02, 0.40 > // that equals now to plank size
mortar 0.01 scale 3.0 // thickness of the material between planks
}
------------------------------------
Also wondering if there is a way to "remote-control" textures from the
outside with parameters, similar to how MACRO allows to manipulate an
object from the outside with parameters. This could save us of having to
re-declare entire textures. With parameters, I could decide (for the
above example) which wood texture I want to use.
---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com
Post a reply to this message
|
|
|
|
On 04/04/2018 08:28 AM, Sven Littkowski wrote:
> texture
> {
> brick // this pattern is just ideal for planks
> MyWoodTexture
> MyTarInbetweenTexture
> brick_size < 5.00, 0.02, 0.40 > // that equals now to plank size
> mortar 0.01 scale 3.0 // thickness of the material between planks
>
> }
Pretty sure if you add texture block wrappers around your predefined
textures what you wrote today will work. As in:
texture
{
brick
texture { MyWoodTexture }
texture { MyTarInbetweenTexture }
brick_size < 5.00, 0.02, 0.40 >
mortar 0.01 scale 3.0
}
Block pattern texture lists need the texture block indicators. There are
too pavement and tiling patterns. As for your second idea I believe
macros is the only way today.
Bill P.
Post a reply to this message
|
|