no-X said:It is 2x OGSS / 4x RGMS. Not 8x SS.
HEXUS.beans :: ATI produce tool to increase Doom3 scores 'up to 35%' with AA enabled
Posted on Thursday, 13 October, 2005 by Ryszard
ATI Technologies have this morning made a tool available to HEXUS which supposedly improves scores in Doom3 when antialiasing is enabled. Improvements 'of up to 35%' are explicitly mentioned by sources within ATI. The tool seemingly changes the way the graphics card maps its own memory to better deal with handling AA sample data in Doom3's case.
The fix will shortly be rolled into CATALYST 5.11 according to ATI sources and a beta drop of that driver will be made available for testing in due course, before the final WHQL driver from Terry Makedon's CATALYST team is made available for public download in November.
HEXUS are in the process of testing the fix and we'll bring you some scores using the executable tool very shortly. It's unclear if the fix affects other games or whether it solely affects Doom3 via ATI's application detection scheme and their ability to reprogram the GPU's memory controller per application using CATALYST A.I.
More on the tool and the fix as we get it.
neliz said:Why not ask Charryszard Directly?
You've seen that a 512MB X800XL can beat the GTX in demanding circumstances *AND* you know that Doom3, even at UQ, doesn't *NEED* 512mb!
Rys said:Yeah, he's talking about the same thing that I have. It was pushed out with Doom3 as the poster child this morning, but actually paying some attention now, a tool name of "ATIAAMemMapSwitch" suggests it's not just D3-specific as I first wrote.
More coffee please.
Rys said:Yessir, supported hardware for the little tool is X1K only.
Dave Baumann said:Joe - it looks like pre X1K users got their own little bonuses with the 5.10's.
Rys said:Yessir, supported hardware for the little tool is X1K only.
geo said:Yeah, well, Dark Geo never 100% believes those things initially. Too many times in the past IHVs have tried to slide a software fillip off as "new gen only", only to be caught later by the bright boys and their reg hacks. I hate being that suspicious tho, and it would be way cool if this is legit for tweaking that controller.
Edit: What, if anything, does it tell us that it seems aimed generically at OGL? Does that say more about how they did it than what they did? Is it reasonable to assume that OGL apps have some generic similarity in their memory access patterns that doesn't apply to D3D?
Nite_Hawk said:That was my suspicion too. Perhaps it is as you say. I'd like to know more about how this works first though. I suppose the first question might be whether or not they currently handle AA under opengl differently than they do under direct3d...
Nite_Hawk
As far as I was aware it tweaks some registry parameters that alters the configuration of the memory controller.Nite_Hawk said:Did they happen to say what exactly it is doing?
Unclear. AFAIK X1300 lacks the ring bus, but I think the controller logic itself might still have some commonality.Joe DeFuria said:Just to be clear...does this new memory mapping ability only specifically apply to the "ring bus" X1600 and X1800? (Opposed to the X1300 which lacks the ring bus?)