Posted: December 19th, 2013 | Author: kn00tcn | Filed under: Hardware, Software, Tips/Tutorials
Tags: annoyance, ATI, catalyst, CCC, drivers, fix
Looks like the Catalyst version isn’t being correctly stored for some users on the recent 13.12 WHQL release. This has happened before and it’s absolutely nothing to be alarmed about. The only time this would even matter is when a game or application is using this number as a version check such as Battlefield 4, but that is a problem in itself as you’ll notice that this number is merely a registry string.
As a user, all you need to do to change the number is to go into the registry like the example shown above. You can see how you can put any text in there. Many applications in turn read that string and I say it’s poor practice on their part.
The correct driver version number to look at is the packaging version. You can even see the date in its numbers! This is the only true way to tell if your driver has been installed. You could also simply look at the dates of the driver .DLL files. I can’t believe how many people are falling for this in forums, they’re wasting a whole day reinstalling things, it’s ridiculous. Few people seem to bother with any real (not to mention FAST and EASY) troubleshooting, ironic when they do it right with hardware issues. You don’t replace the tower if a component is acting funny, software is no different.
By the way, the Nvidia Forceware driver is the same. It also uses a string for the basic number that many applications read.
Last Modified: December 19th, 2013
Posted: February 14th, 2013 | Author: kn00tcn | Filed under: Hardware, Tips/Tutorials
Tags: annoyance, ATI, CAPs, CCC, drivers, fix, profiles
So a few months ago, maybe when 12.10 CAP 1 came out, you may have noticed some of the AMD pre-defined crossfire profiles do not appear anymore in CCC (and you know they used to be there). What seems to be happening is that CCC is falling back to the CAP that came with the currently installed driver, which is located in the system folders of Windows.
This is certainly a problem for legacy users stuck on a driver branch and default CAP made in April 2012. Hawken for example only appeared in later CAPs and you need to tell CCC to load the profile since it doesn’t match the game exe.
So what’s the solution? Might as well overwrite the driver CAP with the latest one since we know that’s what CCC is loading.
Let’s start with renaming atiapfxx.blb in your system folders of Windows: C:\Windows\SysWOW64 and C:\Windows\System32. Just put an -old at the end or something so that you can rename back if there is a problem.
Install the latest CAP then go to its folder, something like C:\Program Files (x86)\ATI Technologies\Application Profiles\. Copy atiapfxx.blb and paste it into the two system folders from earlier.
Restart your system and now your CCC will display the new profiles again.
There was a related bug posted on forums where ALL pre-defined profiles were missing for some users of newer cards. I’m not sure if this method can also fix that issue as I’ve never ran into it.
Last Modified: February 14th, 2013
Posted: February 14th, 2013 | Author: kn00tcn | Filed under: Crossfire Scaling, Hardware, Tips/Tutorials
Tags: annoyance, ATI, crossfire, fix, fps, frostbite
Uh so maybe I should have posted this almost a year ago. Sometime around Catalyst 12.3, the framerate in Battlefield Bad Company 2 and Medal of Honor 2009 took a severe hit. I am not sure if Need for Speed: The Run (the other frostbite engine game) took a hit.
As usual, the fix is simply placing an older driver dll into the game folder if you want to keep a newer set for the rest of the system. You’ll need aticfx32.dll and atidxx32.dll if you play in DirectX 10 (why wouldn’t you be anyway?).
Refer to my instructions on how to extract driver dll files from installers.
Last Modified: February 14th, 2013
Posted: March 30th, 2012 | Author: kn00tcn | Filed under: Hardware, Tips/Tutorials
Tags: annoyance, ATI, crossfire, drivers, fix
UPDATE: Here’s an easy fix that you can place in your startup so that the clocks reset automatically without any interaction. Made by kevsamiga1974 from Guru3D forums.
So this has happened before a couple years ago. Luckily it appears to be minor. Just open a close a game and your secondary crossfire gpu should be back to 2d idle clockspeeds. I tried it on a couple DirectX9 games and it worked fine.
Last Modified: September 16th, 2012
Posted: February 12th, 2012 | Author: kn00tcn | Filed under: Crossfire Scaling, Hardware, Tips/Tutorials
Tags: ATI, crossfire, drivers, engine, fix, fps, tweak, unreal
I discovered this some months ago, when vsync and crossfire are enabled in old UE2 games, the combination will cause strange framerates and massive stuttering. So you should disable CF by disabling Catalyst AI, rename the game to ForceSingleGPU.exe, or make a profile in RadeonPro or the profiles feature in CCC (starting from Catalyst 12.1).
This seems to affect the standard UE2 games, not the heavily modified ones like Bioshock or Duke Nukem Forever. It does not matter if you’re enabling vsync with D3DOverrider, an in-game option, or the engine .ini file, it all results in the same stutter. I’m noticing it in Unreal Tournament 2004 for example.
Last Modified: April 27th, 2012
Posted: November 4th, 2011 | Author: kn00tcn | Filed under: Hardware, Tips/Tutorials
Tags: annoyance, ATI, crossfire, drivers, fix, fps, gaming
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.
Last Modified: November 17th, 2011
Posted: October 11th, 2011 | Author: kn00tcn | Filed under: Hardware, Tips/Tutorials
Tags: annoyance, ATI, drivers, fix, opengl
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.)
Last Modified: November 1st, 2011
Posted: October 2nd, 2011 | Author: kn00tcn | Filed under: Hardware, Tips/Tutorials
Tags: annoyance, ATI, drivers, fix, gaming, opengl
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 0x00000116 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.
Last Modified: December 15th, 2011
Posted: October 2nd, 2011 | Author: kn00tcn | Filed under: Crossfire Scaling, Hardware, Tips/Tutorials
Tags: annoyance, ATI, crossfire, drivers, fix, fps, gaming
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.
Last Modified: April 27th, 2012
Posted: August 15th, 2011 | Author: kn00tcn | Filed under: Software, Tips/Tutorials
Tags: annoyance, brink, engine, fix, fps, gaming, server, tweak
You may have noticed how awful Brink feels and looks in motion when playing the campaign or challenge modes, totally different from what your framerate counter displays. Here is how to get around that nonsense. The main idea is 1-you will run a local dedicated server, 2-you set what campaign or challenge to load, 3-you connect to it.
First, install the dedicated server in the tools section of Steam. While that’s downloading, go to the launch options of Brink in your games list and add ‘+set win_allowMultipleInstances 1‘ so that Brink’s executable can run more than once at the same time. (Otherwise you wind up having to launch the game first, then alt-tab to launch the server second.)
Once installed, check the ‘\Steam\steamapps\common\brink dedicated server‘ folder and you should see example .bat files. Edit an existing one, or copy into a new file, adjusting the server name and ports as you want them. Everytime you want to launch the server, just run the .bat file. Push the quit button or type in ‘quit’ in the console for the server to shutdown.
Now it’s time to tell the server what campaign and maps to load. Instead of memorizing server console commands or map names, I would make a .cfg file for every map of each campaign so that it’s very simple to quickly start playing on the mission that you left off in your campaign. Every .cfg file will look like this:
campaign set campaign_#TEAMNAME#
Replace #TEXT# as necessary. You can have spaces in your password, quotes don’t seem to be needed (eg: ‘g_password hello world‘). Change the campaign team name to ‘resistance‘ or ‘security‘. To play the Agents of Change DLC maps, add ‘_dlc1‘ to the end of the campaign line (eg: ‘campaign set campaign_security_dlc1‘).
Bot Difficulty: any: -1, easy: 0, normal: 1, hard: 2
Resistance map names (in order of campaign): aqarium, seetow, terminal, resort, ccity, refuel, shipyard, reactor
Security map names (in order of campaign): aqarium, terminal, ccity, sectow, shipyard, reactor, resort, refuel
Agents of Change DLC map names (in order): lab, founders
Challenges: enable server hijacking then selecting a challenge as 2 player and public should join your server, or any other for that matter (source)
OR I think I managed to make a .cfg that works:
campaign set campaign_challenges
Set your coop player amount to a number between 2 and 4 (eg. ‘applyServerConfig ChallengesCoop2‘ for a 2-player game). Change your password just like a campaign server, and then change the challenge map number to the challenge you want: Be More Objective: 06, Parkour This: 05, Escort Duty: 01, Tower Defense: 03 (eg. to have a Parkour This challenge, the last line would be ‘spawnServer sp/challenge_05.entities‘)
So once you make your .cfg files (or use mine), place them in the ‘\Steam\steamapps\common\brink dedicated server\base‘ folder. Launch your server with your .bat file from earlier and type ‘exec security3‘ if you want to play the 3rd mission of the security campaign and your .cfg file for that mission is named security3.cfg. Then launch the game and go to Freeplay, search for LAN servers, and you should see your local server ready for you to join. If your router’s ports are open, you can have your friends join your server as well. There is a handy script to open and close the ports via UPnP, so that you don’t need to bother opening your router admin settings as long as UPnP is enabled.
Now you can play Brink the way it’s supposed to be! It may seem complicated, but once all this is set, you just exec the .cfg you want from the server console window, nice and simple.
Source for original .cfg file and discussion: Steam Forums
Last Modified: March 3rd, 2012
More information on some of the commands, or using additional ones: BrinkBase.de
You can also type commands in the console window and sometimes the values and what they mean will be displayed (eg. typing ‘si_botDifficulty‘ in the server console).