Mip Mapping - Revision history

EricChadwick: /* Testing the Mip Level */ links

2016-11-17T13:31:04Z

‎Testing the Mip Level: links

EricChadwick: /* Testing the Mip Level */ Optimal texture size?

2015-06-06T18:53:13Z

‎Testing the Mip Level: Optimal texture size?

EricChadwick: Testing the Mip Level

2015-06-06T18:52:01Z

Testing the Mip Level

EricChadwick: image formatting, PDF attachment

2014-11-30T00:56:26Z

image formatting, PDF attachment

EricChadwick: cleanups

2014-11-29T23:07:13Z

cleanups

Caustic at 14:09, 10 October 2014

2014-10-10T14:09:56Z

EricChadwick: EricChadwick moved page Mip Mapping to Mip mapping: switching to initial uppercase

2014-08-21T21:39:29Z

EricChadwick moved page Mip Mapping to Mip mapping: switching to initial uppercase

New page

#REDIRECT [[Mip mapping]]

← Older revision		Revision as of 13:31, 17 November 2016
Line 34:		Line 34:

	See also [http://www.polycount.com/forum/showthread.php?t=60842 Optimal texture size?] on the Polycount Forum.		See also [http://www.polycount.com/forum/showthread.php?t=60842 Optimal texture size?] on the Polycount Forum.
		+
		+	* [http://aras-p.info/blog/2011/05/03/a-way-to-visualize-mip-levels/ http://aras-p.info/blog/2011/05/03/a-way-to-visualize-mip-levels/]
		+	* [https://docs.unrealengine.com/udk/Three/ViewModes.html#Texture%20Density https://docs.unrealengine.com/udk/Three/ViewModes.html#Texture Density]
		+	* [https://docs.unrealengine.com/latest/INT/Engine/UI/LevelEditor/Viewports/ViewModes/#lightmapdensity https://docs.unrealengine.com/latest/INT/Engine/UI/LevelEditor/Viewports/ViewModes/#lightmapdensity]
		+	* [http://docs.cryengine.com/display/SDKDOC2/Texels+Per+Meter http://docs.cryengine.com/display/SDKDOC2/Texels+Per+Meter]

	== Nvidia DDS Plugin for Photoshop ==		== Nvidia DDS Plugin for Photoshop ==

@@ Line 32: / Line 32: @@
 [[Image:mip_colors_chadwick.jpg|thumb|left|400px|A mip map test file applied to all objects in a scene, shows the optimal texture sizes. Image by [http://ericchadwick.com Eric Chadwick].]]<br clear="all"/>
 [[File:mip_colors_2014_chadwick.zip]] Mip map test file in [[DDS]] format.
 == Nvidia DDS Plugin for Photoshop ==

← Older revision		Revision as of 18:52, 6 June 2015
Line 26:		Line 26:
	\|}		\|}

		+
		+	== Testing the Mip Level ==
		+	Use an image with custom mip levels to test which texture size the assets use the most. It's easy then to see which assets are never using the higher mips, and can thus use smaller textures.
		+
		+	[[Image:mip_colors_chadwick.jpg\|thumb\|left\|400px\|A mip map test file applied to all objects in a scene, shows the optimal texture sizes. Image by [http://ericchadwick.com Eric Chadwick].]]<br clear="all"/>
		+	[[File:mip_colors_2014_chadwick.zip]] Mip map test file in [[DDS]] format.

	== Nvidia DDS Plugin for Photoshop ==		== Nvidia DDS Plugin for Photoshop ==

@@ Line 9: / Line 9: @@
 [http://developer.nvidia.com/object/General_FAQ.html#t1 NVIDIA] says: ''"Whether you're using mipmapping or not, you should never use "nearest" filtering, which causes texture swimming artifacts when textures are minified. Using mipmaps allows you to create accurately minified versions of your textures, so that they look as good as possible in the distance. Mipmapped textures only require 33% more memory than their non-mipmapped counterparts, so it is wise to trade off the small amount of extra memory for the vastly improved image quality. In addition, today's GPUs are optimized to handle mipmaps very efficiently, so the performance impact of using mipmaps is minimal."''
-* NVIDIA whitepaper [[ftp://download.nvidia.com/developer/presentations/2005/Misc/Lets_Get_Small-2005.pdf|Let's Get Small: Understanding MIP Mapping]] by Kevin Bjorke (4MB PDF)<<BR>>Helpful tips on using mips.
+* NVIDIA whitepaper [[file:Lets_Get_Small-2005.pdf|Let's Get Small: Understanding MIP Mapping]] by Kevin Bjorke (4MB PDF). Helpful tips on using mips.
-* [http://www.polycount.com/forum/showthread.php?t=92218 Making good mipmaps?] Polycount forum thread with tips.
+* [http://www.polycount.com/forum/showthread.php?t=92218 Making good mipmaps?] Polycount Forum Thread with tips.
 == Mip Fading ==
@@ Line 18: / Line 18: @@
 {| border="1"
-|[[Image:mip_mountblade-mip-fade-tutorial.jpg|thumb|left|200px]]
+|rowspan="2"|[[Image:mip_mountblade-mip-fade-tutorial.jpg|thumb|left|200px]]
-|[[Image:mip_mountblade-no-mip-fade_thumb.jpg|thumb|left|200px|Without mip fading.]]
+|[[Image:mip_mountblade-no-mip-fade_thumb.jpg|thumb|left|400px|Without mip fading.]]
-|[[Image:mip_mountblade-yes-mip-fade_thumb.jpg|thumb|left|200px|Mip fading has been added.]]
 |-
-|colspan="3"|Mip map fading tutorial and examples. Images by [http://wypierpapier.blogspot.com/ 'Gutekfiutek'].
+|[[Image:mip_mountblade-yes-mip-fade_thumb.jpg|thumb|left|400px|Mip fading has been added.]]
 |}

@@ Line 1: / Line 1: @@
 == What is a Mip Map? ==
 To render a texture more smoothly in a game, it is resized multiple times to make "mips," which are smaller versions of the texture. These smaller versions are swapped or blended with the original texture as the texture recedes in the scene.
@@ Line 11: / Line 6: @@
 The term ''mip'' is based on the Latin phrase ''multum in parvo'', meaning "much in a small space". See the [http://en.wikipedia.org/wiki/Mipmap Wikipedia Mipmap page].
-{| border="1" cellpadding="2" cellspacing="0"
+[[image:nvidia_mipmaps.jpg|frame|left|Mip maps. Image by [http://developer.nvidia.com/ NVIDIA].]]<br clear="all"/>Most game engines will create the mips automatically, if mips don't already exist in the texture file when it's loaded. If you create the mips yourself, you can do some interesting texture tricks, by taking advantage of the fact that the textures are swapped by distance... fogging, sharpening, fading out, etc.
-|-
-|}
-−
 Most game engines will create the mips automatically, if mips don't already exist in the texture file when it's loaded. If you create the mips yourself, you can do some interesting texture tricks, by taking advantage of the fact that the textures are swapped by distance... fogging, sharpening, fading out, etc.
 [http://developer.nvidia.com/object/General_FAQ.html#t1 NVIDIA] says: ''"Whether you're using mipmapping or not, you should never use "nearest" filtering, which causes texture swimming artifacts when textures are minified. Using mipmaps allows you to create accurately minified versions of your textures, so that they look as good as possible in the distance. Mipmapped textures only require 33% more memory than their non-mipmapped counterparts, so it is wise to trade off the small amount of extra memory for the vastly improved image quality. In addition, today's GPUs are optimized to handle mipmaps very efficiently, so the performance impact of using mipmaps is minimal."''
@@ Line 22: / Line 13: @@
 == Mip Fading ==
 Because of the way texture filtering works, distant polygons (and oblique polygons) usually use the smaller mip levels of a texture. This can be exploited for special effects, by purposefully editing the mip levels.
-== Nvidia DDS Plugin for Photoshop ==
+In the following example the original texture has been darkened, then the mips have been tinted with progressively brighter colors as they get smaller, using the [[#Nvidia_DDS_Plugin_for_Photoshop|Nvidia DDS plugin]]. This causes a velvet-like effect for the grass surface.
-If you're using the [[Category:TextureFormatRuntime|DDS format]] the [http://developer.nvidia.com/nvidia-texture-tools-adobe-photoshop NVIDIA DDS plugin for Photoshop] the [http://developer.nvidia.com/nvidia-texture-tools-adobe-photoshop NVIDIA DDS plugin for Photoshop] has a great interface for testing mips settings and creating custom mips. However it doesn't work in a 64bit operating system.
-−
-=== Sharpening Settings window ===
-{| border="1" cellpadding="2" cellspacing="0"
+{| border="1"
 |-
 |}
 Each of the numbered boxes at the bottom corresponds to one of the mip levels... "Image" is the top mip level, and they descend from there.
 The number of boxes you need to adjust depends on how large your original image is. For example a 256x256 map only has nine mip levels: 256,128,64,32,16,8,4,2, and 1 (1x1). So you would only have to adjust the boxes from Image to 8.

← Older revision		Revision as of 14:09, 10 October 2014
Line 1:		Line 1:
−	#~~REDIRECT~~ [[Mip ~~mapping~~]]	+	<!-- ## page was renamed from Mip Map -->
		+	= Mip Map =
		+
		+
		+
		+	== What is a Mip Map? ==
		+	To render a texture more smoothly in a game, it is resized multiple times to make "mips," which are smaller versions of the texture. These smaller versions are swapped or blended with the original texture as the texture recedes in the scene.
		+
		+	Without mips, as unfiltered texture pixels get smaller than screen pixels they shimmer like crazy, because the pixels are quickly switching from one color to another. This is called "nearest neighbor" filtering. Instead games usually use bilinear, trilinear, or anisotropic filtering, for smoother texture rendering.
		+
		+	The term ''mip'' is based on the Latin phrase ''multum in parvo'', meaning "much in a small space". See the [http://en.wikipedia.org/wiki/Mipmap Wikipedia Mipmap page].
		+
		+	{\| border="1" cellpadding="2" cellspacing="0"
		+	\|-
		+	\|}
		+
		+	Most game engines will create the mips automatically, if mips don't already exist in the texture file when it's loaded. If you create the mips yourself, you can do some interesting texture tricks, by taking advantage of the fact that the textures are swapped by distance... fogging, sharpening, fading out, etc.
		+
		+	[http://developer.nvidia.com/object/General_FAQ.html#t1 NVIDIA] says: ''"Whether you're using mipmapping or not, you should never use "nearest" filtering, which causes texture swimming artifacts when textures are minified. Using mipmaps allows you to create accurately minified versions of your textures, so that they look as good as possible in the distance. Mipmapped textures only require 33% more memory than their non-mipmapped counterparts, so it is wise to trade off the small amount of extra memory for the vastly improved image quality. In addition, today's GPUs are optimized to handle mipmaps very efficiently, so the performance impact of using mipmaps is minimal."''
		+	* NVIDIA whitepaper [[ftp://download.nvidia.com/developer/presentations/2005/Misc/Lets_Get_Small-2005.pdf\|Let's Get Small: Understanding MIP Mapping]] by Kevin Bjorke (4MB PDF)<<BR>>Helpful tips on using mips.
		+	* [http://www.polycount.com/forum/showthread.php?t=92218 Making good mipmaps?] Polycount forum thread with tips.
		+
		+	== Mip Fading ==
		+	[[Image:mip_mountblade-mip-fade-tutorial.jpg\|thumb\|200px\|In this example the original texture has been darkened, then the mips have been tinted with progressively brighter colors as they get smaller, using the [[#Nvidia_DDS_Plugin_for_Photoshop\|Nvidia DDS plugin]]. This causes a velvet-like effect for the grass surface.]]
		+
		+	Because of the way texture filtering works, distant polygons (and oblique polygons) usually use the smaller mip levels of a texture. This can be exploited for special effects, by purposefully editing the mip levels.
		+
		+	== Nvidia DDS Plugin for Photoshop ==
		+	If you're using the [[Category:TextureFormatRuntime\|DDS format]] the [http://developer.nvidia.com/nvidia-texture-tools-adobe-photoshop NVIDIA DDS plugin for Photoshop] the [http://developer.nvidia.com/nvidia-texture-tools-adobe-photoshop NVIDIA DDS plugin for Photoshop] has a great interface for testing mips settings and creating custom mips. However it doesn't work in a 64bit operating system.
		+
		+	=== Sharpening Settings window ===
		+
		+	{\| border="1" cellpadding="2" cellspacing="0"
		+	\|-
		+	\|}
		+
		+	Each of the numbered boxes at the bottom corresponds to one of the mip levels... "Image" is the top mip level, and they descend from there.
		+
		+	The number of boxes you need to adjust depends on how large your original image is. For example a 256x256 map only has nine mip levels: 256,128,64,32,16,8,4,2, and 1 (1x1). So you would only have to adjust the boxes from Image to 8.
		+
		+	It takes some testing to see what works best. Something that helps is the 3D Preview button, just make sure to adjust the Preview Settings first so it doesn't have to make a ton of different compressions each time you change a setting.
		+
		+	----
		+	[[Category:TextureTechnique]] [[Category:Glossary]]