db&w documentation wiki

finest software | finest docs

Site Tools


infinimap2018:procedural

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
private:infinimap2017:procedural [2017/05/10 11:47] lightwolfinfinimap2018:procedural [2017/12/27 10:41] (current) – ↷ Links adapted because of a move operation lightwolf
Line 1: Line 1:
 ====== infiniMap Procedural Texture ====== ====== infiniMap Procedural Texture ======
-===== Editing (Colour Correction) =====+{{ infinimap2018:procedural.png?direct&400|}} 
 +The procedural texture layer uses the same controls and, additionally, includes simple colour correction.
  
 +Except for some special cases we recommend using the Node instead of the Procedural Texture. Due to SDK limitations, the node is more accurate when mapping and allows you to access UV maps.
 +
 +Unfortunately the SDK provided with the current releases for LightWave 3D doesn't allow procedural textures to access UV Maps.
 +
 +There are also limitations to the accuracy of the Texture Quality setting. As long as the Scale of the texture is correct and the textured object itself has not been scaled within Layout, the Quality Setting will be correct (( Well, at least very close. Unfortunately the plugin can only estimate the optimum settings. )).
 +
 +A change of the size of the object in Layout will need a readjustment of the Texture Quality setting. The Quality has to be set to roughly the square of  the scale factor of the mesh multiplied by 100 to get the percentage. For example, if the object has been scaled to <5.0, 5.0, 5.0> the Texture Quality should be 2500% ( 5 x 5 x 100).
 +
 +As a rule of thumb, do not scale an object in Layout that has the infiniMap texture layer applied to its surface.
 +
 +===== Return Value =====
 +
 +This option is only available on the procedural texture if the texture is applied to a colour texture layer (i.e. The texture layers that modify the colour of a surface).
 +
 +It basically sends the image data differently to LightWave so the result can be used as the source value in a gradient. You should not have to activate it unless the infiniMap layer does not behave as expected in conjunction with other layers.
 +
 +If you activate “Return Value” you will be able to enter a colour or percentage (depending on the texture layer type), just as you can with any other procedural texture.
 +
 +Please note that toggling “Return Value” does not immediately update the user interface. You will need to select another layer and then select infiniMap again for the user interface change to show.
 +===== Editing (Colour Correction) =====
 +{{ infinimap2018:simplecc.png?direct|}}
 The Editing options allow for simple, on the fly colour correction that is applied to the infiniMap image while rendering. The Editing options allow for simple, on the fly colour correction that is applied to the infiniMap image while rendering.
 +
 The settings are similar to the ones supplied by LightWave 3D in the images panel. The settings are similar to the ones supplied by LightWave 3D in the images panel.
 ==== Brightness ==== ==== Brightness ====
Line 13: Line 36:
  
 The Hue setting changes the Hue of the image, basically cycling the colours through the colour spectrum. It is measured in degrees. 0° is the default. A setting of 360° degree is a full circle and the same as 0°. The Hue setting changes the Hue of the image, basically cycling the colours through the colour spectrum. It is measured in degrees. 0° is the default. A setting of 360° degree is a full circle and the same as 0°.
-Saturation+==== Saturation ==== 
 This changes the saturation of the image. 100% is the default value, at 0% the image will be greyscale only. This changes the saturation of the image. 100% is the default value, at 0% the image will be greyscale only.
 ==== Gamma ==== ==== Gamma ====
infinimap2018/procedural.1494409657.txt.gz · Last modified: 2017/05/10 11:47 by lightwolf