ATi Catalyst 5.13 final

Videochipfabrikant ATi heeft zonet de finalversie van Catalyst-driver 5.13 uitgebracht. Deze release is beschikbaar voor Windows 2000, Windows XP en Windows XP x64 en wordt geleverd met een groot aantal bugfixes en nieuwe features. Catalyst 5.13 voegt onder andere voor een aantal videokaarten uit de X1000-serie hardwarematige ondersteuning toe van H.264 en is het mogelijk om de Radeon X1800 XT in CrossFire-opstelling te gebruiken. Vier dagen geleden werd de reviewversie van Catalyst 5.13 op het internet gezet. Deze versie kon door de reviewers gebruikt worden om de X1800 XT CrossFire te benchmarken. Vandaag hebben onder meer Beyond3D, FiringSquad, HotHardware, Guru3D en AnandTech hun 'non-disclosure agreement' mogen opheven en hun bevindingen kunnen publiceren. Het exacte changelog van de reviewversie was nog niet bekendgemaakt, maar bij de officiële release van Catalyst-versie 5.13 is dat nu wel bekend, en ziet er als volgt uit:

Issues Resolved in Catalyst® Software Suite 5.13

• F.E.A.R: Slow game performance is no longer noticed when using CrossFire. Further information on this resolved issue can be found in topic number 737-21270
• The Video Preview no longer fails to change to its default settings when swapping the display mappings using the Catalyst® Control Center. Further information on this resolved issue can be found in topic number 737-21174
• Attempting to stretch the display horizontally using the Catalyst® Control Center, no longer results in the horizontal stretch mode failing to be applied unless the display is stretched vertically first. Further information on this resolved issue can be found in topic number 737-21175
• The PowerPlay™ option found in the Catalyst® Control Center no longer defaults to the enabled state after initial install of the display driver for systems containing an ATI Radeon® Xpress 200 series product. Further information on this resolved issue can be found in topic number 737-21180
• Auto-detect no longer fails to be applied as the default setting for the Deinterlacing option when first entering the Video aspect page of the Catalyst® Control Center. Currently the option is set as Weave. Further information on this resolved issue can be found in topic number 737-21185
• Catalyst® Control Center: Attempting to extend the desktop display when using a CRT, TV and DFP display devices no longer results in display corruption being noticed on the primary display adapter. Further information on this resolved issue can be found in topic number 737-20982
• Attempting to set the CRT as the primary display device after hot-plugging a DFP display device and enabling extended desktop mode, no longer results in the CRT failing to be set as the primary. Further information on this resolved issue can be found in topic number 737-21269
• Catalyst® Control Center: Entering the Overdrive™ aspect and changing the GPU setting to 509 and the memory setting to 505 no longer results in color corruption and the Windows XP operating system rebooting. Further information on this resolved issue can be found in topic number 737-21229

Known Issues for Catalyst® Software Suite 5.13

• BattleField 2 Special Forces: A blooming or ghosting effect may be noticed when playing the game in night vision mode. Further details can be found in topic number 737-21263
• Beyond Good and Evil: Flickering artifacts are noticed on the game characters after approximately 15 minutes of game play. Further details can be found in topic number 737-20795
• Dark Age of Camelot: The game exits to the desktop immediately after launching, or may play for up to 15 minutes followed by a VPU Recover error message being displayed. Further details can be found in topic number 737-20794
• Dragonshard: Playing the game under Windows XP Media Center Edition with CrossFire™ enabled, may result screen becoming out of sync, and a scrolling display image occurring shortly there after. Further details can be found in topic number 737-20975
• Fable: The Lost Chapters: Playing the game under Windows XP MCE may result in the shadows found within the game appearing jittery, when the desktop resolution is set to 1024x768 32bpp, and all the game options are set to default. Further details can be found in topic number 737-21184
• Serious Sam 2 Demo: Enabling CrossFire™ may result in a performance drop being noticed when playing the game under Windows XP Media Center Edition. Further details can be found in topic number 737-20976
• WARHAMMER: DAWN OF WAR: Starting a skirmish game on a 4 player map under Windows XP, may result in the game performance appearing choppy when using an ATI Radeon® X800 series, and having all of the game options set to high. Further details can be found in topic number 737-20974
• World of Warcraft: A VPU Recover event may occur when launching the game with high level avatar and rotating or zooming within the Blackwing Lair or within Searing Gorge Further details can be found in topic number 737-21265
• Catalyst® Control Center: The SmartShader™ effect is not removed from the 3D preview when attempting to restore the default values in the Catalyst® Control Center. Further details can be found in topic number 737-20846
• The Apply button in the Custom settings of the Advanced mode, within the Catalyst® Control Center Video standard settings, is grayed out when playing a media file. Further details can be found in topic number 737-497
• Connecting an HDTV to an ATI Radeon® X700 series may result in the HDTV being detected as a CRT or TV under the Windows XP operating system. Further details can be found in topic number 737-20783
• Attempting to install the integrated WDM driver under Windows XP may result in an error message being displayed indicating that the hardware is not installed because the install Wizard cannot find the necessary software. Further details can be found in topic number. 737-20784
• The PAL FM fine tuning algorithm is currently using 200 MHz bandwidth which may overlap FM channels resulting in the same FM channel being found several verdana during the scan function. Further details can be found in topic number 737-20979
• Launching the Adobe Gamma calibration application and moving the gamma slider back and forth, results in the Task Manager being filled with cli.exe until the system becomes low on memory. Further details can be found in topic number 737-20980
• Catalyst® Control Center: The preview for the Deinterlacing aspect found in the Catalyst® Control Center is currently unavailable when using the ATI Radeon® X1300. Further details can be found in topic number 737-20986
• The Video Preview found in the Standard Settings of the Video option of the Catalyst® Control Center may fail to provide a preview after hotplugging an LCD panel to an ATI Radeon 9500 or 9800 and selecting to extend the desktop. Further details can be found in topic number 737-21173
• Connecting two display devices to the ATI Radeon® X850 CrossFire™ Edition and one display device to the ATI Radeon® X850 XT may result in the display device connected to the Radeon® X850 XT still being active once CrossFire™ is enabled. Further details can be found in topic number 737-21177
• The WDM Drivers may not be enumerated due to the Capture chip not being detected when using the ATI Radeon® X850 XT (ViVo) as a slave card on a system containing an ATI Radeon® X850 CrossFire™ Edition. Further details can be found in topic number 737-21178
• The secondary display device may fail to activate when attempting to enable clone mode when using an ATI Radeon® X800 GTO. Further details can be found in topic number 737-21179
• Using the Custom option when installing the software driver results in the Theater™ 550 software driver not being present. Further details can be found in topic number 737-21183
• The apply button may remain inactive when attempting to change the Hue and Saturation settings found in the TV Properties\Avivo Color settings when enabling a TV as the primary display device and a CRT as the secondary display device. Further details can be found in topic number 737-21264
• Connecting two display devices to an ATI Radeon® X1600 series product may result in the device manager failing to detect the secondary display device. Further details can be found in topic number 737-21266