AMD Catalyst (Modified Build)

[marcosamerio]

Hi

You ll release a 32 bits version?

Bye

[TwL]

Well, ain't planning it basically x86 is a bit different in this case as base '%windir%\system32\' is a singled out folder there is no mix up like in x64 or at least I am not aware there would be such issues in 32-bit OS like there is in x64 which this pack correlates.

This mod was never about performance, but functionality fix / correcting the v10.x mess up by combining right versions to work in everything end user would want working. As I see it we have more power in, atm, equipment on market than on small village and drivers blocking to use the power. As what goes to gaming we have no games to play which would utilize the power and this "xx% improvement to game X" is just some new idioticy. What I mean they are not fixing 'drivers' anymore they fix unique patches to software which is incredibly stupid.

[Hans Dampf]

Hi Twl,

I was so happy when I saw your post.
I know this has been a lot of work for you to test all of the stuff and bring it together! You did a great job!

I am running Quadfire 5970 + Eyefinity + 9600GT
Thought I get it fixed now.
Same problem for me as you described: The 9600GT will be display 1 after reboot. So it crashes the Eyefinity -> just 3 black screen or loss of icons (after adding the extended blacked out display) - first works - after reboot crashes

So I tried your Installation now several times. Followed your steps for deinstallation and reinstall. All is fine. I just done get PhysX enabled with the 257.15. - just no option for it and GPU-Z and Fluidmark and Vantage tell me: No Physx!
With the PhysX modded 196.21 it worked just fine - but causes crashes after reboots.
Don't know why I don't find the Physx-Option in NVidia-Control Panel - neither the NPT will give a result.
NVidia control panel shows Physx correctly installed in the drivers section and CCC works fine.
What can I do?
Here is a screeny:

[TwL]

Originally Posted by Hans Dampf

Hi Twl,

I was so happy when I saw your post.
I know this has been a lot of work for you to test all of the stuff and bring it together! You did a great job!

I am running Quadfire 5970 + Eyefinity + 9600GT
Thought I get it fixed now.
Same problem for me as you described: The 9600GT will be display 1 after reboot. So it crashes the Eyefinity -> just 3 black screen or loss of icons (after adding the extended blacked out display) - first works - after reboot crashes

So I tried your Installation now several times. Followed your steps for deinstallation and reinstall. All is fine. I just done get PhysX enabled with the 257.15. - just no option for it and GPU-Z and Fluidmark and Vantage tell me: No Physx!
With the PhysX modded 196.21 it worked just fine - but causes crashes after reboots.
Don't know why I don't find the Physx-Option in NVidia-Control Panel - neither the NPT will give a result.
NVidia control panel shows Physx correctly installed in the drivers section and CCC works fine.
What can I do?

HD5970:
Well the problem with the 'HD5970' is that the last functional driver level is so old here. AMD/ATI fixed a lot on these cards specifically on versions
10.4->10.5. So, ain't gonna be easy setup in any case, if you get it working clean 1 time it will work on everything after.

When you install this card, before you start open up 'run...' > 'devmgmt.msc' > disable the NVIDIA card > then install > after you get all the ATI stuff in
straight line > enable the NVIDIA side and progress below.

(I honestly don't think there is an fully functional solution, if the Catalyst v10.3b can't display correctly. As any v10.4-v10.5 will break the OpenCL
functionality leaving only one choice and that's to have newest v10.5(v8.732) driver for HD5970 which this package doesn't have. )


PhysX you probably will get working:
As for PhysX (Turn off NVIDIA control panels & Tweakers & Fluidmark windows completely) use the 'Tweaker' there is disable the PhysX > reenable
it. on Forceware '257.15'(to not extend display you still need GenL v1.03 Hybrid mod "1.03 was made to make 'fake display' so might bug") this should
work. With '196.21'(you want to have v1.02, but v1.03 mod will work also.) you have to have display/fake display adapter attached while installing.
Important:
Do not switch an display cable from ATI device to NVIDIA device for this purpose, if you absolutely don't have an other display cable/fake adapter to
attach leave it empty and use 1.03 patch in this case.
Prefer these instead of 196.21:
Forceware v196.34 Beta

