Light map - Revision history

EricChadwick: /* More Information */ removed :Category:TextureCoordinates because doesn't exist, contains nothing

2015-03-14T17:20:09Z

‎More Information: removed Category:TextureCoordinates because doesn't exist, contains nothing

EricChadwick: /* More Information */ :Category:TextureCoordinates

2015-03-14T16:53:37Z

‎More Information: Category:TextureCoordinates

EricChadwick: Edge padding link fix

2014-09-13T00:31:09Z

Edge padding link fix

EricChadwick: credits fix

2014-09-13T00:08:35Z

credits fix

EricChadwick: images restored

2014-09-13T00:08:09Z

images restored

Throttlekitty: Throttlekitty moved page LightMap to Light map: Convert old>new space and case.

2014-08-14T17:13:42Z

Throttlekitty moved page LightMap to Light map: Convert old>new space and case.

Throttlekitty at 17:12, 14 August 2014

2014-08-14T17:12:57Z

Cheeseplus: 15 revisions

2014-07-29T08:43:41Z

15 revisions

EricChadwick: HDR, RGBM

2014-04-04T16:14:55Z

HDR, RGBM

EricChadwick: CategoryEnvironmentLighting

2013-09-20T21:15:01Z

CategoryEnvironmentLighting

@@ Line 35: / Line 35: @@
 * [http://www.scriptspot.com/3ds-max/scripts/texture-atlas-generator Texture Atlas Generator]
 * [[RadiosityNormalMap]]
 == Software ==

@@ Line 35: / Line 35: @@
 * [http://www.scriptspot.com/3ds-max/scripts/texture-atlas-generator Texture Atlas Generator]
 * [[RadiosityNormalMap]]
-* [[Category:TextureCoordinates]]
+* [[:Category:TextureCoordinates]]
 == Software ==

@@ Line 23: / Line 23: @@
 Some people create the light map UVs with an automatic unwrap & pack algorithm. Automatic unwrapping is faster and easier to create but it tends to waste more texture space, so the light map pixels end up larger on the model, the lighting is more blurry.
-Time-permitting, for the best results it is best to start with a copy of the texture UVs (if they're good), unmirror any mirrored parts that need unique lighting, un-overlap any overlaps that need unique lighting, and scale up the UVs for areas that need greater lighting detail. Then pack them all into the 0-1 UV square with appropriate [[Edge Padding]] space between the UVs.
+Time-permitting, for the best results it is best to start with a copy of the texture UVs (if they're good), unmirror any mirrored parts that need unique lighting, un-overlap any overlaps that need unique lighting, and scale up the UVs for areas that need greater lighting detail. Then pack them all into the 0-1 UV square with appropriate [[Edge  padding]] space between the UVs.
 When an artist manually tunes the UVs by overlapping/mirroring parts they know will receive identical lighting, and scaling up areas that have higher-frequency shadows, this allows the light map to have a higher apparent texture resolution. If overlaps are used, they should be moved at least 1 unit outside the UV square to avoid rendering errors when the lighting is baked.

@@ Line 4: / Line 4: @@
 Because the light map lighting is baked ahead of time the artist can use a non-real-time lighting techniques like radiosity, which can take many minutes to render. This allows the surfaces to receive bounce lighting, soft shadowing, color bleeding, etc., for a very realistic-looking result.
-[[image:lightmap_samavan-ishuriken.jpg|thumb|600px|left|Multiply light mapping for the iPhone, [http://samavan.deviantart.com/art/iPhone-Shuriken-Game-2-145376053 original size]. Image by [http://samavan.com/|Thomas "sama.van" Varoux].]]<br clear="all"/>
+[[image:lightmap_samavan-ishuriken.jpg|thumb|600px|left|Multiply light mapping for the iPhone, [http://samavan.deviantart.com/art/iPhone-Shuriken-Game-2-145376053 original size]. Image by [http://samavan.com/ Thomas "sama.van" Varoux].]]<br clear="all"/>
 Traditionally, light maps store the color and brightness of pre-baked lighting. The [[Diffuse map]] is applied to the mesh with no lighting (like an [[Emissive map]]), and the light map is then multiplied against it, darkening the diffuse where the light map has shadows.
@@ Line 12: / Line 12: @@
 However, an over-multiply technique can be used instead to get an "over-exposed" look, where the light map is multiplied two or more times. If it is multiplied 2x this means middle-gray will cause the diffuse map to render at its regular intensity, while brighter light map values will cause over-brightening, and darker values will still darken the color map. If multiplied 4x then 1/4 gray becomes the middle value.
-[[image:20110422_multiply4x.jpg|thumb|600px|left|Multiplying vertex color onto a texture, using a 4x multiply [[Shaders|shader]] to over-brighten. This example uses vertex color, but a light map could easily be used instead. Image by [http://ericchadwick.com/|Eric Chadwick].]]<br clear="all"/>
+[[image:20110422_multiply4x.jpg|thumb|600px|left|Multiplying vertex color onto a texture, using a 4x multiply [[Shaders|shader]] to over-brighten. This example uses vertex color, but a light map could easily be used instead. Image by [http://ericchadwick.com/ Eric Chadwick].]]<br clear="all"/>
 Another type of light mapping called [[Radiosity normal map|Radiosity Normal Mapping]] or Directional Light Mapping is where the light is stored as directions in order to combine it with normal maps to create the appearance of higher-frequency light mapping. For more information see the [http://www.polycount.com/forum/showthread.php?t=76554 Lightmaps: tech pros and cons] thread on Polycount.

@@ Line 4: / Line 4: @@
 Because the light map lighting is baked ahead of time the artist can use a non-real-time lighting techniques like radiosity, which can take many minutes to render. This allows the surfaces to receive bounce lighting, soft shadowing, color bleeding, etc., for a very realistic-looking result.
-Traditionally, light maps store the color and brightness of pre-baked lighting. The [[Diffuse map]] is applied to the mesh with no lighting (like an [[Emissive map]]), and the light map is then multiplied against it, darkening the diffuse where the light map has shadows.
+[[image:lightmap_samavan-ishuriken.jpg|thumb|600px|left|Multiply light mapping for the iPhone, [http://samavan.deviantart.com/art/iPhone-Shuriken-Game-2-145376053 original size]. Image by [http://samavan.com/|Thomas "sama.van" Varoux].]]<br clear="all"/>
-{| border="1" cellpadding="2" cellspacing="0"
+Traditionally, light maps store the color and brightness of pre-baked lighting. The [[Diffuse map]] is applied to the mesh with no lighting (like an [[Emissive map]]), and the light map is then multiplied against it, darkening the diffuse where the light map has shadows.
-|-
-|}
 Because the light map is multiplicative, this can only darken the surface.
@@ Line 14: / Line 12: @@
 However, an over-multiply technique can be used instead to get an "over-exposed" look, where the light map is multiplied two or more times. If it is multiplied 2x this means middle-gray will cause the diffuse map to render at its regular intensity, while brighter light map values will cause over-brightening, and darker values will still darken the color map. If multiplied 4x then 1/4 gray becomes the middle value.
-{| border="1" cellpadding="2" cellspacing="0"
+[[image:20110422_multiply4x.jpg|thumb|600px|left|Multiplying vertex color onto a texture, using a 4x multiply [[Shaders|shader]] to over-brighten. This example uses vertex color, but a light map could easily be used instead. Image by [http://ericchadwick.com/|Eric Chadwick].]]<br clear="all"/>
-|-
-|}
 Another type of light mapping called [[Radiosity normal map|Radiosity Normal Mapping]] or Directional Light Mapping is where the light is stored as directions in order to combine it with normal maps to create the appearance of higher-frequency light mapping. For more information see the [http://www.polycount.com/forum/showthread.php?t=76554 Lightmaps: tech pros and cons] thread on Polycount.
 == Light Map Texture Coordinates ==
 Typically a light map requires each mesh to have a second set of UV texture coordinates, where every surface that will receive lighting needs to have its own unique space within the 0-1 UV square.

← Older revision	Revision as of 17:13, 14 August 2014
(No difference)

@@ Line 1: / Line 1: @@
 = Light Map =
 A texture that stores pre-rendered lighting, because dynamic real-time lighting typically doesn't look as nice and can be a performance hog.
@@ Line 8: / Line 4: @@
 Because the light map lighting is baked ahead of time the artist can use a non-real-time lighting techniques like radiosity, which can take many minutes to render. This allows the surfaces to receive bounce lighting, soft shadowing, color bleeding, etc., for a very realistic-looking result.
-Traditionally, light maps store the color and brightness of pre-baked lighting. The [[DiffuseMap]] is applied to the mesh with no lighting (like an [[EmissiveMap]]), and the light map is then multiplied against it, darkening the diffuse where the light map has shadows.
+Traditionally, light maps store the color and brightness of pre-baked lighting. The [[Diffuse map]] is applied to the mesh with no lighting (like an [[Emissive map]]), and the light map is then multiplied against it, darkening the diffuse where the light map has shadows.
 {| border="1" cellpadding="2" cellspacing="0"
@@ Line 22: / Line 18: @@
 |}
-Another type of light mapping called [[RadiosityNormalMap|Radiosity Normal Mapping]] or Directional Light Mapping is where the light is stored as directions in order to combine it with normal maps to create the appearance of higher-frequency light mapping. For more information see the [http://www.polycount.com/forum/showthread.php?t=76554 Lightmaps: tech pros and cons] thread on Polycount.
+Another type of light mapping called [[Radiosity normal map|Radiosity Normal Mapping]] or Directional Light Mapping is where the light is stored as directions in order to combine it with normal maps to create the appearance of higher-frequency light mapping. For more information see the [http://www.polycount.com/forum/showthread.php?t=76554 Lightmaps: tech pros and cons] thread on Polycount.
 <span id="LMTC"></span>
@@ Line 53: / Line 49: @@
 ----
-[[Category:Texturing]] [[Category:TextureTypes]] [[Category:LightMap]] [[Category:Glossary]] [[Category:EnvironmentLighting]]
+[[Category:Texturing]] [[Category:TextureTypes]] [[Category:Light map]] [[Category:Glossary]] [[Category:EnvironmentLighting]]

← Older revision	Revision as of 08:43, 29 July 2014
(No difference)

@@ Line 37: / Line 37: @@
 == More Information ==
 * [http://www.polycount.com/forum/showthread.php?t=76554 Lightmaps: tech pros and cons] thread on Polycount
 * [http://boards.polycount.net/showthread.php?t=72455 how to unwrap uv's for lightmaping purposes?] thread on Polycount
@@ Line 46: / Line 47: @@
 == Software ==
 * [http://gameware.autodesk.com/beast Beast] is used in [http://www.unrealengine.com/ Unreal Engine 3] and [http://unity3d.com/support/documentation/Manual/LightmappingInDepth.html Unity3D]
 * [http://www.frecle.net/index.php?show=giles.about giles]

← Older revision		Revision as of 21:15, 20 September 2013
Line 51:		Line 51:

	----		----
−	[[Category:Texturing]] [[Category:TextureTypes]] [[Category:LightMap]] [[Category:Glossary]]	+	[[Category:Texturing]] [[Category:TextureTypes]] [[Category:LightMap]] [[Category:Glossary]] [[Category:EnvironmentLighting]]