[noxx2]

Download:
http://ati.amd.com/support/driver.html

Infos:
http://www.winfuture.de/news,36538.html
http://hardware-infos.com/news.php?news=1671
http://game.amd.com/us-en/content/pdf/Catalyst_712.pdf

Chancelog:

* Call of Juarez: Enabling Super AA and CrossFire™ no longer results in corruption being noticed when playing the game. Further details can be found in topic number 737-30592
* DIRT: Launching DIRT with CrossFire™ enabled no longer results in the application failing to launch and an error message being displayed. Further details can be found in topic number 737-29554
* Enemy Territory Quake Wars: Flickering is no longer noticed when SuperAA is enabled. Further details can be found in topic number 737-31136
* Enemy Territory Quake Wars: Setting the in-game options to 2560x1600 and soft particles, along with AA to 8x in the Catalyst™ Control Center no longer results in corruption being noticed. Further details can be found in topic number 737-31135
* Globe 2.1: Corruption is no longer noticed during the introduction video when CrossFire™ is enabled. Further details can be found in topic number 737-31140
* Loki demo: Launching the demo no longer results in the introduction movie failing to display. Further details can be found in topic number 737-31117
* STALKER: Flickering is no longer noticed when playing the game with AA set to 4x and full dynamic lighting is enabled. Further details can be found in topic number 737-30593
* STALKER: The operating system no longer fails when attempting to play the game with CrossFire™ enabled and all in-game options set to maximum. Further details can be found in topic number 737-31131
* HD Audio is now working when setting the desktop resolution to 640x480@60Hz under the Windows XP operating system. Further details can be found in topic number 737-30588
* Enabling CrossFire™ and entering hibernation mode no longer results in the Windows XP operating system failing when attempting to resume from hibernation mode. Further details can be found in topic number 737-30590
* Hot un-plugging the DFP display device when clone mode is enable no longer results in the DFP display device still appearing in the Catalyst™ Control Center. Further details can be found in topic number 737-31114
* HD-DVD content is no longer blocked over native HDMI when using the cyberlink player. Further details can be found in topic number 737-30596
* Connecting an HDMI display device as the secondary display no longer results in extended desktop mode failing when attempting to apply it. Further details can be found in topic number 737-30589
* Entering hibernation mode under Windows XP no longer results in the operating system hanging when attempting to resume from hibernation mode. Further details can be found in topic number 737-31115
* CrossFire™ no longer fails to become disabled when hot unplugging the display device from the interlink dongle. Further details can be found in topic number 737-31116
* Connecting a Dell 30" LDC display device to an ATI Radeon™ HD 2600 series of product no longer results in flashing or no display image. Further details can be found in topic number 737-30545
* The 2D and 3D gamma no longer appears different when using the gamma calibration tool. Further details can be found in topic number 737-29945
* Playing the online game TianLongBaBu for an extended period of time (2 hours or more) on a system containing an ATI Radeon™ HD2400 or HD2600 no longer results in the operating system failing to respond. Further details can be found in topic number 737-30542
* Rotating the display device and running a directX9 sample in full-screen mode no longer results in corruption being noticed. Further details can be found in topic number 737-31118
* Disabling CrossFire™ no longer results in the Windows XP operating system rebooting. Further details can be found in topic number 737-31132
* Connecting a single display device to a secondary graphics adapter no longer results in extended desktop mode being applied. Further details can be found in topic number 737-30538
* Disconnecting display device no longer results in the ability to enable the dis-connected display device within the Catalyst™ Control Center in a CrossFire™ configured system. Further details can be found in topic number 737-31133
* Connecting a TV as the primary display device and setting the signal format to any PAL mode no longer results in corruption being noticed on the secondary display device when playing a media file using WinAmp or WinDVD. Further details can be found in topic number 737-31134
* The Enable ATI Overdrive clocks for 3D applications only checkbox is now checked and grayed out when the OverDrive option in the Catalyst™ Control Center is unlocked. Further details can be found in topic number 737-30600
* Corruption is no longer noticed when enabling Theater mode and enabling clone mode. Further details can be found in topic number 737-30546
* Dragging the WinDVD player from the primary display to the secondary display no longer results in the player failing to respond. Further, closing the WinDVD player using the Task Manager may result in the operating system failing to respond. Further details can be found in topic number 737-29955
* With some h.264 titles that have MPEG2 intros, playback no longer switches from hardware accelerated to software once the introductory content is finished. Further details can be found in topic number 737-28517
* On certain products, dragging player window from primary to secondary display no longer results in hardware acceleration being disabled which resulted in the CPU usage increasing. Further details can be found in topic number 737-28516
* DXVA is now in use when play H264/VC1 HD content on systems containing an ATI Radeon™ HD 2600 series of product. Further details can be found in topic number 737-31137
* Enabling tiling on the secondary display device when Overlay Theater Mode is enable no longer result in corruption being noticed. Further details can be found in topic number 737-31138
* Corruption is no longer noticed on the secondary display device when Overlay Theater Mode is enabled. Further details can be found in topic number 737-31139
* Enabling clone mode no longer results in corruption being noticed on both display devices when Overlay Theater mode is enabled and the 3D screen saver becomes active. Further details can be found in topic number 737-31141

[JackTramiel]

Klasse, wollt eh die Tage mal einen neuen Versuch starten mein TV Part endlich ans laufen zu bekommen.
In Sachen HTPC hat sich beim Treiber ja auch echt was getan, nur das Problem mit der Overscan Korrektur unter 50Hz ist IMMERNOCH NICHT gefixt. Das kann echt nicht wahr sein.

Danke für die Info.

[noxx2]

DXVA is now in use when play H264/VC1 HD content on systems containing an ATI Radeon™ HD 2600 series of product. Further details can be found in topic number 737-31137

Heisst das, das man sich den Registry Tweak für die Hardwarebeschleunigung nun sparen kann?

[JackTramiel]

Bei der 2600 brauchte man den glaub ich eh nicht unbedingt. Zumindest lief das mit den Cyberlink Codecs und ohne Reghack auch so schon bei mir. Nun sollte es aber definitiv laufen würde ich sagen.

[noxx2]

Kann es sein, das man den Overscan nicht mehr einstellen kann? Finde die Option nicht, grrrrr

[kiesow]

Originally Posted by noxx2

Kann es sein, das man den Overscan nicht mehr einstellen kann? Finde die Option nicht, grrrrr

Geht AFAIK schon zumindest seit der letzten Version nicht mehr

[rtv]

Nicht zu böse auf ATI sein - bei nvidia ist man sogar an die noch ältere Treiberversion 94.24 gebunden weil alle "modernen" Treiber wie die aktuellen 16x.xx keine custom resolutions with PAL & NTSC mehr erlauben...

[kiesow]

Aber gerade ATI hatte darauf hingewiesen, das es durchaus helfen könnte, wenn sich einer von euch Devs "offiziell" mit einer Fehlerbeschreibung bei ihnen melden würde. Stand irgendwo bei http://forum.team-mediaportal.com/at...ms-t29894.html

[t-herweg]

Ist das Problem mit dem ATI 690G und x1250 denn mit dem Treiber gelöst?

[kiesow]

Originally Posted by t-herweg

Ist das Problem mit dem ATI 690G und x1250 denn mit dem Treiber gelöst?

Nein, das besteht leider noch immer.