Difference between revisions of "Template:Portal:Texturing/Featured"
imported>Darkness X |
imported>Katan (Matched to the updated article) |
||
| Line 1: | Line 1: | ||
====Creating detailed Normal Maps==== | ====Creating detailed Normal Maps==== | ||
You need to create a [[Normal_Maps| | You need to create a [[Normal_Maps|normal map]] first and foremost because if you don't, your texture wouldn't reflect light and therefore appear black ingame. What is more there is an even better reason why you '''want''' to do one. Normal maps are designed to make an object look much more detailed than it actually is. Based on illumination and the information stored in the file, a congrous surfase is simulated. In other words, you could stay in front of a completely flat plane with a stone texture that appears to be uneven and rocky, thanks to the normal map. | ||
Not | Not every texture has a normal map, only those that are rendered ingame such as tables, books, clothes, etc. Icons, book images, menus and whatnot aren't rendered ingame, hence they don't need one. The normal map's file name orientates itself by the texture, with the sole exception that '''_n''' is attached to it. E.g., the normal map for the texture ''Texture.dds'' would be ''Texture_n.dds''. | ||
One normal map can relate to an endless amount of textures. Example: You have a normal map and two textures. The normal map is called ''normal_n.dds'', the two texture files ''normal_tex01.dds'' and ''normal_tex02.dds''' respectively. The game will recognize both textures as belonging to the one ''normal_n''; it simply ignores the letters that come after the underscores, in this case ''tex01'' and ''tex02''. So you may want to avoid texture file names like ''my_uber_sword_texture.dds''. | |||
And why is the | And why is the normal map's detail important? Because it is the normal map that defines how uneven and how rocky your stone texture looks ingame. Less detail for the normal map equals less detail for the object. | ||
<div style="text-align:right;">[[Creating detailed Normal Maps|Read more...]]</div> | <div style="text-align:right;">[[Creating detailed Normal Maps|Read more...]]</div> | ||
Latest revision as of 08:11, 14 May 2010
Creating detailed Normal Maps[edit source]
You need to create a normal map first and foremost because if you don't, your texture wouldn't reflect light and therefore appear black ingame. What is more there is an even better reason why you want to do one. Normal maps are designed to make an object look much more detailed than it actually is. Based on illumination and the information stored in the file, a congrous surfase is simulated. In other words, you could stay in front of a completely flat plane with a stone texture that appears to be uneven and rocky, thanks to the normal map.
Not every texture has a normal map, only those that are rendered ingame such as tables, books, clothes, etc. Icons, book images, menus and whatnot aren't rendered ingame, hence they don't need one. The normal map's file name orientates itself by the texture, with the sole exception that _n is attached to it. E.g., the normal map for the texture Texture.dds would be Texture_n.dds.
One normal map can relate to an endless amount of textures. Example: You have a normal map and two textures. The normal map is called normal_n.dds, the two texture files normal_tex01.dds and normal_tex02.dds' respectively. The game will recognize both textures as belonging to the one normal_n; it simply ignores the letters that come after the underscores, in this case tex01 and tex02. So you may want to avoid texture file names like my_uber_sword_texture.dds.
And why is the normal map's detail important? Because it is the normal map that defines how uneven and how rocky your stone texture looks ingame. Less detail for the normal map equals less detail for the object.