PMC websites shut down November 13th 2025 unless web hosting fees are paid. See up to date status from PMC Website Hosting and Domain Registration Fee Status forum topic. Please Support PMC to help keep these websites online.

Enjoyed or found this pages content useful, please Support PMC to help me keep this web page online beyond November 13th 2025 when web hosting fees are due.

PMC Editing Wiki

User Tools

Site Tools

Trace: • overview.html
arma:file_formats:paa

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
arma:file_formats:paa [2015/08/22 01:42] – removed obsolete links. snakemanarma:file_formats:paa [2024/08/01 08:04] (current) – links added. snakeman
Line 1: Line 1:
-====== PAA / PAC file format ======+====== ArmA 1 PAA / PAC File Format ====== 
 + 
 +[[https://www.pmctactical.org/forum/viewforum.php?f=42|ArmA 1 Forum]], [[:arma|ArmA 1 Home]], [[arma:config|ArmA 1 Config]], [[arma:tools|ArmA 1 Tools]], [[arma:file_formats|ArmA 1 File Formats]], [[arma:missions|ArmA 1 Missions]], [[arma:modeling|ArmA 1 3D Modeling]], [[arma:terrain|ArmA 1 Terrain]], [[arma:texturing|ArmA 1 Texturing]], [[arma:scripting|ArmA 1 Scripting]] 
 + 
 +**ArmA 1** aka Armed Assault (ArmA)
  
  
 ====== Introduction ====== ====== Introduction ======
  
-Of the many image file formats 'out there', such as jpeg, such as gif. BI choose to use a specially developed file format (paa) as the base texture file for all engine types. The reason for this is the raw data within the file can be passed directly to Miscrosft's Direct X as a DCT1 picture (eg) without further massaging. While all engines except Elite also support JPG files, PAA files can result in much better performance.+Of the many image file formats 'out there', such as jpeg, such as gif. bis choose to use a specially developed file format (paa) as the base texture file for all engine types. The reason for this is the raw data within the file can be passed directly to Miscrosft's Direct X as a DCT1 picture (eg) without further massaging. While all engines except Elite also support JPG files, PAA files can result in much better performance.
  
  
Line 24: Line 28:
 Every PAA file starts with a **TypeOfPaa** Every PAA file starts with a **TypeOfPaa**
 <code cpp> <code cpp>
-ushort TypeOfPaa;  // type of texture, known values are +ushort TypeOfPaa;  // type of texture, known values are
     // 0xFF01 DXT1 compressed texture (may have 1 bit alpha map, check MSDN documentation for details)     // 0xFF01 DXT1 compressed texture (may have 1 bit alpha map, check MSDN documentation for details)
     // 0x1555 Uncompressed RGBA 5:5:5:1 texture     // 0x1555 Uncompressed RGBA 5:5:5:1 texture
Line 42: Line 46:
 <code cpp> <code cpp>
 struct PAA_Tag { struct PAA_Tag {
- byte    name[8]; // name of tag is actually reversed when written in file, + byte    name[8]; // name of tag is actually reversed when written in file,
  // so OFFSTAGG would be written as GGATSFFO. See  below for known tags.  // so OFFSTAGG would be written as GGATSFFO. See  below for known tags.
  ULONG tag_size; // size of this tag  ULONG tag_size; // size of this tag
Line 53: Line 57:
 **Special Case** **Special Case**
  
-TypeOfPaa 0x4747 Uncompressed Index Palette texture +TypeOfPaa 0x4747 Uncompressed Index Palette texture
  
-This is a corrupt entry in the sense that it does not have a TypeOfPaa! It is the lead in bytes to a standard AVCGTAGG. The next block of data is, the palette. Followed by 'standard' mip-data blocks. +This is a corrupt entry in the sense that it does not have a TypeOfPaa! It is the lead in bytes to a standard AVCGTAGG. The next block of data is, the palette. Followed by 'standard' mip-data blocks.
  
 Indecipherable commentary from Feersum:\\ Indecipherable commentary from Feersum:\\
Line 63: Line 67:
 ====== HexDump ====== ====== HexDump ======
  
-{{http://tactical.nekromantix.com/images/wiki/Paacformat.gif}}+{{https://pmc.editing.wiki/images/Paacformat.gif}}
  
  
Line 136: Line 140:
  UWORD width; // width of this mipmap  UWORD width; // width of this mipmap
  UWORD height; // height of this mipmap  UWORD height; // height of this mipmap
- UCHAR size[3]; // size of compressed texture data. this is 24-bit unsigned integer.  + UCHAR size[3]; // size of compressed texture data. this is 24-bit unsigned integer. 
- UCHAR data[size]; // actual texture data + UCHAR data[size]; // actual texture data
 }; };
 </code> </code>
Line 204: Line 208:
 **FLAGTAGG = 1, interpolated alpha channel (default behaviour)** **FLAGTAGG = 1, interpolated alpha channel (default behaviour)**
  
-{{http://tactical.nekromantix.com/images/wiki/paa_alpha_channel_default.jpg}}+{{https://pmc.editing.wiki/images/paa_alpha_channel_default.jpg}}
  
 **FLAGTAGG = 2, alpha channel interpolation disabled** **FLAGTAGG = 2, alpha channel interpolation disabled**
  
-{{http://tactical.nekromantix.com/images/wiki/paa_alpha_channel_no_interpolation.jpg}}+{{https://pmc.editing.wiki/images/paa_alpha_channel_no_interpolation.jpg}}
  
  
Line 215: Line 219:
 MSDN documentation on DXT1 textures: [[http://msdn.microsoft.com/library/default.asp?url=/library/en-us/directx9_c/Opaque_and_1_Bit_Alpha_Textures.asp|DirectX: Opaque and 1-Bit Alpha Textures]]\\ MSDN documentation on DXT1 textures: [[http://msdn.microsoft.com/library/default.asp?url=/library/en-us/directx9_c/Opaque_and_1_Bit_Alpha_Textures.asp|DirectX: Opaque and 1-Bit Alpha Textures]]\\
 Squish Compression [[http://www.sjbrown.co.uk/?code=squish|DXTn compress/decompress]] Squish Compression [[http://www.sjbrown.co.uk/?code=squish|DXTn compress/decompress]]
 +
arma/file_formats/paa.1440207773.txt.gz · Last modified: 2015/08/22 01:42 (external edit)