UPDATE: 11.11 has fixed both Killing Floor and Red Orchestra. This fix is not needed anymore.
Looks like Catalyst 11.10 has extremely high gpu usage in Killing Floor, so it struggles to maintain a solid framerate when there’s any action on screen.
No problem, put 11.9′s atiumdag.dll into your ‘\steamapps\common\killingfloor\System‘ folder.
The original Red Orchestra is in the same situation.
UPDATE: Apparently 11.10 is now fine with the apps and games that the Rage drivers broke, so you’d want to update to the final release. Some people’s Rage turned blue, so those people should just use the atioglxx.dll from the Rage driver that works best for them (put it in Rage’s game folder): 11.10p v1, 11.10p v2, 11.10p v3.
I’m seeing reports of people saying that the Rage drivers broke all other OpenGL applications or games. No problem, there are two ways to quickly fix this for yourself.
You can go back to having 11.9 WHQL installed for the system, then simply place atioglxx.dll from the 11.10p Rage driver into Rage’s folder. (Wherever rage.exe is located, I don’t have the game.)
Or if you just want to fix 1 or 2 things while keeping the 11.10 preview installed for the system, just put atioglxx.dll from 11.9 into the game or application folder of what you want to fix. Java based games like Minecraft or Spiral Knights actually run java.exe, so you will put the dll into Java’s ‘bin’ folder instead.
I put in a couple other OpenGL driver files, atigktxx.dll and atiglpxx.dll, just in case if using the single atioglxx.dll alone did not work.
By the way, these are 32-bit dlls for 32-bit games/apps/Java. As for issues in Rage itself, I can’t do any tests since I don’t have the game. (Which would be useful since I’m a 4870×2 and I hear 4 series has the most problems at the moment.)
UPDATE: 11.12 seems to work fine, this should be good for 6 series cards that can’t use old dlls.
Not sure how widespread this is, but on my 4870×2, ETQW will freeze after a few seconds of playing and then BSOD with “Attempt to reset the display driver and recover from timeout failed.” The STOP code is 0×00000116 with atikmpag.sys as the faulting module.
This happens on… let’s say recent drivers. I can successfully play without issue using the handy 10.4 atioglxx.dll, which is the latest most stable driver for older OpenGL versions or games. I also used atigktxx.dll just in case. Simply place them into the main ETQW folder.
I’m also seeing that Doom 3 has a driver reset after a minute of play or when vsync is enabled, so the 10.4 files fix that as well.
After installing AMD Catalyst 11.8 drivers, I noticed Borderlands was not performing properly on my 4870×2. 11.9 or 11.10p do not appear to have fixed it.
No problem, just drop 11.7′s atiumdag.dll into the ‘Borderlands\Binaries‘ folder. Simple problem, simple solution.
UPDATE 2: Now that you can set custom profiles in CCC, you might be able to force GRID’s profile for Serious Sam HD. (I don’t have Sam installed right now.)
UPDATE: It seems radeonpro is NOT applying itself, so I guess the only options are to stay on an older CAP, find a CAP switcher, get a faster single GPU card, use a crack (which would disable achievements and multiplayer), somehow trick steam into loading renamed .exes (could an NTFS junction work?), or have Croteam make us a copy of the game exe that’s named as GRID.exe, since attempting that yourself just closes the renamed .exe and launches SamHD.exe.
The latest CAP disables crossfire in the Serious Sam HD games due to crashes happening near water. This should be a game issue that also affects SLI. I assume The Second Encounter will act the same as my testing of The First Encounter.
But if you don’t mind the possible crashing and want to get your framerate back to where it was before, just force the Race Driver GRID profile in radeonpro.
Simply rename UDK.exe found in the Bin32 folder to AliceMadnessReturns.exe. Make sure to have the latest CAP, and it still works even with my sparkling spots fix, which uses 11.2 dlls.
The Alice profile is almost as fast as other profiles like Crysis 2, but without flickering of the water or other artifacts.
Here’s a similar situation to the Cities In Motion issue, this particular CAD software also has a problem running on ATI/AMD drivers newer than Catalyst 10.4, or at least 10.4 looks reliable enough to function properly. After launching, amdkmdap has a driver reset when the 3d rendering panel appears, crashing the application.
The fix is nice and simple, just place the appropriate OpenGL driver into the program’s folder where CityEngine.exe is.
If you have any other OpenGL game or application that is crashing after 10.4, try this fix or the Cities in Motion one.
Your card should support 10.4 drivers in the first place, I have no idea what you would do if you’re using one of the latest Radeons or if you’re using an nVidia card.
It appears every driver after Catalyst 11.2 has a bug in Unreal Development Kit. I would have noticed this sooner if I used UDK more often this year. I don’t know how many cards this affects, it might just be for older cards. I’m on a 4870×2.
Anyway the solution is simple, put 11.2′s dx9 dlls into the binaries folder of UDK. Installing the whole 11.2 driver set for the whole system is not a useful workaround, since most people would need fixes or performance gains seen in newer drivers.
So grab the dlls, then place them into the appropriate folder:
For the 32bit editor and game: put atiumdag.dll into \Binaries\Win32 For the 64bit editor: put atiumd64.dll into \Binaries\Win64
If you’re using RadeonPro to force crossfire profiles, it will overwrite the dll that you placed, so you’ll have to use the driver version compatibility feature to use 11.2′s dll. I would instead just make a copy of and rename the 32bit UDK.exe into AliceMadnessReturns.exe to get crossfire scaling when launching the game.
Once again, like the Section 8: Prejudice trick, grab RadeonPro (since it’s a steam game) and simply use the Half-Life 2 crossfire profile. Apparently other profiles flicker or do not scale as well.
Credit goes to spyre who noticed this… months ago. I’m not sure why it’s still not in the CAPs or drivers.
After a fair amount of testing, the Dark Void profile gives the performance boost of the FEAR profile without the flickering.
So what you need to do is grab RadeonPro so you can make a profile for the game. You can’t simply do the exe rename trick, as it has a launcher that blocks you from starting from the game exe directly.
Once inside RadeonPro, push the ‘add a new profile’ button and select S9-Win32-F.exe from the Binaries/Win32 folder of the game. Go to the tweaks tab and click ‘manage custom profiles’, then add Dark Void as ‘ShippingPC-SkyGame.exe‘. Now to fix the launcher issue, go to the launcher tab and select ‘Games for Windows Live’ from the dropdown, then pick the actual launcher exe, which is S9.exe in the root folder of the game.
This should do it until a profile gets built into the drivers. Enjoy!