(make sure after you've install there's no 'NVxxxxx.exe' files running while running an physX patch/hack and that you install in correct order + never
run an PhysX application before final reboot and you cannot change physX settings while application using it is running. ATI(this package) > NVIDIA >
PhysX(v9.10.0222) > patch/hack > reboot)

(In absolutely extreme issue on screen. hell, disable the NVIDIA card temporary on device manager > check for 'NVxxxxx.exe' > then install & patch
"not suggested, but" works if everything else fails.)

-edit-

As for display:
Do this as I do, if you use an fake display adapter OR Display attached on NVIDIA side (drag-n-drop the NVIDIA display to least used corner):


It's a dirty trick(from catalyst v10.2 and below), but works for 'flickering' if such and if there's an 'real' or 'fake' display attached.

[TwL]

^
@Hans Dampf

hope that helps.

Sorry had to edit it a lot to explain the idea behind some things on installation progress to hopefully give you better picture where we are at and maybe you could just reinstall PhysX & disable enable correctly according to that without reinstall even, if you find where it went wrong.

[Hans Dampf]

Hi TWL ! Meanwhile I tried and have some success with 257.15+Physx and no fake adapter.
Nvidia shows now Physx enabled but Fluidmark runs on two ATI GPU's!! Weird stuff.
See here:


You give me great support man! I will try your other proposals next.
Strange thing: Fluidmark on CPU: 28FPS but on GPU 19FPS
Checked Vantage PhysX and this one pushed PhysX as normal!

[TwL]

yeah, but in progress you lost ATI side. you see the 'DirectCompute' missing on NVIDIA side that's the ATI side over writing the correct order installed drivers there

use this guide I wrote to some other fellow yesterday to clean the ATI crap out (Although since you already got the correct driver hopefully haven't tested anything else shouldn't need full clean-up.):
http://forums.guru3d.com/showpost.ph...3&postcount=22
(and don't forget that ATI Stream tools still have to be uninstalled as usually.)

It's a bit:


but with the above advice followed exactly you should get it functional flawless as I see the ATI Display driver is working correctly which is really good news.

(please use Fluidmark v1.1.1 to test. The new v1.2.0 uses Multithreaded PhysX which is always CPU in first core even while there would be NVIDIA it won't tell you it's there. v1.1.1 will tell you either 2 choises 'software' = CPU or 'Hardware' = NVIDIA card)

-edit-

Strange thing: Fluidmark on CPU: 28FPS but on GPU 19FPS

Yeah, that's CPU alright.. You should be getting near 200FPS and around 20-60SPS GPU.

[Hans Dampf]

I wil give it at try!
So clean up again completely and start from the beginning, right?
After years of searching I finally found the god of bits and bytes, who can make my system work!
Glad to meet you here! I am very much impressed!

[TwL]

clean-base is half the job, but not absolute most, if you haven't installed v10.4 or v10.5 drivers. (problem is, if you have ATI installers are so crap they don't always overwrite newer files with older which you need).

yeah, do it once well and according to advice I started on and it'll be great setup. Just need to follow that word by word:
http://forums.guru3d.com/showpost.ph...4&postcount=29

-edit-

Perhaps on more advice on NVIDIA side (you can correct this after all ATI stuff etc etc if you want it won't mess anything to update/modify NVIDIA
side when ATI is working and inside):
any v197.xx or v257.xx drivers you will lose ability to view NVIDIA GPU Usage on 3rd party tools and if NO display of
any kind is attached you will also lose Memory Usage on tools like MSI Afterburner. Drivers although works just fine hardware physX.

