Topic on Talk:AMD Catalyst Control Center
This is a permanent link to the first version of this post.
You can view later versions on the post history page.
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)
Instructions (were present a couple of years ago) (use
-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
- It seems the driver is programmed to look for an additional
C:\ATI\ACE\APL\User.blb
. This is good, since it should survive driver updates
- It seems the driver is programmed to look for an additional
%LOCALAPPDATA%\AMD\CN\gmdb.blb
can be instead opened with Notepad and stores Crimson control panel profiles- Different MSAA hacks can be tried by renaming executables
- 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]