Difference between revisions of "Creating detailed Normal Maps"

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''.

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.

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.