Last driver you get GPU usage is the suggested 196.34 beta, but even on that you need 'some' adapter attached to see memory usage as it's readed
from display. PhysX performance is the same no matter do you install 196.xx, 197.xx or 257.xx.

[TwL]

Just tested exact adviced setup here took an picture:


FluidMark v1.2.0:


Using 196.34 beta + PhysX patch v1.02 there with basic display setup added HDMI to ATI card & DVI from same display to NVIDIA. Also tested on fake adapter. Took this to demostrate the concept 'having' GPU/Memory utilization rocks ;P

NVIDIA control panel has 'PhysX section' so you don't need the 'tweaker'.

[Hans Dampf]

Using 196.34 beta + PhysX patch v1.02 there with basic display setup added HDMI to ATI card & DVI from same display to NVIDIA. Also tested on fake adapter. Took this to demostrate the concept 'having' GPU/Memory utilization rocks ;P

Hi again TwL !
Do you think that this will work with 3 screens under Eyefinity??
I could only attach one cable to the GT9600 - maybe two.
The point is the extended display on three screen but Geforce only attached to one of them.
For that reason I guess, the fake display with 196.34 + Patch 1.02 should work better - because I can extend the fake display to all three screens.
-> Or just skip the fake display and do as I learned yesterday with the 257.15?

Another point: Yesterday night I did some benches with the setup I came so far. (Thought before I delete the drivers again clean, I can play with it until I go to bed) Vantage was running like overclocked Very nice framerates!
- so I think: why not overclock it as always. Made a profile in CCC with my commonly stable 950 /1150mem @ 1.250V and got BSOD's, GSOD's and other crashes. So I clocked down - whatever clocks and voltage I tried .. crash.

My Point: Is it possible to overclock based on your setup or is overclocking screwed with it?
Maybe to mention: Since I am commonly setting the voltage in the CCC Profile I uninstalled Afterburner to avoid crashes. Is this the wrong way?

Thanks again man for helping me out with your great knowledge!
Wanna get this setup perfect and will not give up until!

[marcosamerio]

TWL im using your "extra_functions_catalyst.reg" to enable
* Full DVXA encoding / decoding with GPU(s) (MPEG2 & AYUV0 included)
* Temporal AA (Doubles AA effect on "every second frame?")
* High Quality Anisotropic Filtering (Supposed to improve quality)
* Hardware Geometry Instancing

can u put please a tweak reg to enable in CCC the function to change the Flip Queue size, i dont use ATT because i dont like it, and a last thing the option called "Optimize Pixel Shader Code" is on by default on the drivers or must be tweaked or enabled?

Bye and tanks

[MerolaC]

Originally Posted by marcosamerio

TWL im using your "extra_functions_catalyst.reg" to enable
* Full DVXA encoding / decoding with GPU(s) (MPEG2 & AYUV0 included)
* Temporal AA (Doubles AA effect on "every second frame?")
* High Quality Anisotropic Filtering (Supposed to improve quality)
* Hardware Geometry Instancing

can u put please a tweak reg to enable in CCC the function to change the Flip Queue size, i dont use ATT because i dont like it

Bye and tanks

+1 on this request, that would be awesome!

[TwL]

Originally Posted by Hans Dampf

Hi again TwL !
Do you think that this will work with 3 screens under Eyefinity??
I could only attach one cable to the GT9600 - maybe two.
The point is the extended display on three screen but Geforce only attached to one of them.
For that reason I guess, the fake display with 196.34 + Patch 1.02 should work better - because I can extend the fake display to all three screens.
-> Or just skip the fake display and do as I learned yesterday with the 257.15?

Another point: Yesterday night I did some benches with the setup I came so far. (Thought before I delete the drivers again clean, I can play with it until I go to bed) Vantage was running like overclocked Very nice framerates!
- so I think: why not overclock it as always. Made a profile in CCC with my commonly stable 950 /1150mem @ 1.250V and got BSOD's, GSOD's and other crashes. So I clocked down - whatever clocks and voltage I tried .. crash.

