In a near future we may have both options, overclocking through overdrive and more advanced overclocking using MSI Afterburner I don't think so, I think it's better leave those duties to more specialized tools like MSI Afterburner. You're welcome, Darren Hodgson, I'm glad you (and all of you that are reporting bugs here) kept trying RadeonPro, without bug reports from the community we can't iron out those bugs if everyone just waits for a stable version I got why you end with up cloned profiles in ATT, that's because you already had them created in ATT then created them again in RadeonPro. I'll make RadeonPro search for the registry entries and only update forced vsync/triple-buffering registry keys instead of creating a duplicated registry key which results in a duplicated profile in ATT. I think you're right, raphook.dll may be using 3D settings (AA/AF/etc.) based on settings you've set in ATT overriding RadeonPro 3D settings. I'll do a little research to see if that's the case. Ok, I'll wait for the screenshot, it's a bit hard to know what's going on without the exact error message. I would love to expose AA/CFX compatibility flags like nHancer does, but unfortunately Catalyst driver don't work the same way Geforce driver does. Geforce drivers use a NvApps.xml file which contains entries like below Code: <PROFILE Label="arma2"> <APPLICATION Label="arma2.exe"/> <PROPERTY Label="aa_behavior_flags" Value="0x00000001" Default="0x00000001" Itemtype="predefined"/> <PROPERTY Label="multichip_rendering_mode" Value="0x02506405" Default="0x02506405" Itemtype="predefined"/> <PROPERTY Label="hybrid_rendering_mode" Value="0x00000009" Default="0x00000009" Itemtype="predefined"/> <PROPERTY Label="multichip_dx10_rendering_mode" Value="0x000240F5" Default="0x000240F5" Itemtype="predefined" OS_TYPE="Vista"/> <PROPERTY Label="hybrid_dx10_rendering_mode" Value="0x00000009" Default="0x00000009" Itemtype="predefined" OS_TYPE="Vista"/> <PROPERTY Label="d3d10_aa_feature_bits" Value="05000000" Default="05000000" Itemtype="predefined"/> </PROFILE> I'm trying to figure out atiapfxx.blb file structure, If I can do it maybe we can start creating profiles with true AA/CFX compatibility instead of trickering Catalyst by renaming executables... BTW, for Star Wars The Force Unleashed you can try Brothers in Arms: Hell's Highway profile to enjoy forced AA and CrossfireX. For BLUR you can just set MVPUMode to AFR and tick Force High Priority, I've found that it's enough to make it run at 60 fps almost all the time. Without Force High Priority frame rate dips to 40'ish fps sometimes.