Guru3D and MSI have been working hard on AfterBurner, today we release an updated Beta revision of Afterburner, this application successfully secured the leading position on graphics card utilities.
Today we release an updated Beta revision of Afterburner, this application successfully secured the leading position on graphics card utilities. We're happy to see MSI Afterburner is leading the overclock applications. MSI Afterburner 2.2.0 Beta 7 is ready,
Changes list includes:
MSI Afterburner is no longer using native AMD ADL SDK GPU indices. Now it always sorts GPUs by PCI location to ensure that GPU indices stay the same in the system regardless of operating system, display driver version and GPU display outputs connection
Added driver-level fan tachometer monitoring fallback for AMD graphics cards via AMD ADL SDK
Added unofficial overclocking support for AMD graphics cards unattached to Windows desktop
Improved Catalyst version detection for AMD graphics cards unattached to Windows desktop
Improved GPU type definition format in hardware database to fix ambiguous GPU type selection on some custom design MSI graphics cards (e.g. MSI R5870 Lightning series)
Now MSI Afterburner's startup daemon routine precaches graphics card state at the first Windows startup. Precached state is being used to improve default clocks detection and clock sliders calibration in some cases when display driver provides no trustworthy defaults detection mechanism (e.g. on AMD graphics cards in unofficial overclocking mode)
Added unified vendor independent videomemory usage monitoring layer for graphics cards, having no generic videomemory monitoring interfaces implementation in display drivers. Unified videomemory usage monitoring layer is based upon RivaTuner's VidMem plugin technology under Windows XP and original concepts of accessing Direct3D kernel mode thunk statistics under Windows Vista and Windows 7, introduced by Mark Russinovich in ProcessExplorer 15. By default unified videomemory usage monitoring path is enabled as primary ath on AMD graphics cards and as a fallback path on NVIDIA graphics cards when generic NVAPI videomemory usage monitoring is not available (e.g. on NVIDIA graphics cards unattcached to Windows desktop, such as dedicated PhysX or other GPGPU graphics cards). Power users may redefine unified and generic videomemory monitoring paths usage behaviors for both AMD and NVIDIA hardware abstraction layers via the configuration file.
MSI On-Screen Display Server has been upgraded to v4.2.3. New version fixes vertex buffer overflow issue causing improper On-Screen Display rendering or crashing in Direct3D10 / Direct3D11 applications when too many items are selected to be displayed in On-Screen Display