- An error occurred while fetching this feed: http://www.db-w.com/index.php?format=feed&type=atom
The node places one image within a 0..1 range of UV values, similar to UDIM tiles.
This node requires a projection node to be connected to the projection input.
The three controls define how the texture is composited. They are identical to the controls found in the native texturing nodes.
This control displays a list of all images used by the node. The top most images has the lowest index (0).
The images should have embedded alpha if required, ideally their RGB should be pre-multiplied by alpha.
Selecting an image will display it in the preview control.
All other interactions are via two pop-up menus. One is launched by double clicking on an image entry, the other by right clicking anywhere on the control:
This allows you to change the select image to another loaded image, load a new image and select it or change it to (none) - which will treat the list entry as being black with no alpha when rendering.
This menu can be launch by right clicking anywhere on the list control. Some of the options will only be available if an image is selected in the list.
If an image is selected - and isn't the first image in the list already - it will move up by one entry in the list.
If an image is selected - and isn't the last image in the list already - it will move down by one entry in the list.
This will add a new image to the list. If an image is selected, the new image will be added below the selected image, otherwise at the end of the list.
This allows the user to load multiple images from disk. These will be added below the currently selected image or at the end of the list.
Images that are loaded into LightWave 3D already will not be loaded again.
This removes the currently selected image from the list.
This clears the list of images.
The node places one image within a 0..1 range of UV values, similar to UDIM tiles. Normally, it also only checks for images within the current tile to see if it has to be placed and rendered or not. Overlap extends the “search” area. If you notice images being cut off, increase this value.
Higher values will lead to much longer rendering times. Anything above a value of 5 or so will be extremely slow.
Basically: If images are cut off at their border, increase this value. Otherwise: Don't. ;)
This defines which image width in Pixels should be considered as being the width of a UV tile at a scale of 100%. If this values is not 0, the the images will also be mapped in a proportional size to each other. If this settings is 0, every image will be as large as the corresponding UV tile at a scale of 100%.
These controls correspond to the identical controls in the native image sampler or image texturing nodes.
The strength of the bump mapping.
For example, if you're texturing instances and would like each of them to have a different distribution, you could use the instance ID as a random seed using the nodal input.
This doesn't do anything at the moment. Eventually it will replace the *Random Seed* with a new random number.
The randomness of the placement of the images as well as their rotation, scale, etc. is based on a noise function. This setting changes the scale of that noise. Larger values make it more chaotic, smaller values less so, which will lead to images next to each other using more similar settings.
The probability a bitmap will show up.
The randomness of the variation in the Probability.
The scale of the Variation randomness.
This controls how much the position of every image may deviate from the middle of the UV tile, on the horizontal ( X ) as well as the vertical (Y) axis. 0 will always place the image at the centre, 0.5 allows it to be placed anywhere from -0.5 to 0.5 from the centre (which covers the whole UV tile).
This rotates all placed images. If Randomize is active, it's the minimum rotation.
Enabling this allows for randomized rotations.
This is the maximum rotation if Randomize is enabled. The random rotations will be in the range from Base to this value.
A value larger than 1 will only allow for random rotations in discreet steps.
For example, if Base is 0°, Max is 360° and Steps is 4, the result of the random rotation will be 0°, 90°, 180° or 270°.
This scales all placed images. If Randomize is active, it's the minimum scale.
Enabling this allows for randomized scale.
This is the maximum scale if Randomize is enabled. The random scale will be in the range from Base to this value.
This tab allows you to modify the Hue, Saturation and Value (Brightness) of the placed image.
This changes the colour of all placed images. If Randomize is active, it's the minimum HSV value.
Enabling this allows for randomized HSV variations.
This is the maximum HSV value if Randomize is enabled. The random colouring will be in the range from Base to this value.
This changes the transparency of all placed images. If Randomize is active, it's the minimum transparency.
Enabling this allows for randomized transparency.
This is the maximum transparency value if Randomize is enabled. The random transparency will be in the range from Base to this value.
The inputs correspond to the controls with the same name. Please remember that the inputs change the values per (surface) spot that is evaluated.
This is the final composite of the random images over the background colour.
This is just the colour of the random images. If no image is visible at a spot, it will be black.
This is the luminosity of the RGB output.
The transparency of the random images, taking their respective alpha channels into account.
A bump map computed from the luminosity of the images.
This is a random value between black and white (0 .. 1.0) for each tile, taking the alpha channel of the mapped images into account.
This is the plugin of the month for February 2019, made possible by the finest patrons on Patreon.