Difference between revisions of "Texture formats"
From polycount
m |
EricChadwick (Talk | contribs) (removed redundant title, moved todo to Discussion page, better headings, simplified text.) |
||
| Line 1: | Line 1: | ||
| − | + | In game development, artists may have several sets of texture files: | |
| − | + | # Source files, native to an image editor such as Photoshop's PSD, stores all editing information such as layers, and high bit depths. | |
| + | # Preview files, for previewing on 3D models or importing into a level editor, does not store layers, usually only [[8bpp]]. | ||
| + | # Runtime files, flattened and compressed files used directly by a game engine, often lossy so not good for editing. | ||
| − | == | + | == Source Formats == |
| − | + | * [[EXR]] | |
| + | * [[HDR]] | ||
| + | * [[PSD]] | ||
| + | * [[TIF]] | ||
| + | == Preview Formats == | ||
* [[BMP]] | * [[BMP]] | ||
| − | |||
* [[GIF]] | * [[GIF]] | ||
| − | |||
* [[JPG]] | * [[JPG]] | ||
* [[PNG]] | * [[PNG]] | ||
| − | * [[ | + | * [[TGA]] |
* [[TIF]] | * [[TIF]] | ||
| − | |||
| − | |||
| − | |||
== Runtime Formats == | == Runtime Formats == | ||
| − | These are | + | These are formats used directly by the game engine. |
| − | Texture | + | * [[3Dc]] |
| + | * [[DDS]] Direct Draw Surface format, which can contain uncompressed, paletted, and compressed variants. | ||
| + | * [[DXT]] DirectX Texture format. | ||
| + | * [[PVR]] | ||
| + | * [[S3TC]] | ||
| + | * [[TPL]] | ||
| + | * [[VTF]] Valve Texture Format, used in Source Engine games. | ||
| − | To save memory, runtime textures often use compression. | + | To save memory, runtime textures often use compression. Specific compression formats are supported in hardware, which means they stay compressed as they are sent to the video card, which can save a significant amount of memory. |
Runtime formats also commonly have pre-created [[Mipmap|mip levels]] stored in them, so the game engine doesn't have to create the mips on load, which helps to reduce the time it takes to load the game level. | Runtime formats also commonly have pre-created [[Mipmap|mip levels]] stored in them, so the game engine doesn't have to create the mips on load, which helps to reduce the time it takes to load the game level. | ||
| − | + | ---- | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
[[Category:Texturing]] | [[Category:Texturing]] | ||
Revision as of 13:42, 14 March 2015
In game development, artists may have several sets of texture files:
- Source files, native to an image editor such as Photoshop's PSD, stores all editing information such as layers, and high bit depths.
- Preview files, for previewing on 3D models or importing into a level editor, does not store layers, usually only 8bpp.
- Runtime files, flattened and compressed files used directly by a game engine, often lossy so not good for editing.
Source Formats
Preview Formats
Runtime Formats
These are formats used directly by the game engine.
- 3Dc
- DDS Direct Draw Surface format, which can contain uncompressed, paletted, and compressed variants.
- DXT DirectX Texture format.
- PVR
- S3TC
- TPL
- VTF Valve Texture Format, used in Source Engine games.
To save memory, runtime textures often use compression. Specific compression formats are supported in hardware, which means they stay compressed as they are sent to the video card, which can save a significant amount of memory.
Runtime formats also commonly have pre-created mip levels stored in them, so the game engine doesn't have to create the mips on load, which helps to reduce the time it takes to load the game level.
