OBD:TXMP: Difference between revisions
m (wikilinked Data Comlink) |
m (changed family) |
||
Line 1: | Line 1: | ||
{{OBD_File_Header | type=TXMP | prev=TXMB | next=TxtC | name=Texture Map | family= | {{OBD_File_Header | type=TXMP | prev=TXMB | next=TxtC | name=Texture Map | family=General | align=center}} | ||
TXMP is the only known instance type that is interpreted differently by the three kinds of Oni engines on the three plaftorms (Windows, Mac and PS2). | TXMP is the only known instance type that is interpreted differently by the three kinds of Oni engines on the three plaftorms (Windows, Mac and PS2). | ||
Line 483: | Line 483: | ||
<references/> | <references/> | ||
{{OBD_File_Footer | type=TXMP | prev=TXMB | next=TxtC | name=Texture Map | family= | {{OBD_File_Footer | type=TXMP | prev=TXMB | next=TxtC | name=Texture Map | family=General}} | ||
{{OBD}} | {{OBD}} |
Latest revision as of 01:58, 8 December 2023
|
TXMP is the only known instance type that is interpreted differently by the three kinds of Oni engines on the three plaftorms (Windows, Mac and PS2).
The difference between "PC" (Windows retail) and "Mac" (Windows demo and Mac proper) is minor, at least from the point of view of disk storage (the structural difference is limited to runtime fields grouped at the end of the instance, which is why they haven't been documented or implemented in OniSplit). A more obvious difference is that "PC" TXMPs store their pixel data in the .raw file, and "Mac" TXMPs use the .sep file, but this merely amounts to using different fields within the same structure. Thus, even though the template checksums for "Mac" and "PC" are different, both formats can easily be described in common.
The PS2 implementation is significantly different from the other two, in that it systematically uses indexed colors: instead of color being stored in the pixel data itself, each pixel is merely an 8-bit index into a 256-color palette (palettes are stored per-level, in files named level0_palette.pal etc). This difference is detailed in a separate section at the bottom of the page.
Windows and Mac TXMP
Offset | Type | Raw Hex | Value | Description |
---|---|---|---|---|
0x00 | res_id | 01 1F 00 00 | 31 | 00031-rl_1.TXMP |
0x04 | lev_id | 01 00 00 06 | 3 | level 3 |
0x08 | char[128] | rl_1 | name of the texture; unused | |
0x88 | int32 | 00 10 00 00 | 0x1000 | options; possible option flags (from left to right):
|
0x8C | int16 | 80 00 | 128 | width of the image in pixels |
0x8E | int16 | 80 00 | 128 | height of the image in pixels |
0x90 | int32 | 01 00 00 00 | 1 | texture format #1 (RGB555); see below for list of available formats.
|
0x94 | link | 00 00 00 00 | unused | link to a TXAN file; used if this texture is animated |
0x98 | link | 00 00 00 00 | unused | link to a TXMP file that contain the environment map |
0x9C | offset | 20 00 00 00 | 00 00 00 20 | at this position starts the texture part in the raw file (Windows retail only) |
0xA0 | offset | 00 00 00 00 | unused | at this position starts the texture part in the separate file (Windows demo and Mac only) |
0xA4 | char[12] | AD DE | dead | The layout of these 12 bytes is different for the "PC" and "Mac" versions (i.e. Windows retail vs. Windows demo and Mac):
Since runtime fields are grouped at the end, PC and Mac TXMPs are treated by OniSplit under the same template, merely switching between the .raw and .sep links, and blanking out everything past 0xA4. |
0xB0 | char[16] | AD DE | dead | completely unused bytes (not part of the PC or Mac TXMP template) |
- Effect options
- "Shield", "Invisibility" and "Daodan shield" options do not affect the texture reading/drawing in any way. The texture data is still RGB555 or whatever format the texture format field says it is. The effect of these flags is that the engine uses vertex shading with a colour that varies with time.
- Animation time
When using animated textures the image to display is selected using the game time and animation speed. For textures that are used by particles the local (particle) time can be used either to replace or offset the game time.
- Pixel storage order
- Pixels are stored in row-major order, meaning that all the pixels forming a scanline (image row) are grouped together (stored in left-to right order); the rows are stored in bottom-to-top order (see illustration below).
- In the case of the DXT1 storage format, the row-major, left-to-right, bottom-to-top order applies to the 4x4 blocks composing the image, and also inside each 4x4 block for the storage of 2-bit pixels.
- In the case of the I1 format (several pixels per byte), the row-major, left-to-right, bottom-to-top order applies to the 1-bit pixels composing the image.
how it's stored | how you'll see it | |
---|---|---|
PS2 implementation
The TXMP layout is mostly the same on the PS2 platform as on the other two, with differences only in the last few bytes.
- There are 4 extra bytes of storage as compared to a Windows demo and Mac TXMP (which is already 4 bytes larger than a Windows retail TXMP).
- The extra 4 bytes come from a palette index (int32) inserted at 0x90, before the pixel format (which is shifted to 0x94 along with everything else that follows).
- Valid palette indices start at 1. Palettes are stored per-level in level#_palette.pal files. Each palette consists of 256 32-bit colors and takes up 1024 bytes.
- The level#_palette.pal files have between 85 and 179 palettes, not counting the first palette (index 0) at the start of each .pal file, which is always blank.
- The pixel format (shifted to 0x94) has only two variants: 0x10 for opaque textures, meaning 32-bit RGB with ignored alpha, or 0x11 for transparent textures.
- The pixel data (color indices) can be stored either in the .raw file (pointer field at 0xA0) or in the .sep file (pointer at 0xA4). See below for an overview.
Here is how the end of the rl_1 TXMP looks in level3_Final.dat of the English retail PS2 version.
Offset | Type | Raw Hex | Value | Description |
---|---|---|---|---|
0x90 | int32 | 56 00 00 00 | 86 | index of the 256-color palette used by this texture (starts at 0x15800 in level3_palette.pal) |
0x94 | int32 | 10 00 00 00 | 16 | palette pixel format #16 (32-bit RGB, with inactive alpha); the other recurrent format is #17 (32-bit RGBA) |
0x98 | link | 00 00 00 00 | unused | link to a TXAN file; used if this texture is animated |
0x9C | link | 00 00 00 00 | unused | link to a TXMP file that contains the environment map |
0xA0 | offset | C0 05 00 00 | 00 00 05 C0 | position of the pixel data in the .raw file |
0xA4 | offset | 00 00 00 00 | unused | position of the pixel data in the .sep file (unused) |
0xA8 | int32 | 00 00 00 00 | 0 | always 0; supposedly the same "material type" (set at runtime) as for Windows demo and Mac |
0xAC | char[4] | AD DE AD DE | dead | supposedly the same texture name pointer (used at runtime) as for Windows demo and Mac |
0xB0 | char[4] | AD DE AD DE | dead | supposedly the same rendering optimization flags (runtime) as for Windows demo and Mac |
0xB4 | char[12] | AD DE | dead | completely unused bytes (not part of the template) |
- Alternative use of .raw or .sep storage
Unlike for PC or Mac game data (where pixel data is stored exclusively in .raw or exclusively in .sep for all TXMPs), PS2 TXMPs use .raw and .sep storage alternatively, depending on the TXMP. The engine apparently uses the .sep pointer only if there is no .raw pointer (or vice-versa).
Examples of textures using .sep storage are: all fly-in portraits; all splashscreen components; some illustrations in Konoko's Data Comlink (namely, combat move illustrations and item illustrations; objectives and weapon illustrations use .raw storage).
Environment/character/particle TXMPs seem to be using .raw storage consistently (not checked beyond level1_Final). As a notable anomaly, .sep storage is used for the following three textures (console screens) in level0_Final: _CON_SAVEGAME (main TXMP only; the animation frames use .raw storage), _CON_SAVEGAME_USED, _CON_USED.
Notes
- ↑ Storage format 7 was jointly used by OniSplit, Daodan DLL and the Intel Mac build to allow for 32-bit textures with transparency - most importantly experimental lightmaps, see HERE. However, the actual storage format used in this case was RGBA_Bytes (type 11), and type 7 was used by mistake.
- ↑ Storage format 11 (RGBA_Bytes) was effectively implemented by OniSplit to allow for 32-bit textures with transparency - most importantly experimental lightmaps, see HERE. However, it was mislabeled as type 7 (ARGB8888) by OniSplit, Daodan DLL and the Intel Mac build, which resulted in byte swapping and the requirement of authoring PC and Mac versions of TXMPs.
ONI BINARY DATA |
---|
TXMB << Other file types >> TxtC |
TXMP : Texture Map |
General file |