Mobile textures (SA/VC)

From GTAMods Wiki
(Redirected from Mobile textures (SA))
Jump to navigation Jump to search

The mobile ports of GTA: San Andreas and GTA: Vice City use texture systems different from their PC and console counterparts in order to reduce the amount of storage space required for storing textures.

The information in this article is based on the formats found in the mobile version of GTA:SA, but most can also be applied to GTA VC.

Textures are grouped into separate databases based on which archive file they are in on non-mobile versions. New databases have been added to store textures exclusive to the mobile games, such as touch controls, updated splash screens and menu icons.

A single texture database is made up of several files:

  • name.txt
  • name.x.toc
  • name.x.dat
  • name.x.tmb

The four files listed above are named according to the archive they come from: name is gta3 for textures from gta3.img, gta_int for textures from gta_int.img, and so on.

In these file names, x refers to the file extension of the texture format used. For example iOS devices use the PVRTC format, which means that x is pvr.


The .txt file contains a list of all the textures in the database, along with various texture properties for each. It also contains information about the database itself.

Properties in the .txt file are set with propertyname=value where value may be an integer or string value. There are two properties – png and img – that are used with hexadecimal numbers (e.g. png=72b88910), but these properties are never read by the game. It is possible that they are some sort of checksum or identifier for texture PNGs/other images.

The affiliate property is set inside quotes – "affiliate=something".

The category line defines default values for texture properties as well as information about the database itself. It must set the cat property in order to be correctly identified as a category line. In GTA:SA, this line is the first in the file, but this is not a requirement.

Texture lines begin with the quoted texture name, such as "ahoodfence2".

See the table below for a list of properties.

Property name Type Meaning
Integer Specifies the format of the texture.
mipmode Boolean
hassibling Boolean
hasbias Boolean
camnorm Boolean Unknown. Used for "thin" textures (e.g. leaves, wires).
forcez Boolean Unknown. Used for some glass textures.
decalz Boolean
noalphatest Boolean Unknown. Used for some shadow textures.
hasdetail Integer
isdetail Integer
detailtile Integer The number of times to tile the detail texture (unconfirmed).
alphamode Integer 1, 2 or 3
streammode Boolean
width Integer The width of the texture, measured in pixels.
height Integer The height of the texture, measured in pixels.
affiliate String A texture that this texture "points to". If a texture is defined as an affiliate, it simply redirects to whichever texture it points to. Affiliate textures do not have any texture data and typically do not define any other properties.



The .toc (table of contents) file is a table of offsets for the .dat file (which contains all of the texture data). This file is not required by the game: a new offset table can be created by reading the .dat file. The purpose of the offset table is to accelerate texture loading. A game running without prebuilt offset tables will likely suffer from small stutters, generally lower FPS, and textures loading later than they should (leaving some objects untextured until the texture loads).

The offset table file stores the size of the .dat file it is for in order to allow the game to ensure that the two files are compatible. If the size given in the .toc file does not match the actual .dat size, the table will be discarded and the offsets will be read directly from the data file instead.

The game is capable of generating offset table files for future use, but this code never runs in production builds. It is likely that to generate the offset files distributed with the game, a late build was run with the generation code enabled.


Offset files have a very basic format: one 32-bit unsigned integer (uint32) for the size of the data file, and then the rest of the file is consecutive 32-bit signed integer (int32) offsets in the order of the entries in the .txt file. These offsets are absolute offsets from the beginning of the data file to the start of the texture's data.

All entries in the database are given offset values. No meaningful offsets can be given for affiliate entries (as they are not actually textures themselves), so for these the value -1 (0xffffffff) is used. No other offset is valid for affiliate entries: -1 is a special case, and everything else is treated as a real offset.

The stored size of the data file is used to verify that the two files match. If this step were left out, the game would be able to try to read any arbitrary file as an offset file, which would lead to incorrect offsets being used. The data size also validates the offset file because in almost every case where the data size changes the offset file must be regenerated. If the offsets are not regenerated, the mismatch of size values allows the game to detect the invalid offsets and ignore them.