My Point: Is it possible to overclock based on your setup or is overclocking screwed with it?
Maybe to mention: Since I am commonly setting the voltage in the CCC Profile I uninstalled Afterburner to avoid crashes. Is this the wrong way?

Thanks again man for helping me out with your great knowledge!
Wanna get this setup perfect and will not give up until!

To 9600GT cable question:
No, basically if you do not want to attach cable and run with lets say PhysX patch 1.03 you would want to add the cable from same display (not in use,
but as long it detects it's attached it's ok) until end of NVIDIA side install. You can then disable the NVIDIA adapter on device manager > remove the
cable > reenable NVIDIA and there would be an Fake display (from PhysX hack 1.03) working without memory loss. memory loss occures when there is
an display attached.
NOTE: you will lose the monitoring capabilities of 9600GT in this case.

Attaching an real display to 9600GT is pointless as it is near 20 times weaker than your setup on ATI side would only harm the performance as NVIDIA
card would drag down the ATI cards by too slow rendering.

Overclocking:
No problem with overclocking. The CCC 10.5 has an bug in Overdrive so 3rd party tools like MSI Afterburner(if volterra chip in card) or AMD GPU Clock
tool(if no volterra chip) would be ideal as CCC will come up with 2D bug of setting clocks always to 400/1200 etc.

However, none of that should 'crash' as you say your setup did. Unsure if this is Catalyst 10.3b specific bug(this does not happen on single ATI+NVIDIA) or just system not capable handling it. I
cannot replicate this in here. So I am sorry to say you are on your own on this one.

Originally Posted by marcosamerio

can u put please a tweak reg to enable in CCC the function to change the Flip Queue size, i dont use ATT because i dont like it, and a last thing the option called "Optimize Pixel Shader Code" is on by default on the drivers or must be tweaked or enabled?

The problem is ATT enabled 'FlipQueueSize' = ineffective through catalyst 10.2->10.5 command. In other words the registry entries doesn't do anything
on ATT when you set flip queue size. I know the flip queue is there somewhere, but in, atm, drivers I can't find any way to enable it (I mean
REAL effective enable it or lower it).

I could enable a lot of none sense registry entries hell I could even paste them here, but the point is to have 'functional' tweaks not myths that
doesn't work.

[marcosamerio]

Originally Posted by TwL

The problem is ATT enabled 'FlipQueueSize' = ineffective through catalyst 10.2->10.5 command. In other words the registry entries doesn't do anything
on ATT when you set flip queue size. I know the flip queue is there somewhere, but in, atm, drivers I can't find any way to enable it (I mean
REAL effective enable it or lower it).

I could enable a lot of none sense registry entries hell I could even paste them here, but the point is to have 'functional' tweaks not myths that
doesn't work.

Im using 10.3b 32 bits too and when i enable "Geometry Instancing" i get a boost around 3 - 5 fps in assasing creed 2 and dow 2, how other registry tweaks can be enabled to perform or personalize the suit dirvers and a last thing the option called "Optimize Pixel Shader Code" is on by default on the drivers or must be tweaked or enabled?


Bye and thanks for reply

[TwL]

@marcosamerio

option called "Optimize Pixel Shader Code":

Failed to answer this as readed the earlier FlipQueueSize sorry. It's always bad to 'Optimize anything' when it comes to textures or Shaders. Basically all ATI does there is modify original content = loss of quality. However, the idiotic GPU crap ATI and NVIDIA keeps pulling to people "xx% improvement on gameX" style of tweaks are completely dependent of this kind of functions.

So, if there is an optimization build by ATI in this case you probably would want it still to be enabled to improve performance.

Other?:
Fail now to understand your question, but in a lowest of sense. 'Video' control register is where GPU settings mirrors them self to 3 section > GPU driver section when enabled.

you really lose me on "how other registry tweaks can be enabled" <- what other ?

