atiapfxx.exe
can be used to convertatiapfxx.blb
in order to force in specific executables certain game profiles, hardcoded in graphics dll (and until 13.12 inatiogl.xml
for OGL)
-hiddenhelp
)atiapfxx [-k] [-s filename] [-p pathname] [-v version number] [-r] -b filename -k To sign or resign the AMD binary file - Optionally use -o to specify binary name -s filename of the XML content - Can be used with -p -k and -o - Use this parameter multiple times to merge XML Files. - Use this parameter exactly once if -r is specified. -b filename of the file to contain the Binary content. - Required in all cases except system/oem binary to xml conversion. -l filename of the progress log. -p to include all .XML files in the specified directory - may be used with "-s" -r to reverse the conversion, Binary to XML, instead of the default, XML to Binary. -sys used with -r option, convert system database to XML. -oem used with -r option, convert oem database to XML. -user used with -r option, convert user database to XML. -ph used with -r option, print placeholder entries. -v to print version string from the binary file -u to specify this is a user XML file -o to dump blob content to log file, need to specify blob file name with "-b" -c specify Version string to use for blob file. Used with string following option: - "-c 8.77" Usage: To convert User XML File(s) into a User Binary File, use: - atiapfxx -u -s file1 [-s file2 ...] -b fileX To convert AMD XML File(s) into an Unsigned AMD Binary File, use: - atiapfxx -s file1 [-s file2 ...] -b fileX To convert AMD XML File(s) into a Signed AMD Binary File, use: - atiapfxx -k -s file1 [-s file2 ...] -b fileX To Sign or Re-Sign an AMD Binary File, use: - atiapfxx -k -b fileX To convert a Binary File to an XML File, use: - atiapfxx -r -sys -s file1 To convert all files in the current directory, use: - atiapfxx -p filepath -b fileX
- The program is dumb as a brick, and it seems only to be able to decode blbs it can find in hardcoded paths. These are in order:
%WINDIR%\SysWOW64\atiapfxx.blb
, string OemBlobFile inHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ATI\AppProfiles
, and%LOCALAPPDATA%\ATI\ACE\APL\User.blb
- Take also note atiapfxx may even always be 32-bit, but in a 64-bit OS the driver at runtime will instead look for the corresponding paths (plus the additional
C:\ATI\ACE\APL\User.blb
I think?).
- The program is dumb as a brick, and it seems only to be able to decode blbs it can find in hardcoded paths. These are in order:
%LOCALAPPDATA%\AMD\CN\gmdb.blb
can be instead opened with Notepad and stores the non-3D part of Crimson control panel profiles EDIT:gmrevert.blb
also seems to exist- Different MSAA hacks can be tried by renaming game exes (or tinkering the blbs if you are bold enough)
- Faking Device ID can help unlocking wickedly disabled effects
- Z-buffer bugs can be somewhat worked around
Actual problems with modern applications: [1], [2], [3], [4?], [5], [6], [7], [opencl]
True story