Below is example code for reading an offset file.

FILE *offsetFile = std::fopen(pathToOffsetFile, "rb");

if (!offsetFile) {
    // Error: unable to open the file.
    // ...

uint32 statedSize;
std::fread(&statedSize, 1, 4, offsetFile);

uint32 dataFileSize = /* the size of the data file */;
if (statedSize != dataFileSize) {
    // Error: offset and data files do not match.
    // ...

int32 *offsetArray = new int32[database.entryCount];

std::fread(offsetArray, 4, database.entryCount, offsetFile);

// offsetArray now contains the offsets from the file.

In both error cases in the above code, the game will resort to reading the offsets from the data file.


The .dat file contains an array of texture listings along with the actual texture data.

Textures are represented in different formats on different platforms. iOS devices use PVR for most textures, as every iPhone before the iPhone 8 used a PowerVR GPU which had special hardware support for the texture format.


The .dat file consists entirely of listing structures, with texture data following the metadata in each.

Listing structures look like the following:

struct Listing {
    hash: u16,
    encoding_type: u16,
    width: u16,
    height_mask: u16,
    compressed_size: u32,
    rle_indicator: u32,


The hash field is a 16-bit hash of the texture name. This allows the game to ensure that each listing matches up with the information from the .txt file rather than blindly trusting that the files match. This hash is calculated as follows:

  1. Start with an unsigned 32-bit hash value of 0.
  2. For every character byte in the string, shift the hash bits left by 5 and add the byte.
  3. After the loop, shift the hash bits right by 5.
  4. Take the two least significant hash bytes to obtain an unsigned 16-bit value.

Sample algorithm (Rust):

fn hash_name(name: &str) -> u16 {
    let mut hash: u32 = 0;

    for byte in name.as_bytes() {
        hash = hash
            .overflowing_add((hash << 5).overflowing_add(*byte as u32).0)

    hash.overflowing_add(hash >> 5).0 as u16

Width & Height

The height_mask field dedicates 15 bits to storing the height of the texture, but the most significant bit encodes a Boolean denoting the use of mipmaps in the texture. If the bit is 1, the texture only contains a single image, but if it is 0, there are multiple mips present. To find the number of mips, the width and height values (with the height being height_mask & 0x7fff) must be divided by two repeatedly until neither can be divided any further. The number of mips is always 1 when height_mask's uppermost bit is set.

Counting mips for a 32x16 texture
Iteration Mip Width Mip Height
1 32 16
2 16 8
3 8 4
4 4 2
5 2 1
6 1 1

Notice how on the fifth iteration the mip height reaches one pixel and that this does not change for the sixth iteration (as it is not possible to divide 1 by 2 using integer division). After the sixth iteration, iteration stops because both dimensions have reached 1. For square textures, the two dimensions will reach 1 on the same iteration.

Run-Length Encoding

The game uses additional run-length encoding as a form of lossless compression to reduce the size of many of the stored textures. This compression is only enabled on textures where rle_indicator != 0.

Decompression is very simple, and requires a segment size and an indicator byte as well as the compressed bytes. The bytes are split into groups. Each group can be either segment size bytes, or segment size + 2 bytes. If the group starts with the indicator byte, the next byte is the number of repetitions. The segment size bytes after that constitute the segment to be repeated. If the first byte in the group is not the indicator byte, a segment is read and appended to the output.

decompress(segment size, indicator, compressed) do
  output := new vector
  while byte := next byte from compressed do
    if byte = indicator then
      repetition count := next byte
      segment := take next 'segment size' bytes from compressed
      'repetition count' times do
        add 'segment' to output
      end loop
    else then
      segment := take next 'segment size' bytes from compressed
      add 'segment' to output
    end if
  end while

  return output