Rivatuner version 2.20 has been released which includes support for nVidia ForceWare GeForce drivers, 180.48 WHQL and AMD ATI Catalyst 8.11. According to the author, the biggest change and challenge for this release was to support Multi-GPU (SLI/CrossfireX) configurations.

Here’s hoping to HD4870x2 Crossfire config working for me once I try Rivatuner 2.20.

Added workaround for broken error reporting system of PowerPlay clock control interfaces in Catalyst 8.10 hotfix 2 and Catalyst 8.11 driver families. Due to internal bug these drivers report incorrect error codes in PowerPlay clock control calls, causing overclocking tools like RivaTuner, ATITool or AMDGPUClockTool to stop working properly. Until the problem is fixed in the Catalyst driver RivaTuner provides temporary workaround by disabling error control for PowerPlay clock control calls on the Catalyst 8.10 hotfix 2 and newer drivers. Please take a note that the workaround can be forcibly disabled via ATIPowerPlayErrorReportingWorkaround registry entry.

Added driver-level fan control support for ForceWare 180.xx drivers family.

Seriously redesigned hardware access layer provides drastically improved multi-GPU support. Now RivaTuner no longer uses single device selection ideology and supports simultaneous access to multiple physical display devices or GPUs in the most popular and frequently used modules, such as hardware monitoring module, profile launcher and task scheduler.

Drastically increased performance of routines applying clock frequencies and fan speed when experimental cloning modes are enabled. Due to new multi-GPU oriented hardware access layer all display devices can be accessed simultaneously, it saves CPU time required on switching current display device and reinitializing hardware access layer in ther previous version.

Now RivaTuner displays physical GPU index in the main tab on multi-GPU systems to simplify identifying independent physical devices and logical devices of the same physical GPU (e.g. two independent RAMDACs located on the same physical GPU).

Improved hardware monitoring module:

New multi-GPU oriented hardware access layer allows simultaneous monitoring of all supported physical display adapters and GPUs installed in the system. Simultaneous monitoring is available for both multi-monitor configurations and SLI/Crossfire modes.

Improved API for hardware monitoring plugins:

Added new GetSourceCaps function allowing the plugins to report different capabilities specific for exported data sources. This function helps hardware monitoring core to identify system wide and multi-GPU support capable data sources.

All GPU sensor specific plugins (e.g. ADT7473.dll) have been updated to support new API functions and provide multi-GPU monitoring support.

All system wide plugins (e.g. CPU.dll) have been updated to support reporting system wide data source capability.

Improved ADT7473.dll plugin.

Now the plugin’s database may include hardcoded pulses per revolution counters for some display adapter models to provide correct fan speed monitoring on the systems with counters improperly calibrated in VGA BIOS (e.g. some GeForce 8800GT models).

New multi-GPU oriented hardware access layer allows associating launch items with any desired physical or logical display device and launching the profiles specific for this device without changing current display device selection.

Now RivaTuner no longer records launcher events into hardware monitoring event history panel by default. Now you may enable launcher event history logging into event history panel properties if necessary.

Improved scheduler module:

New multi-GPU oriented monitoring module and launcher allow using the scheduler to program independent dynamic gamma, fan and clock control algorithms for each physical display device installed in the system.

New ‘Pause scheduler’ module allows you to suspend the scheduler’s activity if necessary.

New ‘Sampling period’ setting allows you to override default sampling period for scheduled tasks associated with hardware monitoring module. Custom sampling period setting can be useful if hardware monitoring module polls hardware frequently but too frequent scheduled tasks execution is not desired. Please take a note that in case of defining multiple scheduled tasks with different sampling periods the maximum sampling period defined for a data source is being used.

New ‘Task freezing period’ setting allows you to define so called task freezing period for scheduled tasks associated with hardware monitoring module. Task freezing period setting is useful when it is necessary to program a few tasks with different execution priorities. Executing a task with non-zero task freezing period causes the scheduler module to suspend execution of all tasks associated with the same data source until task freezing period is over and to put such tasks into the queue. The last queued task will be executed in the end of task freezing period.

Now RivaTuner restarts hardware monitoring range based tasks on hardware monitoring module startup, on hardware monitoring history clearing and on resuming the scheduler module from pause.

Now RivaTuner no longer records scheduler events into hardware monitoring event history panel by default. Now you may enable scheduler event history logging into event history panel properties if necessary.

Now RivaTuner hides low-level overclocking tab on PowerPlay support capable display adapters (RV630 and newer series) when overclocking functionality is not available (e.g. on the secondary GPUs in Crossfire mode under Windows XP).