Reference:Bump Map - Revision history

Jr: fix wording

2025-05-09T11:12:50Z

fix wording

Jholsenback: clarification

2018-02-06T11:40:43Z

clarification

Jholsenback: consistency

2018-02-04T19:29:00Z

consistency

Jholsenback: version changes

2017-06-26T10:29:56Z

version changes

Clipka: Indexentries fix

2016-12-17T01:09:06Z

Indexentries fix

Jholsenback: indexentry additions

2016-10-13T10:49:07Z

indexentry additions

Jholsenback: 3.7.1 updates

2016-10-13T09:35:49Z

3.7.1 updates

Clipka: indexentry fix

2016-05-03T23:03:29Z

indexentry fix

Chrisc: Indexentry fix

2013-02-11T05:48:11Z

Indexentry fix

Jholsenback: 1 revision: Reference Migration Initial Load

2012-03-15T19:05:09Z

1 revision: Reference Migration Initial Load

@@ Line 29: / Line 29: @@
 <p>By default, the bump pattern is mapped onto the x-y-plane. The bump pattern is <em>projected</em> onto the object as though there were a slide projector somewhere in the -z-direction. The pattern exactly fills the square area from (x,y) coordinates (0,0) to (1,1) regardless of the pattern's original size in pixels. If you would like to change this default you may translate, rotate or scale the pigment or texture to map it onto the object's surface as desired. If you would like to change this default orientation you may translate, rotate or scale the pigment or texture to map it onto the object's surface as desired.</p>
 <p>