-edit-
@marcosamerio

As for general here now note. This package I created is not build to 'perform' it is for functionality, if you are looking for top end quality and performance as I said to many others. Download and use the latest Catalyst v8.40.0 drivers.

[marcosamerio]

Originally Posted by TwL

@marcosamerio

option called "Optimize Pixel Shader Code":

Failed to answer this as readed the earlier FlipQueueSize sorry. It's always bad to 'Optimize anything' when it comes to textures or Shaders. Basically all ATI does there is modify original content = loss of quality. However, the idiotic GPU crap ATI and NVIDIA keeps pulling to people "xx% improvement on gameX" style of tweaks are completely dependent of this kind of functions.

So, if there is an optimization build by ATI in this case you probably would want it still to be enabled to improve performance.

Other?:
Fail now to understand your question, but in a lowest of sense. 'Video' control register is where GPU settings mirrors them self to 3 section > GPU driver section when enabled.

you really lose me on "how other registry tweaks can be enabled" <- what other ?

-edit-
@marcosamerio

As for general here now note. This package I created is not build to 'perform' it is for functionality, if you are looking for top end quality and performance as I said to many others. Download and use the latest Catalyst v8.40.0 drivers.

Thanks a lot TwL for all, i cant find the catalyst 8.40.0 ¿wich version is? im using windows 7 32 bits

Bye

[TwL]

OK, new Experimental build is up. Updated main topic now.

Updates:
* I build an experimental build which uses new drivers (v7.32.1) which only replaces the cal x86 dlls (NOT the performing driver) from v10.3b to v10.5 hotfix.
* Installer was dumped up to date from v10.6 (alpha?) anyway v3.0.775.0 (old one was v3.0.774.0).
* Included 'FlipQueueSize' in manual reg entry tested to be functional enabled now. No Control Panel access. To change you need to 'CCC Runtime restart' and re apply the .reg file.
NOTE: NONE of the applications (not even DWM can be running if you restart the runtime instead of reboot)

