Texture atlas - Revision history

Windwalkr at 03:24, 6 June 2018

2018-06-06T03:24:00Z

← Older revision		Revision as of 03:24, 6 June 2018
Line 36:		Line 36:
	[[Category:Modeling]]		[[Category:Modeling]]
	[[Category:Content creation]]		[[Category:Content creation]]
	~~[[Category:TRS18]]~~

Tonyhilliam at 02:34, 17 January 2018

2018-01-17T02:34:16Z

← Older revision		Revision as of 02:34, 17 January 2018
Line 33:		Line 33:

	* Image demonstrating the combination of two separate textured meshes into an atlas.		* Image demonstrating the combination of two separate textured meshes into an atlas.

			[[Category:Modeling]]
			[[Category:Content creation]]
			[[Category:TRS18]]

N3vpolsen at 05:15, 17 October 2017

2017-10-17T05:15:27Z

← Older revision		Revision as of 05:15, 17 October 2017
Line 19:		Line 19:
	So you need to weigh up if you actually plan on having a few meshes on the screen at the one time to benefit from a texture atlas. A very effective way to use texture atlases is to make all your high LODs use individual textures so you have plenty of texels available to each asset up close and then your very lowest LOD can use a small texture atlas (eg. 256x256 even though it contains several assets). This means if 60 assets all at their lowest LOD are sharing the one texture atlas which is 256x256, not only are 60 assets only performing one draw call, you also only have a single 256x256 texture in use. In this scenario, the penalty for "misusing" an atlas is quite minimal.		So you need to weigh up if you actually plan on having a few meshes on the screen at the one time to benefit from a texture atlas. A very effective way to use texture atlases is to make all your high LODs use individual textures so you have plenty of texels available to each asset up close and then your very lowest LOD can use a small texture atlas (eg. 256x256 even though it contains several assets). This means if 60 assets all at their lowest LOD are sharing the one texture atlas which is 256x256, not only are 60 assets only performing one draw call, you also only have a single 256x256 texture in use. In this scenario, the penalty for "misusing" an atlas is quite minimal.

	[[File:~~atlastexture256x256~~]]		[[File:Atlastexture1.jpg]]

	=Performance Benefits=		=Performance Benefits=

N3vpolsen at 05:06, 17 October 2017

2017-10-17T05:06:05Z

@@ Line 1: / Line 1: @@
 A [[texture atlas]] is a single larger texture which combines what would normally be several distinct smaller textures. This technique can be a significant performance optimisation.
-This page TBD.
+A "texture atlas" is just a fancy name for the technique of packing a number of textures into one texture.
 =Performance Benefits=

Windwalkr: Created page with "A texture atlas is a single larger texture which combines what would normally be several distinct smaller textures. This technique can be a significant performance optimis..."

2017-10-11T09:14:18Z

Created page with "A texture atlas is a single larger texture which combines what would normally be several distinct smaller textures. This technique can be a significant performance optimis..."

New page

A [[texture atlas]] is a single larger texture which combines what would normally be several distinct smaller textures. This technique can be a significant performance optimisation.

This page TBD.

=Performance Benefits=
* Collapse several [[render chunk]]s into a single chunk, reducing the number of [[draw calls]] required to render a mesh.
* Collapse several [[material]]s into one, especially across multiple meshes in a [[mesh library]] asset, allowing the meshes to benefit from [[material sharing]] and [[mesh stitching]].

=Concerns=
* Texture Bleeding (when mipmapping)
* Texture Wrapping
* Over-large textures (avoid this by atlasing low LODs)

=Example=

* Image demonstrating the combination of two separate textured meshes into an atlas.