-While POV-Ray will normally interpret the bump map input file as a container of linear data irregardless of file type, this can be overridden for any individual bump map input file by specifying <code>gamma</code> GAMMA immediately after the file name. For example:</p>
+While POV-Ray will normally interpret the bump map input file as a container of linear data irrespective of file type, this can be overridden for any individual bump map input file by specifying <code>gamma</code> GAMMA immediately after the file name. For example:</p>
 <pre>
 bump_map {

@@ Line 10: / Line 10: @@
    normal {
      bump_map {
-       BITMAP_TYPE &quot;filename&quot; [gamma GAMMA] [premultiplied BOOL]
+       [BITMAP_TYPE] &quot;filename&quot; [gamma GAMMA] [premultiplied BOOL]
        [BUMP_MAP_MODs...]
+       }
@@ Line 24: / Line 24: @@
 </pre>
-<p>After the required <em>BITMAP_TYPE</em> keyword is a string expression containing the name of a bitmapped bump file of the specified type. Several optional modifiers may follow the file specification. The modifiers are described below.</p>
+<p>After the optional <em>BITMAP_TYPE</em> keyword is a string expression containing the name of a bitmapped bump file of the specified type. Several optional modifiers may follow the file specification. The modifiers are described below.</p>
 <p class="Note"><strong>Note:</strong> Earlier versions of POV-Ray allowed some modifiers before the <em>BITMAP_TYPE</em> but that syntax is being phased out in favor of the syntax described here.</p>
 <p>Filenames specified in the <code>bump_map</code> statements will be searched for in the home (current) directory first and, if not found, will then be searched for in directories specified by any <code>+L</code> or <code>Library_Path</code> options active. This would facilitate keeping all your bump maps files in a separate sub-directory and giving a <code>Library_Path</code> option to specify where your library of bump maps are. See [[Reference:Scene Parsing Options#Library Paths|:Library_Path|Library Paths]] for details.</p>

@@ Line 10: / Line 10: @@
    normal {
      bump_map {
-       BITMAP_TYPE &quot;bitmap.ext&quot; [gamma GAMMA] [premultiplied BOOL]
+       BITMAP_TYPE &quot;filename&quot; [gamma GAMMA] [premultiplied BOOL]
        [BUMP_MAP_MODs...]
+       }

@@ Line 38: / Line 38: @@
 {{#indexentry:bt2020, keyword}}
 {{#indexentry:srgb, keyword}}
-<p>This will cause POV-Ray to perform gamma adjustment or decoding on the input file data before building the bump map. Alternatively to a numerical value, <code>srgb</code> may be specified to denote that the file is pre-corrected or encoded using the <em>sRGB transfer function</em> instead of a power-law gamma function. {{New}} in version 3.7.1, other valid special values are <code>bt709</code> and <code>bt2020</code>, denoting that the file is encoded or pre-corrected using the ITU-R BT.709 or BT.2020 transfer function, respectively. See section [[Documentation:Tutorial Section 3.3#Gamma Handling|Gamma Handling]] for more details.</p>
+<p>This will cause POV-Ray to perform gamma adjustment or decoding on the input file data before building the bump map. Alternatively to a numerical value, <code>srgb</code> may be specified to denote that the file is pre-corrected or encoded using the <em>sRGB transfer function</em> instead of a power-law gamma function. {{New}} in version 3.8, other valid special values are <code>bt709</code> and <code>bt2020</code>, denoting that the file is encoded or pre-corrected using the ITU-R BT.709 or BT.2020 transfer function, respectively. See section [[Documentation:Tutorial Section 3.3#Gamma Handling|Gamma Handling]] for more details.</p>
 <p>The file name is optionally followed by one or more <em>BITMAP_MODIFIERS</em>. The <code>bump_size</code>, <code>use_color</code> and <code>use_index</code> modifiers are specific to bump maps and are discussed in the following sections. See the section <!--<linkto "Bitmap Modifiers">Bitmap Modifiers</linkto>--->[[Reference:Bitmap Modifiers|Bitmap Modifiers]] where the generic bitmap modifiers <code>map_type</code>, <code>once</code> and <code>interpolate</code> are described.</p>

@@ Line 37: / Line 37: @@
 {{#indexentry:bt709, keyword}}
 {{#indexentry:bt2020, keyword}}
 <p>This will cause POV-Ray to perform gamma adjustment or decoding on the input file data before building the bump map. Alternatively to a numerical value, <code>srgb</code> may be specified to denote that the file is pre-corrected or encoded using the <em>sRGB transfer function</em> instead of a power-law gamma function. {{New}} in version 3.7.1, other valid special values are <code>bt709</code> and <code>bt2020</code>, denoting that the file is encoded or pre-corrected using the ITU-R BT.709 or BT.2020 transfer function, respectively. See section [[Documentation:Tutorial Section 3.3#Gamma Handling|Gamma Handling]] for more details.</p>
 <p>The file name is optionally followed by one or more <em>BITMAP_MODIFIERS</em>. The <code>bump_size</code>, <code>use_color</code> and <code>use_index</code> modifiers are specific to bump maps and are discussed in the following sections. See the section <!--<linkto "Bitmap Modifiers">Bitmap Modifiers</linkto>--->[[Reference:Bitmap Modifiers|Bitmap Modifiers]] where the generic bitmap modifiers <code>map_type</code>, <code>once</code> and <code>interpolate</code> are described.</p>
 ==Bump_Size==
 <p>The relative bump size can be scaled using the <code>bump_size</code> modifier. The bump size number can be any number other than 0 but typical values are from about 0.1 to as high as 4.0 or 5.0.</p>
 <pre>
@@ Line 59: / Line 60: @@
 </pre>
 {{#indexentry:use_index}}
 {{#indexentry:use_color}}
 {{#indexentry:use_colour}}
 <p>Usually the bump map converts the color of the pixel in the map to a gray scale intensity value in the range 0.0 to 1.0 and calculates the bumps based on that value. If you specify <code>use_index</code>, the bump map uses the color's palette number to compute as the height of the bump at that point. So, color number 0 would be low and color number 255 would be high (if the image has 256 palette entries). The actual color of the pixels doesn't matter when using the index. This option is only available on
 palette based formats. The <code>use_color</code> keyword may be specified to explicitly note that the color methods should be used instead. The alternate spelling <code>use_colour</code> is also valid. These modifiers may only be used inside the <code>bump_map</code> statement.</p>

@@ Line 11: / Line 11: @@
      bump_map {
        BITMAP_TYPE &quot;bitmap.ext&quot; [gamma GAMMA] [premultiplied BOOL]
-       [BUMP_MAP_MODS...]
+       [BUMP_MAP_MODs...]
+       }
    [NORMAL_MODFIERS...]
@@ Line 17: / Line 17: @@
 BITMAP_TYPE:
    exr | gif | hdr | iff | jpeg | pgm | png | ppm | sys | tga | tiff
-BUMP_MAP_MOD:
+GAMMA:
    map_type Type | once | interpolate Type | use_color |
    use_colour | bump_size Value
@@ Line 24: / Line 26: @@
 <p>After the required <em>BITMAP_TYPE</em> keyword is a string expression containing the name of a bitmapped bump file of the specified type. Several optional modifiers may follow the file specification. The modifiers are described below.</p>
 <p class="Note"><strong>Note:</strong> Earlier versions of POV-Ray allowed some modifiers before the <em>BITMAP_TYPE</em> but that syntax is being phased out in favor of the syntax described here.</p>
-<p>Filenames specified in the <code>bump_map</code> statements will be searched for in the home (current) directory first and, if not found, will then be searched for in directories specified by any <code>+L</code> or <code>Library_Path</code> options active. This would facilitate keeping all your bump maps files in a separate subdirectory and giving a <code>Library_Path</code> option to specify where your library of bump maps are. See [[Reference:Scene Parsing Options#Library Paths|:Library_Path|Library Paths]] for details.</p>
+<p>Filenames specified in the <code>bump_map</code> statements will be searched for in the home (current) directory first and, if not found, will then be searched for in directories specified by any <code>+L</code> or <code>Library_Path</code> options active. This would facilitate keeping all your bump maps files in a separate sub-directory and giving a <code>Library_Path</code> option to specify where your library of bump maps are. See [[Reference:Scene Parsing Options#Library Paths|:Library_Path|Library Paths]] for details.</p>
 <p>By default, the bump pattern is mapped onto the x-y-plane. The bump pattern is <em>projected</em> onto the object as though there were a slide projector somewhere in the -z-direction. The pattern exactly fills the square area from (x,y) coordinates (0,0) to (1,1) regardless of the pattern's original size in pixels. If you would like to change this default you may translate, rotate or scale the pigment or texture to map it onto the object's surface as desired. If you would like to change this default orientation you may translate, rotate or scale the pigment or texture to map it onto the object's surface as desired.</p>
 <p>
@@ Line 33: / Line 35: @@
+   }
 </pre>
-<p>This will cause POV-Ray to perform gamma adjustment or -decoding on the input file data before building the bump map. Alternatively to a numerical value, <code>srgb</code> may be specified to denote that the file is pre-corrected or encoded using the <em>sRGB transfer function</em> instead of a power-law gamma function. See section [[Documentation:Tutorial Section 3.3#Gamma Handling|Gamma Handling]] for more information on gamma.</p>
+<p>This will cause POV-Ray to perform gamma adjustment or decoding on the input file data before building the bump map. Alternatively to a numerical value, <code>srgb</code> may be specified to denote that the file is pre-corrected or encoded using the <em>sRGB transfer function</em> instead of a power-law gamma function. {{New}} in version 3.7.1, other valid special values are <code>bt709</code> and <code>bt2020</code>, denoting that the file is encoded or pre-corrected using the ITU-R BT.709 or BT.2020 transfer function, respectively. See section [[Documentation:Tutorial Section 3.3#Gamma Handling|Gamma Handling]] for more details.</p>
 <p>The file name is optionally followed by one or more <em>BITMAP_MODIFIERS</em>. The <code>bump_size</code>, <code>use_color</code> and <code>use_index</code> modifiers are specific to bump maps and are discussed in the following sections. See the section <!--<linkto "Bitmap Modifiers">Bitmap Modifiers</linkto>--->[[Reference:Bitmap Modifiers|Bitmap Modifiers]] where the generic bitmap modifiers <code>map_type</code>, <code>once</code> and <code>interpolate</code> are described.</p>
 {{#indexentry:bump_size}}
 ==Bump_Size==
 <p>The relative bump size can be scaled using the <code>bump_size</code> modifier. The bump size number can be any number other than 0 but typical values are from about 0.1 to as high as 4.0 or 5.0.</p>

@@ Line 54: / Line 54: @@
 </pre>
-{{#indexentry:use_index, use_color, use_colour}}
+{{#indexentry:use_index|use_color|use_colour}}
 ==Use_Index and Use_Color==
 <p>Usually the bump map converts the color of the pixel in the map to a gray scale intensity value in the range 0.0 to 1.0 and calculates the bumps based on that value. If you specify <code>use_index</code>, the bump map uses the color's palette number to compute as the height of the bump at that point. So, color number 0 would be low and color number 255 would be high (if the image has 256 palette entries). The actual color of the pixels doesn't matter when using the index. This option is only available on
 palette based formats. The <code>use_color</code> keyword may be specified to explicitly note that the color methods should be used instead. The alternate spelling <code>use_colour</code> is also valid. These modifiers may only be used inside the <code>bump_map</code> statement.</p>

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