Reference:Pigment Map - Revision history

Jholsenback: corrections

2017-07-24T10:44:09Z

corrections

Jholsenback: clarification and clean up

2017-07-23T14:13:38Z

clarification and clean up

Jholsenback: version changes

2017-06-26T10:17:01Z

version changes

Jholsenback: link repair

2016-12-11T16:48:15Z

link repair

Jholsenback: documenting map entry restriction change

2016-11-20T23:20:07Z

documenting map entry restriction change

Jholsenback: cleanup and blend mode / gamma additions

2016-11-19T13:54:09Z

cleanup and blend mode / gamma additions

Jholsenback: 1 revision: link repair

2012-07-23T19:27:57Z

1 revision: link repair

Jholsenback: link repair

2012-07-20T19:36:19Z

link repair

Jholsenback: 1 revision: Reference Migration Initial Load

2012-03-15T19:07:44Z

1 revision: Reference Migration Initial Load

Jholsenback: 1 revision: Initial Load (TF)

2012-03-11T22:27:48Z

1 revision: Initial Load (TF)

New page

{{#indexentry:pigments, pigment list}}
{{#indexentry:pigment_map}}
In addition to specifying blended colors with a color map you may create a blend of pigments using a <code>pigment_map</code>. The syntax for a pigment map is identical to a color map except you specify a pigment in each map
entry (and not a color).
The syntax for <code>pigment_map</code> is as follows:
<pre>
PIGMENT_MAP:
pigment_map { PIGMENT_MAP_BODY }
PIGMENT_MAP_BODY:
PIGMENT_MAP_IDENTIFIER | PIGMENT_MAP_ENTRY...
PIGMENT_MAP_ENTRY:
[ Value PIGMENT_BODY ]
</pre>
Where <code>Value</code> is a float value between 0.0 and 1.0 inclusive and each PIGMENT_BODY is anything which can be inside a <code>pigment{...}</code> statement. The <code>pigment</code> keyword and
<code>{}</code> braces need not be specified.
Note: The <code>[]</code> brackets are part of the actual PIGMENT_MAP_ENTRY. They are not notational symbols denoting optional parts. The brackets surround each entry in the pigment map.
There may be from 2 to 256 entries in the map.
For example:
<pre>
sphere {
<0,1,2>, 2
pigment {
gradient x //this is the PATTERN_TYPE
pigment_map {
[0.3 wood scale 0.2]
[0.3 Jade] //this is a pigment identifier
[0.6 Jade]
[0.9 marble turbulence 1]
}
}
}
</pre>
When the <code>gradient x</code> function returns values from 0.0 to 0.3 the scaled wood pigment is used. From 0.3 to 0.6 the pigment identifier Jade is used. From 0.6 up to 0.9 a blend of Jade and a turbulent marble is used. From 0.9 on up only the turbulent marble is used.
Pigment maps may be nested to any level of complexity you desire. The pigments in a map may have color maps or pigment maps or any type of pigment you want. Any entry of a pigment map may be a solid color however if all entries are solid colors you should use a <code>color_map</code> which will render slightly faster.
Entire pigments may also be used with the block patterns such as <code>checker</code>, <code>hexagon</code> and <code>brick</code>. For example:
<pre>
pigment {
checker
pigment { Jade scale .8 }
pigment { White_Marble scale .5 }
}
</pre>
Note: In the case of block patterns the <code>pigment</code> wrapping is required around the pigment information.
A pigment map is also used with the <code>average</code> pigment type. See
[[Reference:Average Pattern|:Average|Average]] for details.
You may not use <code>pigment_map</code> or individual pigments with an <code>image_map</code>. See section [[Reference:Patterned_Textures#Texture_Maps|Texture Maps]] for an alternative way to do this.
You may declare and use pigment map identifiers but the only way to declare a pigment block pattern list is to declare a pigment identifier for the entire pigment.

@@ Line 9: / Line 9: @@
 <pre>
 PIGMENT_MAP:
-   pigment_map { [blend_mode [BLEND_MODE]] [blend_gamma [FLOAT]] | PIGMENT_MAP_BODY }
+   pigment_map { PIGMENT_MAP_BODY }
 BLEND_MODE:
-   [0] | 1 | 2 | 3
+| 1 | 2 | 3
 PIGMENT_MAP_ENTRY:
-   [Value PIGMENT_BODY]
+   [ Value PIGMENT_BODY ]
 </pre>

@@ Line 9: / Line 9: @@
 <pre>
 PIGMENT_MAP:
-   pigment_map { PIGMENT_MAP_BODY }
+   pigment_map { [blend_mode [BLEND_MODE]] [blend_gamma [FLOAT]] | PIGMENT_MAP_BODY }
 BLEND_MODE:
    [0] | 1 | 2 | 3
 PIGMENT_MAP_ENTRY:
    [Value PIGMENT_BODY]
@@ Line 19: / Line 19: @@
 <p>Where <em><code>Value</code></em> is a float value between 0.0 and 1.0 inclusive and each <em>PIGMENT_BODY</em> is anything which can be inside a <code>pigment{...}</code> statement. The <code>pigment</code> keyword and <code>{}</code> braces need not be specified.</p>
 <p class="Note"><strong>Note:</strong> The <code>[]</code> brackets that are part of the actual <em>PIGMENT_MAP_ENTRY</em> should not confused with the symbols denoting optional syntax.</p>
@@ Line 24: / Line 32: @@
 <p>In <em>previous</em> versions there <em>had</em> to be from 2 to 256 entries in the map. A {{Change}} in version 3.8 has removed the upper restriction.</p>
-<p>Here's an example:</p>
+<p>Here's a simple example:</p>
 <pre>
@@ Line 63: / Line 71: @@
 <p>You may declare and use pigment map identifiers but the only way to declare a pigment block pattern list is to declare a pigment identifier for the entire pigment.</p>
-<p>The possible values for <code>blend_mode</code> and their descriptions are as follows:</p>
+<p>See also: [[Reference:Color Map|Color Maps]].</p>

@@ Line 4: / Line 4: @@
 {{#indexentry:blend_gamma}}
 <p>In addition to specifying blended colors with a color map you may create a blend of pigments using a  <code>pigment_map</code>. The syntax for a pigment map is identical to a color map except you specify a pigment in each map
-entry and not a color. {{New}} in version 3.7.1 non-linear pigment map interpolation support has been added.</p>
+entry and not a color. {{New}} in version 3.8 non-linear pigment map interpolation support has been added.</p>
 <p>The syntax for <code>pigment_map</code> is as follows:</p>
@@ Line 22: / Line 22: @@
 <p class="Note"><strong>Note:</strong> The <code>[]</code> brackets that are part of the actual <em>PIGMENT_MAP_ENTRY</em> should not confused with the symbols denoting optional syntax.</p>
-<p>In <em>previous</em> versions there <em>had</em> to be from 2 to 256 entries in the map. A {{Change}} in version 3.7.1 has removed the upper restriction.</p>
+<p>In <em>previous</em> versions there <em>had</em> to be from 2 to 256 entries in the map. A {{Change}} in version 3.8 has removed the upper restriction.</p>
 <p>Here's an example:</p>

← Older revision		Revision as of 16:48, 11 December 2016
Line 71:		Line 71:
	</ul>		</ul>

−	<p>[[Reference:~~Color_Map~~\|Color Maps]] also support the {{New}} non-linear interpolation scheme.</p>	+	<p>[[Reference:Color Map\|Color Maps]] also support the {{New}} non-linear interpolation scheme.</p>

@@ Line 22: / Line 22: @@
 <p class="Note"><strong>Note:</strong> The <code>[]</code> brackets that are part of the actual <em>PIGMENT_MAP_ENTRY</em> should not confused with the symbols denoting optional syntax.</p>
-<p>There may be from 2 to 256 entries in the map.</p>
+<p>In <em>previous</em> versions there <em>had</em> to be from 2 to 256 entries in the map. A {{Change}} in version 3.7.1 has removed the upper restriction.</p>
 <p>Here's an example:</p>

@@ Line 1: / Line 1: @@
 {{#indexentry:pigments, pigment list}}
 {{#indexentry:pigment_map}}
 <p>In addition to specifying blended colors with a color map you may create a blend of pigments using a  <code>pigment_map</code>. The syntax for a pigment map is identical to a color map except you specify a pigment in each map
-entry (and not a color).</p>
+entry and not a color. {{New}} in version 3.7.1 non-linear pigment map interpolation support has been added.</p>
 <p>The syntax for <code>pigment_map</code> is as follows:</p>
 <pre>
@@ Line 8: / Line 11: @@
    pigment_map { PIGMENT_MAP_BODY }
 PIGMENT_MAP_BODY:
-   PIGMENT_MAP_IDENTIFIER | PIGMENT_MAP_ENTRY...
+   PIGMENT_MAP_IDENTIFIER | [blend_mode [BLEND_MODE]] [blend_gamma [FLOAT]] | PIGMENT_MAP_ENTRY...
 PIGMENT_MAP_ENTRY:
-   [ Value PIGMENT_BODY ]
+   [Value PIGMENT_BODY]
 </pre>
 <p>Where <em><code>Value</code></em> is a float value between 0.0 and 1.0 inclusive and each <em>PIGMENT_BODY</em> is anything which can be inside a <code>pigment{...}</code> statement. The <code>pigment</code> keyword and
-<code>{}</code> braces need not be specified.</p>
+<p>Where <em><code>Value</code></em> is a float value between 0.0 and 1.0 inclusive and each <em>PIGMENT_BODY</em> is anything which can be inside a <code>pigment{...}</code> statement. The <code>pigment</code> keyword and <code>{}</code> braces need not be specified.</p>
-<p class="Note"><strong>Note:</strong> The <code>[]</code> brackets are part of the actual <em>PIGMENT_MAP_ENTRY</em>. They are not notational symbols denoting optional parts. The brackets surround each entry in the pigment map.</p>
 <p>There may be from 2 to 256 entries in the map.</p>
-<p>For example:</p>
 <pre>
 sphere {
@@ Line 31: / Line 40: @@
+   }
 </pre>
 <p>When the <code>gradient x</code> function returns values from 0.0 to 0.3 the scaled wood pigment is used. From 0.3 to 0.6 the pigment identifier Jade is used. From 0.6 up to 0.9 a blend of Jade and a turbulent marble is used. From 0.9 on up only the turbulent marble is used.</p>
 <p>Pigment maps may be nested to any level of complexity you desire. The pigments in a map may have color maps or pigment maps or any type of pigment you want. Any entry of a pigment map may be a solid color however if all entries are solid colors you should use a <code>color_map</code> which will render slightly faster.</p>
-<p>Entire pigments may also be used with the block patterns such as <code>checker</code>, <code>hexagon</code> and <code>brick</code>. For example:</p>
 <pre>
 pigment {
@@ Line 41: / Line 54: @@
+     }
 </pre>
 <p class="Note"><strong>Note:</strong> In the case of block patterns the <code>pigment</code> wrapping is required around the pigment information.</p>
 <p>A pigment map is also used with the <code>average</code> pigment type. See
-[[Reference:Average Pattern|:Average|Average]] for details.</p>
+<p>A pigment map is also used with the <code>average</code> pigment type. See [[Reference:Average Pattern|:Average|Average]] for details.</p>
 <p>You may not use <code>pigment_map</code> or individual pigments with an <code>image_map</code>. See section <!--<linkto "Texture Maps">Texture Maps</linkto>--->[[Reference:Patterned Textures#Texture Maps|Texture Maps]] for an alternative way to do this.</p>
 <p>You may declare and use pigment map identifiers but the only way to declare a pigment block pattern list is to declare a pigment identifier for the entire pigment.</p>

← Older revision	Revision as of 19:27, 23 July 2012
(No difference)

← Older revision	Revision as of 19:07, 15 March 2012
(No difference)