Both (I want to have official INF in install, separated modified INF & 'Functions.reg' as choice)

Idea was never to perform good, but to get back what is not working and after 20-25 builds and over 10-15 Official AMD/ATI builds of drivers. We are
still and will be looking on full functional driver ONLY. OpenGL, OpenCL with-in any setup working correctly. Difficulties on CrossFireX and setups like
ATI+NVIDIA will be bypassed as they come around and build around the issues. All current and every future build will support these no matter even, if
they make me build the slowest driver in earth.

To read and understand:

Should you use 'Catalyst [Modified build]' in the first place:
I do not believe that this topic is for newbies or unexperiences new users. I do believe that people who understands what they are doing or at least how
to read should be the only people using my mods and further more I still build them to myself not for others, including support for other to use them in
their specific systems is what you should consider an bonus.

Paranoia Users:

I will as said before separate the tweaking and cleaning to be user optional for next build. I will not separate build up of tweaks to user optional from our install system as it's
here to stay and any paranoia user can read my installer through personally, if he/she wishes and understand it or not use my mods at all and use what ever
you like, but don't come here to ask questions about it I am getting sick and tired of people stupidity when not utilizing what I have to offer and then
trying to out smart the installer by installing 'something' from the package which is the most idiotic thing I can think of anyone doing.

