DDS

From Blood Wiki
(Difference between revisions)
Jump to: navigation, search
Line 21: Line 21:
 
DDS files should have mipmaps pre-generated. If there is no mipmaps generated, it is implied that this texture is not using mipmaps.  
 
DDS files should have mipmaps pre-generated. If there is no mipmaps generated, it is implied that this texture is not using mipmaps.  
  
{{important|Engine shouldn't try to use mipmaps on this texture (see [[Darkplaces_material_system/General_Keywords#noMipMaps | noPicMip]], also gfx/ images never use mipmaps) or it can crash.}}
+
{{important|Engine shouldn't try to use mipmaps if they are not exist in DDS (see [[Darkplaces_material_system/General_Keywords#noMipMaps | noPicMip]], also gfx/ images never use mipmaps) or it can crash.}}
  
 
{{bug|Some drivers don't deal with non-power-of-two compressed textures (giving the black walls). Best way is to always make DDS textures to be [[power-of-two]].}}
 
{{bug|Some drivers don't deal with non-power-of-two compressed textures (giving the black walls). Best way is to always make DDS textures to be [[power-of-two]].}}

Revision as of 14:27, 1 August 2012

This page is not finished
You can help by editing and extending it.

Direct Draw Suface is a file format developed by Microsoft for DirectX SDK. This format is used in many games to store compressed textures.

Darkplaces engine can load DDS storing the images of the following formats:

  • BGRA : 32-bit uncompressed image
  • DXT1 : 4-bit compressed DXT1 texture
  • DXT2 : 8-bit compressed DXT2 texture
  • DXT3 : 8-bit compressed DXT3 texture
  • DXT4 : 8-bit compressed DXT4 texture
  • DXT5 : 8-bit compressed DXT5 texture

In Darkplaces, DDS are not general texture format like TGA or JPEG but an override texture (dds/filename.dds) that get loaded instead of it's base texture (filename.tga), if presented.

All DDS files should be stored under dds/ directory, rest of the path should mimic file path of the base texture:

dds/textures/mausoleum/outerwall1_1 // override textures/mausoleum/outerwall1_1
dds/models/mapobjects/inn/barrel1_1_norm // override models/mapobjects/inn/barrel1_1_norm
dds/models/mapobjects/inn/barrel1_1 // override models/mapobjects/inn/barrel1_1

DDS files should have mipmaps pre-generated. If there is no mipmaps generated, it is implied that this texture is not using mipmaps.

Important: Engine shouldn't try to use mipmaps if they are not exist in DDS (see noPicMip, also gfx/ images never use mipmaps) or it can crash.
Bug: Some drivers don't deal with non-power-of-two compressed textures (giving the black walls). Best way is to always make DDS textures to be power-of-two.

DDS for NetRadiant

Unfortunately, NetRadiant can't load DDS images, it always loads base texture instead. This becomes a problem when supplying Radiant with the builded game (which only include DDS, no base textures). In order to avoid missing textures and broken brush texturing, every world texture that gotta be applied on brushes, should have separate radiant-only image (see qer_editorImage).

By a convention, radiant-only image should be stored in gamedir/radiant/path_to_base_texture:

textures/town/wall1_1
{ 
    qer_editorImage radiant/textures/town/wall1_1
    ...
}

Tools

You can use following tools to produce compressed DDS images:

Future alternatives

In 2010 Khronos group introduced KTX format (covering OpenGL and OpenGL ES texture formats). This format can be used as a replacement to DDS in future.

Console variables

 r_texture_dds_load : load compressed dds/filename.dds instead of filename.tga. If file exists (requires driver support).
 r_texture_dds_load_alphamode : trust DDPF_ALPHAPIXELS flag, 1: texture format and brute force search if ambiguous, 2: texture format only
 r_texture_dds_load_logfailure : log missing DDS textures to ddstexturefailures.log, 0: done log, 1: log with no optional textures (_norm, glow etc.). 2: log all
 r_texture_dds_save : save compressed dds/filename.dds texture when filename.tga is loaded, so that it can be loaded instead next time
 r_texture_dds_swdecode : 0: don't software decode DDS, 1: software decode DDS if unsupported, 2: always software decode DDS. Software decoding breaks all benefits of DDS and should be used if driver dont support DDS or for debugging purposes.

See also

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox