Talk:AMD Catalyst Control Center

About this board

Mirh (talkcontribs)
  • atiapfxx.exe can be used to convert atiapfxx.blb in order to force in specific executables certain game profiles, hardcoded in graphics dll (and until 13.12 in atiogl.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"


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 in HKEY_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?).
  • %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

Zzeleznez (talkcontribs)

With atiapfxx.exe successfully extracted blb to xml (size 1.45mb) and edit it but when i try to convert back got an error "mxml: Character entity "" not terminated under parent <application>!" Tried also blb from catalyst 15.11 and got same error. Solved: just replace "&" symbols in .xml to any other for example "n". Also latest atiapfxx.exe I found was in Crimson 17.9.3.

Reply to "Compatibility tips"
Mirh (talkcontribs)

Quite Legacy cards with new-ish drivers and OS [caveat?] [note] [log bug]

TeraScale mobile dedicated GPUs with Intel IGPs

Very latest driver for pre-GCN hardware [overview]

EDIT: VSR can be forced on a lot of cards
EDIT2: folks on Windows Vista can get 17-months-newer drivers with minimal hacks

Reliable firm confirmed milestones

10.2 - latest driver supporting everything that ever lived

14.4 - latest driver supporting fixed switching

16.1.x branch (see above) - latest driver supporting pre-GCN

17.7.1 - latest to officially support W8.1, but it can be hacked

18.9.3 - latest 32 bit driver

Reply to "Modded drivers"
Mirh (talkcontribs)

Usually located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video

These are older examples. Hex checking dlls or procmonitoring should also be possible

EDIT-trivia: basically the same structure can be found in linux closed driver, under /etc/ati/amdpcsdb

Garrett (talkcontribs)

Registry information is also listed in the Catalyst Control Center under Information, Software.

Mirh (talkcontribs)

Which to be honest point to another registry key (with everything identical) under HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\ but whatever..

Anyway cool, thanks for the tip

EDIT: there's also this pretty good software to tinker with stuff [partial guide]
EDIT2: around 2013 some stuff was moved left and right between system-wide registry and game-specific profiles.

Reply to "Registry settings"

It's still called Catalyst Control Center if you have an Intel CPU

Z Overlord (talkcontribs)

only on systems with an AMD CPU and an AMD GPU is it called AMD VISION Engine Control Center

Reply to "It's still called Catalyst Control Center if you have an Intel CPU"
There are no older topics