DeTex Version 1.xx by Mikero
See ReadMe General
See fixes
Detex lists, compares or creates the Texheaders.bin from paX files.
Note that pax means paa or pac. With a minor exception that will never be encountered anywhwere except flashpoint's indexed-pac files, they are treated identically.
Brief description of what a texheader is.
A texheader contains brief information about every paX file in the starting directory (if any), and all subsequent folders. It is used in conjunction with the creation of a pbo, and would normally reside in the root folder of that pbo.
Unlike all other file\references in bis, this file contains addresses relative to where the texheader is located. In effect, relative to the root of the pbo, not the prefix.
The contents of a texheader is quite small and contains the essential details of
where each mipmap is in each paX,
the type of paX format (dxt, argb1555, etc)
the all important type of pax file _suffix (_co,_ca, _nohq, etc)
texheaders were introduced in the game engine, as of operation arrowhead. Prior to this, the same information was generated during the game.exe load time.
Syntax:
Unless explicitly overridden, the default filename for reading or writing is 'texheaders.bin'
DeTex [-options] infileOrFolder [OutfileOrFolder]
options: caSEInseNsitive
Listing is default
-P Dont pause
-M ake
-MN make noisy
-C ompare
Usage examples:
Analyse and display
Analyses the texheader and displays on screen, and any subsequent texheaders in the subfolders.
1)detex P:/Some/Project/Folder[/texheaders.bin]
texheaders is assumed if not stated.
2) detex Z:/DZ
will dump the contents of all texheaders in the DZ folder and beyond
----
Make
detex -M p:/my_pProject/Folder [destination\FILE]
creates a teheaders bin at the root of a project\folder
optionally, this file can be written elsewhere (but serves no real purpose)
----
Compare
detex -C this\folder that\folder
compares one (or several) texheaders agaisnt each other. Useful for large teams wanting to know if sommething has changed from the original.