What this should fix:
* Crossfire issues
* Performance is 10 to 1 on new drivers against old on hundreds of titles and some of fixes like mouse cursors etc etc in this edition is fixed.
(won't write all let ATI do that ;P)

Tested:
I tested the driver on these conditions:
- Crossfire HD5850 + 9800GTX with:
* driver versions: 196.34beta, 197.45, 257.15beta (all working correctly)
- Single HD5850 + 9800 GTX with:
* driver versions: 196.34beta, 257.15beta (all working correctly)
- Using Intel(s775) & AMD(spider) motherboards.


Install note:
Please read the installation top to bottom before you have an issue on anything.

Screenshot of functional setup:

[Memorian]

Replace the {<YourVideoCardID>} inside 'extra_functions.reg' with your card ID.
Help me with this please

[TwL]

Just follow with instructions:
1. make sure you have removed the driver and rebooted.
2. There is now 'Update 1' online, if using the .cmd then that goes before removal of this registry key.
3. to find correct entry:

1. open 'regedit' in windows
2. go to 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contr ol\Video'
3. locate {} entry there where when you open {} there's 'Video\'-folder which has
1 single entry 'Services'. correct {} is the one which reads in 'services' = amdkmdap and has 0000, 0001, 0002 folders beside the 'video' folder.

4. copy that {} to the reg.

[Memorian]

Ok **** this it's too confusing
Also High Quality AF is enabled by default since HD2xxx series so it won't make any difference

[TwL]

Actually. no.. it's not enabled by default and not controllable through Control Panel either. Difference.. Difference is the ATI crap 'It's sophisticated', lol,
but seriously it's crap that basically could improve the performance by disabling it and while forcing quality it might come in handy.


-edit-

Might as well say this again and again, but I do not build this to gain performance from any of equipment. I build this to get working functions out
of equipment we have. This is not a "Radeon Mr. Tweak"-page in other words.

I fixed 'Experimental Build' for 1 single reason and that's because I suspect that Crossfire (and HD59xx cards) issues/overclocking on 'Hans Dampf'-post
here little above this message were not caused by compining Catalyst 10.3b driver build, but the Catalyst 10.3b driver itself where Catalyst 10.5 should
fix that and as it's functional at x64 all other changes of ATI application side is also in better support "while talking to" driver they were build to.

Hopefully the experimental build will be the last build I have to make to get ati sh1t working properly.

[Hans Dampf]

OMG !!! Can't attend coming home from work!!
Great, great news for me!! Thank you so much man!

After several cleans and setups I couldn't make it work 100%. I could make same as before PhysX work on NVidia only with 257.15 and no fake display. Showing correctly 300% boost in vantage PhysX test but nothing for real in Fluidmark.

Found the problem why I couldn't overclock: Uninstallation of Afterburner/RivatunerOSD was no good idea. Set it up again and everything fine.
Now clocking stable at 960 /1200 @ 1.25V on 4 cores ... CPU 4.4GHz/1.43V - all with only 1K PSU

Good news: With your driver and same settings as before I benched Vantage again and got a big boost on GPU score! Games run like charm - but crossfire must be still disabled for Eyefinity. Single screen crossfire pushes like hell !!

[TwL]

yeah, well looks like I did hit another wall in other ATI bug here on the experimental. Nothing really serious, but at least on my display as I am still testing these the 'video settings' on this 10.5(a) hotfix driver are ineffective(again looks to be 10.5a specific issue), lol. (I'm begin to wonder do they do like random bugs on each driver, draw a card "hey, we don't want AA working on next version" and so on)

Looks like I have to take a look to some other driver still to get things working absolute clean, but I am really running out of drivers, lol. Also while overclocking mentioned 2D bug remains on 10.5 series of drivers (it's an official bug/developer temporary modification).

-edit-

Seems, the video section ain't as bad as I though. it's only catalyst screwing up. the effects on everything are still there in real video.

Here's one more edition of "extra_functions.reg" enabling control of different kind of noise removal for Video Watching people:
Extra Functions - File Only

Will, allow control of 'Mosquito Noise Reduction' what ever that does in real, but well one more wheel to Catalyst, lol. ;P

(for those who do not know what this file is read the first post how to install/register it you need the {GUID} to it.)

[Hans Dampf]

Originally Posted by TwL

yeah, well looks like I did hit another wall in other ATI bug here on the experimental. Nothing really serious, but at least on my display as I am still testing these the 'video settings' on this 10.5(a) hotfix driver are ineffective(again looks to be 10.5a specific issue), lol. (I'm begin to wonder do they do like random bugs on each driver, draw a card "hey, we don't want AA working on next version" and so on)

Looks like I have to take a look to some other driver still to get things working absolute clean, but I am really running out of drivers, lol. Also while overclocking mentioned 2D bug remains on 10.5 series of drivers (it's an official bug/developer temporary modification).

I don't care too much on the 2D bug as others. I use that rig 95% for games and benches. Few minutes in 2D are not a big deal. Temps are fine because of watercooled cards. But of course this quote just counts for me - for others it maybe much more important.

For older drivers I remember that 9.12 Hotfix was scaling pretty well
Hope 10.6 preview will be posted soon! Since rflair is no more posting previews, it is a little bit quiet on that preview/testing stage.

DEAR ATI CATALYST TEAM,

IF YOU READ THIS PLS BE AWARE OF THE FACT THAT A COMMUNITY LIKE THIS IS A BIG HELP FOR YOU, TESTING ALL YOUR NICE BETA DRIVERS UPFRONT BEFORE YOU RELEASE THEM OFFICIALLY TO THE PUBLIC.

PLS RELEASE MORE BETA DRIVERS TO US - EVEN THEY ARE ON EARLY STAGE!

THANK YOU