ATI Catalyst 10.7 Major Crossfire Issue

Posted: August 1st, 2010 | Author: | Filed under: Hardware
Tags: , , , , ,

UPDATE: 10.10 Solves it for good.

NEW HOTFIX DRIVER: 10.8b says it fixed the issue, which might have appeared on 10.6. It’s almost perfect, the games are ok, but when exiting some of them, the core is still in 3d speeds. Here’s a list of some games that I tested. I was close to trying TwL‘s drivers, too…

Today I installed Catalyst 10.7 drivers after skipping 10.6 from hearing some horror stories. I’m with a 4870×2 using Vista64. The installation went smoothly, including the HDMI install. (A year ago the HDMI installer failed on one release, worked on the next month’s release.)

After some testing, there’s a severe problem with the 2d/3d detection, so far with the second core.

With DX9 and OGL games, the second core does not switch between 2d and 3d speeds. On a fresh boot, it stays idle after launching a game. This mismatch makes games really stuttery, especially if they are more demanding. The DX9 games I tested were: Borderlands, Call of Duty Modern Warfare 2, Far Cry 2, Lead and Gold, Mirror’s Edge, Moonbase Alpha, Need for Speed SHIFT, Serious Sam HD.

Mirror’s Edge managed to flip the second core into 3d, but then it got stuck after exiting! I checked Borderlands and it was as smooth as it was before (some areas can dip to ~45fps). Lead and Gold finally has a crossfire profile in the drivers, so now that the second core was in 3d mode, the game was nice and smooth without the huge flicker and ~40fps from before.

DirectX 10/11 games I tested (Battlefield Bad Company 2, Red Faction Guerrilla, Shattered Horizon) work just fine. Launching and exiting flips both cores correctly into 2d/3d. Even after Mirror’s Edge locks the second core into 3D, you could reset it back to idle speed by opening and closing a DX10 game.

If there is no hotfix, it might still be possible to take a specific .dll from 10.5 or 10.6 and put it in the Windows system folder so you can still use the new game profiles of 10.7.

Last Modified: October 22nd, 2010

5 Comments »

BFBC2 Map Loading Times

Posted: May 27th, 2010 | Author: | Filed under: Hardware
Tags: , , , , , ,

UPDATE2: You can just put atidxx32.dll into your game folder if you don’t want to install the whole 10.5HF package. Expand it from the installer or use the one I have posted here. Here’s my test again with 10.5WHQL, then placing the dll into the game’s folder.

10.5 – 29s
10.5 – 26s

HF dll – 10s
HF dll – 11s

HF dll – 12s (vsync)
HF dll – 11s (vsync)

OLD UPDATE: Apparently they aren’t in the WHQL 10.5s, no wonder.

ATI Catalyst 10.5 was supposed to fix the loading times for Battlefield Bad Company 2 when using 4800 series cards. I’m a 4870×2, but I didn’t really notice much difference. Maybe my 3.6ghz Q9550 or crossfire made it less noticeable. Oh well, at least it’s not the horror stories of 1 minute or more. I’ll have to check some single 4870 or 4850 user stories to compare, but here are my own results:

Panama Canal empty map and vsync with D3DOverrider, since the game’s option does not work. I load it once from a fresh start of the game, exit to the main menu, then load once more. The total time is from the fade to black on the server browser to the fade to black on the map loading screen. (This second time is from the first fade until the fps goes really high and hard drive usage relaxes.)

10.4 – 36s (25s)
10.4 – 34s (25s)

10.5 – 36s (25s)
10.5 – 34s (24s)
10.5 – 28s (23s) – Decided to close D3DOverrider so that the fps is unlocked, relaunched the game… seems that took off about ~6-8 seconds on the first time load.

I should have tested without vsync on 10.4, but still it’s just a few seconds difference. I wonder when they finally fix the in-game option if it will be any different.

Last Modified: February 14th, 2013

No Comments »