06.06.2012: Updated latest changes to Clean-up v5.01 now including missing paths and verified new data against old data. NVIDIA Section will be gone soon (as there's a new setup not ignoring Batman Arkham Tweaks = stable version, Experimental version is going to be fully functional in PhysX just not in B:AC release).27.07.2011: New modified driver is attempt to support <any> system. I know from the past that CFX/QFX systems this will be bad move, so, most likely we will see x86/x64/Desktop(single card) + <X>Fire x86/x64 drivers still separated as AMD has not been able to even fix the DirectX 9-11 currently and my honest guess is they are still struggling to get the CPU/GPU processors and hopefully basic processing unit network together + application engineers/developers to actually support their new crap. Sadly at current drivers we have this ain't gonna happen as no one seems to be interested of porting this. Hopefully also I can mod against the DX1x drivers and not these damn alpha/beta/preview/uber future AMD builds.26.07.2011: New v4.90-5.00 cleaning system begins to be ready. Adding it as soon I've verified and tested it against laptops.03.07.2011: Started working on 10.2->10.7 preview however there's still some problems on core driver at both 10.6a and 10.7 preview. I can first solutions from earlier drivers, but will build new build against 10.7 soon enough.01.07.2011: Time is limited, but got hold on new testing equipment working on pretty tight schedule (7 day weeks), but there's some free time now and then, so, currently I am hoping to test the 10.6 hotfixes and build against 10.7 (WHQL).17.03.2011: Still no word for testing equipment. Missing an decent CFX GPU for testing currently as only component. Beside that and few other probs in real life next build will be here around start of next month at earliest. It is been build never the less, but testing is 100 times slower on current hardware and so I will not even attempt to build.

Older News Archives:

23.01.2011: Genetix Cleaner v4.84 update: Improved the script further to process display data faster and to not hunt ghosts. Updated AMD
Motherboard ignore some of files. So, clean-up is now has full support for AMD motherboards. Also ignoring now HDMI so HDMI is not cleaned during
clean-up. *by my personal testing now and few testers helping out I truly hope v4.84* is 'the' number and clean-up won't have to be updated again ever.22.01.2011: Genetix Cleaner v4.83b update: bug at jumping over installed content + process missing x86 entries.22.01.2011: Genetix Cleaner v4.83 - Stand-Alone ATI/NVIDIA clean-up system is now alive and I do believe this is the last clean-up which will be build as it doesn't anylonger matter what AMD/ATI updates (if there's something I am sure to fix it). Current clean-up system can be even now used, if drivers are installed in matter of facts in any system condition.21.01.2011: For people who has Flashed BIOS or updated GPU hardware without reinstalling windows. There is an possible bug of detecting 'ghost' hardware. Solution is provided at driver release notes.20.01.2011: heck I just have to congrat AMD Driver team after 9 months of breaking OCL they have finally brought back functional OCL to 11.1 beta's. (Even while they did break OpenGL in the action, heh).20.01.2011: Hmm, 2 bugs identified and dealt with. (still trying to locate the mobility OGL bug mentioned), but information can be read on release notes and included temporal NOTE to install instructions. Next build date is unknown, but it will no longer be 10.11 or 10.12 driver series.20.01.2011: If there's a better use for a internet I haven't found it. 19.01.2011: New NVIDIA patch up also fixed basics on installer so only the installer cmd was updated to include better WISE installation clean-up (optional).19.01.2011: Final Build v5.10 is up and I did some major testing on this one took me solid 10 hours to go through all equipment and installation methods and I almost completely fixed the batching and tweaking.19.01.2011: Fixing sevral issues and adding build v5.09 online today.18.01.2011: There was Critical issue with installer and clean-up batch files. Please, override the files before installation.18.01.2011: Added NVIDIA v1.07 and v1.07-ocl builds for hybrid setups. Driver is different and monitoring data and OpenCL support. Select your own poison for now these are the best before I finish this NVIDIA developer driver OpenCL support for new.17.01.2011: Goodbye signature checks. New system build against this concept. So, now we have full HD69xx support and also I scripted up RadeonPro fix for this
hardware. Including minor hardware detection to installation.17.01.2011: Driver release is growing so huge I have to split it for unique setup styles. As for currently: Mobility, AGP will be at own category and HD2xxx-6xxx on their own category.17.02.2011: Updating recent bug fixes and new cleanup comes as WinRAR SFX requesting Administrative privileges. I could of done this now on CMD form, but using WinRAR SFX this guarantees 2 things first of that it's executing in 'temp'-folder which is writable and second that user has needed permissions to do clean-up. (You may still extract the EXE by right click with WinRAR -> Extract it's not locked by any means)

NOTE: Make sure 'device manager' says 'Standard VGA Display Adapter' on all ATI and NVIDIA cards, if not:
- remove driver & add check mark to 'Delete the Driver Software for this Device' -> 'scan for hardware changes'
or on NVIDIA cards
- 'scan for hardware changes' -> to find NVIDIA adapter before reboot (to avoid another reboot as otherwise it detects it after you've rebooted and
you have to reboot again)
(Do this so many times/long that it does says 'Standard VGA Display Adapter', if there's an WDDM 1.1 Microsoft driver continue to clean-up you cannot
remove it by device manager)NOTE (PhysX): uninstall PhysX as ATI Catalyst also affects PhysX functionality / display setup also.

2. reboot as usual.

OPTIONAL (Chipset UPDATE, if needed):
People with INTEL Chipsets: Intel Chipset Software (proper update process) -> Official Website / Newest Drivers (NOTE: This website has popups, but drivers are always newer than at Intel because of Intel hides latest updates to specific chipsets)
People with AMD Chipsets: AMD South Bridge Driver
NOTE: AMD drivers and utilities are included with v5.00 build package. Detection if/when to use these might be incorrect as for now would still be recommended that you do your own updates.
(Increases Stability of whole system to have properly installed and up-to-date chipset drivers before driver installation)

DirectX: AMD/ATI: You should install DirectX Full Installation BEFORE actual driver installation OR use the webinstaller with the clean-up cmd I created to make sure that Microsoft newest DirectX patches/improvements could work better/at all before driver is in the system. AMD/ATI+NVIDIA: You wanna update DirectX also while full installation is done, after the 'fake' display for NVIDIA card is active as then DXDIAG will see correct GPU memory amount of all cards.

NOTE: Check that there is NO 'C:\AMD' OR 'C:\ATI' folders existing. (AMD/ATI Official Install folders as these installers tends to check it seems).

AMD/ATI- Install Instructions:

NOTE (Critical): Batch files most be executed as TRUE administrator (and not on any safe mode).
Instructions are given at above quote how to for OEM and bad situation systems at none administrative level users can do this. There are also
situations on Windows where operating system itself bugs (like on latest RC SP1).NOTE (Bug) [v5.10 ONLY]: Please, install the packages from folder with no spaces (ex. c:\something) there's an registry passthrough error, if you already did run the install you can launch 'optimize\finalize_optimization.cmd' manually would solve the problem.NOTE (Bug) : Verify/Understand that there is no updated hardware bug mentioned at release notes.

1. Run 'genetix_cleanup.cmd'2. Run 'genetix_install_silent.cmd'Alternatively: Run 'genetix_install.cmd' (this will display AMD Driver installation window. Just don't boot when asked by AMD driver installer.)3. Reboot to finish the setupNOTE (ATI+NVIDIA): If you have an hybrid setup proceed to NVIDIA setup instead of rebooting.

NVIDIA [Hybrid Systems] - Install Instructions:

3. Run NVIDIA + PhysX Installations before rebooting. ('genetix_nvinstall.cmd' from v1.08 is recommended which will require the NVIDIA Expansion pack v1.07)4. To enable ATI + NVIDIA OpenCL do following at this SlideShow:5. Reboot to finish the setup

NOTE: You might still need to reset or modify any direction NVIDIA overclocking from monitoring applications as this activated the 'nvapi' better/faster.

NVIDIA - Driver Versions:

Slideshow is only applicable to NVIDIA driver versions 25x.xx and below noting that 19x.xx driver versions needs PhysX Mod 1.03 before restart + PhysX Mod 1.04ff after new PhysX installation installed after actual display driver has been installed separately. At new NVIDIA 26x.xx this display setup does not apply and OCL/DC device is activated even without display being attached, however this is unfunctional as of yet because of buggy new nvidia display syncronize module.

Cross-/Tri-/QuadFireX-EyeFinity + NVIDIA:

Under Cross-/Tri-/QuadfireX systems and Multi-monitor environments you really wanna create linking and generally finish installing ATI Side BEFORE you
turn up NVIDIA driver & it's monitor. Otherwise you will be in switch situation where NVIDIA monitor will keep switching as 'Display 1' and that is a situation
you can only get rid of by disabling & removing NVIDIA monitor and then reboot and do the whole monitor setup again.

* PhysX support
* OpenCL 1.1 / DirectCompute x.x Support
* Functional GPU and Memory Monitoring support (Watch NVIDIA Display Adapted installation section 'slideshow' is needed for applications to query memory utilization)NOTE for WISE Installation Wizard: There is an question about removal as PhysX 9.10.0514 was build to block old installations, lol, but there is an risk cleaning these installers, if your other software uses these type of installers keeping uninstall data. This doesn't affect any regular user as really rarely anything uses this path as uninstall backup.

* PhysX support
* OpenCL 1.1 / DirectCompute x.x Support
* Unfunctional GPU Monitoring support
* Functional Memory Monitoring support (Watch NVIDIA Display Adapted installation section 'slideshow' is needed for applications to query memory utilization)NOTE for WISE Installation Wizard: There is an question about removal as PhysX 9.10.0514 was build to block old installations, lol, but there is an risk cleaning these installers, if your other software uses these type of installers keeping uninstall data. This doesn't affect any regular user as really rarely anything uses this path as uninstall backup.

NOTE:
by using these you understand to read the install instructions, that the driver is for testing purposes only no matter how Final/Uber finished build anyone including myself says it is and you are the one who installs them as in you are responsible for your own equipment/hardware. You do understand to read what you are using like batch/cmd file and that these files can very easily harm your system, if they are build badly or purposely to do so.

Friendly advice trust no one on web check yourself, do not relay on someone else writings.

* OpenGL update for all hardware (11.1beta)
* New HardwareID detection system for CCC tweaking
* Fixed minor installer bug at CCC 2.0 force installations should now be fully functional to install new CCC panel under HD6 and Mobility configurations. (AGP as for currently is still unknown).
* Fixed forced CCC 2.0 Installation uninstallation detection to clean-up, if detected.
* Few completely new tweaks to CCC and settings are now applied to correct GUIDs not to display data.
* ATI Stream v2.3 added correctly now for AGP and Mobility setups. Including force pass through to system.

Bugs:

- Bug: New OpenGL profiling. This seems to only affect OpenGL 4.1 and actually at lower levels like Doom 3 and Prey etc the OpenGL works just fine and looks damn great. It will however fail at Heaven Benchmark and so I will provide solution for it.
+ Solution: Download the OpenGL patch and apply at download section.
- Bug: There's an 'foldername' bug at finalizing optimization which script is passing RunOnce for final optimize the folder names with spaces cannot be used correctly at passed command.
+ Solution: Run the whole package from folder without spaces for now. Will be fixed to next build. Alternatively, if already run you can go to the package folder and run optimize yourself from "optimize\finalize_optimization.cmd" as the hardware detection is already build it just needs to be launched at it's own folder.
- Bug: For people who has Flashed BIOS-, Updated 'new' Cards-, removed card from computer without reinstalling windows. There is an possible bug of detecting 'ghost' hardware.
+ Solution: make .cmd or run as Administrator from command prompt commands:

Adobe Flash issues while plug.in installed by browser [Opera 10, Firefox v3.x/4.x]:Problem: Flash does not act as hardware accelerated by ATI Catalyst 11.1-11.2 installation while flash is installed by the browser.Solution: Install Flash from adobe site separately. This will make the hardware acceleration check mark to function correctly under usage of flash.

----Game Specific Fixing----

Common Gaming DVA Hardware Acceleration failure in all drivers:

* Tearing issue with other resolutions that 1920x1080 and 1920x720:

Found the cause on tearing issues when you play for example 1920x1200 or any other resolution not mentioned above. Problem is caused by ATI DVA modules and can be solved as follows:

1. Launch the game and change your resolution to 1920x720 or 1920x1080 in-game2. exit the game3. relaunch the game and start playing4. now ESC > Options > change the resolution back to what ever resolution you were using.

When you load the code ATI driver will "think" correctly on DVA side (As the modules doesn't support anything else then XXXXx1080 and XXXXx720) and
activate hardware acceleration and switching resolution while playing the game will not affect the performance as DVA Hardware acceleration is already
enabled and it will not disable. Bad news is you have to do this every single time you load the game so I suggest you quit as 1920x1080 or 1920x720 resolution.

Battlefield: Bad Company 2:

Other BF:BC2 Releated for everyone. The BF:BC2 folder comes with these files backup the files and remove these files from BF:BC2 folder:

Code:

D3DCompiler_42.dll
D3DX9_42.dll
d3dx10_42.dll
d3dx11_42.dll

(This will make sure game uses YOUR system newer DirectX instead of old DirectX files which came with the game itself.)

Bioshock/Bioshock 2:
Help for people to run AA as well as other effects and general functionality topic: THIS POST

Settings:
- In each testing were exact same as low as catalyst settings go. With 'Prefer Application settings', if possible by settings.
- The benchmarks were taken 5 minutes after restart complete IDLE and redone 25 minutes after complete IDLE. Best result
there was remains as picture here.

This includes official to Builds here and will be updated regularly:

-Latest Updates:
* Official 10.12a 'Vantage Extreme'
* Final Build v5.00
- Click 'preview' to get better view from right corner. Seems to be nice way of viewing images.

You can try with your <what ever> version of catalyst/Forceware to redo anything what's shown on screenshots (except the Eva Mendes) and it will fail on any other driver than what's included here.

Skip read the edit said:

Also, just for the record of the NVIDIA driver side. Every single Forceware after '196.34 beta' is actually slower than '196.34 beta', but you will need an PhysX hack v1.02 for that from GenL (can be found pretty easily). So, consider that before using v257.15 (OR any other v197.xx) drivers. PhysX works flawless over 60FPS on same setup, if using '196.34 beta' + GenL patch v1.02 that is on screens while at new Forceware v257.xx as you can see on screenshot it drops BELOW 60FPS to 54FPS although it allows more on screen.

Well, it would seem that v257.15 has a small bug in disabling & enabling adapter. I crashes but only 1 time(if disabling adapter on device manager), but there's an BONUS, heh. It would seem that Forceware 257.15 works with out anykind of display adapter attached to it & without 'extending display' (as we are used to have when we work with Radeon+Geforce combination).

Also there's new entry on windows Power saving options for SLI adapters and IGP which basically should disable the First GPU to save power however, in ATI+NVIDIA case sadly this option disables the ATI card as it's the first (Option doesn't exist, if no display in NVIDIA device which is probably also reason for the '1 crash time').

Basically when you install according to above instructions with no display (or fake) attached to NVIDIA card it'll still work.

Found the bug in PhysX slow down now. It is not 'PhysX Hybrid Mod 1.03'(so works with out anykind of display attached) it is
'MSI Afterburner' and probably it's RTSS OSD service. Pretty easy to reproduce:
1. Afterburner Up Framerate drops to half on Fluidmark
2. Afterburner Closed Framerate goes back to 120FPS on Fluidmark

Your issue with PhysX could be related to Fan speed reporting API in NVIDIA release 256 drivers which is currenlty working abnormally slow on some nVidia cards. Disable fan speed graph in either Precision or Afterburner if you're experiencing stuttering or lower than expected FPS.

yeah, I know of the issue, but basically I don't believe using fans at all. :3eyes:

Just kidding of course, but seriously one of the reasons I left 'Forceware' out of this mess. As I think it's better let people choose what versions with /without cracking physX they wanna use and as suggested '196.34 beta' is very good choise for physx 257.15 is no better when it comes to physics.

However, no it's not v257.15 specifically on my case > I tested 19x drivers also with different catalyst compinations > culprit was 'Rivatuner Statistic Server'/OSD.

(btw, while researching found out that 'fluidmark' only utilizes ~33% of card and only 60% of Radeon, but seems multithreaded 'FluidMark v1.2.0' does much better results.)

@Shroomalistic

now that's weird. as I read your video card. I am using exact same setup works flawless.

@commonly

just went nicely to below 200MB on 7-zip..
(Included 7-zip download link on post now)

as what goes to 'usefulness' of this package. I build it to function in almost any condition, but as said no one is forced to use them. Point is there is NO other drivers existing that supports hardware in this level.

The driver setup above supports clean (as what goes to .INF's) all ati cards. (with exception there is v10.3b issues on HD5970 as there were back then, but even those cards works better with this than on new as with new you cannot use cards computing capabilities by any means other than this driver as GPU #2 is locked by AMD/ATI since v10.4<any beta/version>). There's several posts in this issue on ATI forums as well on ATI stream forums with no resolutions.

The second ATI fixes 'aticaldd.dll' > 'aticfx32.dll' > driver under x64 system SysWOW64\ I will stop updating this topic & move to those drivers.

As what goes to USB I don't think so. Latency to device would probably be first issue and even on USB3 bandwidth would still be issue. PhysX requires a lot of memory.

better question would probably be 'Could PhysX/physics chip(commonly would support all) be made size and suitable like usual DDRx memory stick?', but no worries as long there's stupid people buying 1/1000 of actual equipment potential like now we will never see true topnotch technology on any market.

Should be just fine and fix the 3 GPU OpenCL also while benchmarking etc.

If you are up to only gaming I still suggest dropping the 10.5 hotfix & 19x.xx(or 257.15) forceware to that, but x86 any GPU tools will fail with ATI Stream in that case. Performance might be better (although, development is near 0 level between 10.3>10.5).

but then again you can always install this and update driver only later giving at least decent baseline what really can be used/utilized with these GPUs.

Funny thing is I haven't seen this issue and I cannot duplicate even while I have same HD5850, but ASUS. I did although read about issue and the higher clocks were meant to be temporal change to improve 2D(multiscreen more specifically) and also read that this is simply edit to 2D profiles to fix(So, no driver is not the one faulty it's CCC settings), but I do not 'modify' drivers simply combined versions. (and if I would of fix this with any of the v10.3 edition CCC Video section would of been broken, 10.4 the video section would of still be broken and missing encoding on both choices.)

As far of my own testing seems the issue has something to do with 'all the time overclocked card' as when on default clocks 2D mode works just fine, but if overclocked the higher clocks remains. As I am using 'MSI Afterburner' my card is 99% not clocked and OC'd only when needed, but those are just what I see as said I cannot reproduce.

You can reproduce it if you activate overdrive and overclock or downclock the cards (also +/- 5MHz).

My card crash if I overclock with third part tools (isn't reference), with a game in background and after I launch an video.
Overdrive seem manage better the idle > uvd > 3d state, and I love it for the this reason.
157/300 on idle state and full oc when I really need it (before damn 10.5 version).

With this i get "crazy" video colors sliders, and white stripes with dynamic contrast "on", I don't know other problems.

ATM i don't have 1 only driver that works without bugs at 100%, very bad. I hope with 10.6 will revert this change and will not have other bugs

actually now that I look your setup I remove the below quote. I read you only got 1 GPU. This mod driver is meant for 2 GPUs or more not a single GPU issues. You should always use newest driver for single GPU setup from AMD or latest functional.

If you are interested on 2D clock correction. Search google for solutions (won't post other tweaking sites), but there's rather easy fix in 2D profiles for the issue.

removed quote said:

Ok, so maybe a stupid question, but why don't you then use Catalyst only from earlier versions and use the new 10.5 driver with them ? I mean even this pack here, only thing you would have to replace would be 'Apps\CCC' folder from earlier catalyst(preferable 10.4b?) and it would work with 10.3b to allow you also to do ATI Stream, if you are not interested on 'ATI Stream'/OpenCL then 10.5 driver with 10.4 CCC would be probably most ideal.

about video on older CCC:
Nothing wrong with encoding/decoding I said 'video section' is a bit different there. since 10.3->10.4 there's issue in CCC it does not change any of the registry Video values even while you change them in control panel 10.5 fixes this issue. It's a bit deeper than contrast I'm afraid also it's literally actually all enhancements through GPU as well.

reproduce:
As I said I cannot reproduce this. I tested what you asked clocks works as they should accordingly here on card BIOS. I tested 900Mhz clocks through overdrive. Also 3D (and REAL heady 2D). I cannot get the same effect out of card as some people for some reason. The reason this would happen would be CCC stresshold trigger to jump clocks.

There is *5 different clocks inside HD5850 BIOS if the CCC issues 2D profile based stresshold trigger to the card clock will change, but in my case I see no issues. Probably the volterra mod I got handles it better.