TRK

From SC4D Encyclopaedia
Revision as of 16:17, 4 August 2012 by sc4e>Whatevermind (Created page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


TRK files (Track Definitions) have been known so far simply as sound settings files. These are the files that other things in the game such as UIs, effects, and exemplars link to. They contain direct properties for either a single sound or a Hitlist playlist, and can link sounds together with a respective logic object. Most of their properties are unknown, however.

The following is a partial specification:

Identifier
SoF
Start Signature
Data Block (Comma Seperated)
EoF

The identifier of a TRK file is often 2DKT. It can also be TKDT. This is always the first 4 bytes in any TKD file so its easy to identify them by. TRK files are never compressed.

SOF is the size of the file in bytes after this point. It is a DWORD so it is easy to calculate.

Start Signature is the start of data for a TKD file. Always TKDT in plain text.

Data Block:

The data block is the main settings area of the TKD file. It consists of 30 commas which which separate 29 areas that can hold various types of data. It is unknown exactly what each area represents however.

A temporary key follows,(Number 2),,XA Instance ID,TLO Instance ID,(1 byte val),(2 byte val),,(1 byte val),,(val),(9 to 10 byte val),,(1 byte val),(val),HLS Instance ID,,,,(1 byte val),(val),(val),,,(5 byte val),(val),,,(1 byte val),(1 byte val),

Val means just any value. Items simply called "val" above are between 1 and 4 bytes long. The 9-10 and 1 byte bits mean that's all that has been seen as its value. This is by no means supposed to be a complete list. Commas with nothing between them means nothing has been seen between them yet.

EoF is the end of file signature which is always ETKD immediately after the last comma of the data block.


A Full TKD file might look like this:

2DKTJ...TKDT,2,,0xaa726b1d,0xe9233083,0,32,,1,,50,174302531,,0,1024,0xe9dc0f3e,,,,0,111,1000,,,11111,779,,,0,1,ETKD

While a Typical TKD looks like:

2DKTJ...TKDT,2,,,0xe9233083,,,,,,50,,,,1024,0xe9dc0f3e,,,,0,,1000,,,,779,,,0,,ETKD

Rush Hour trackdefs can now just skip the beginning 8 bytes altogether, though this is not always done.