RivaTuner v2.20 Released!

[Mem]

Minor bugfixes:

* Fixed incorrect 2x effective memory clock multiplier for RADEON HD 4870 / 4870 X2 series equipped with QDR DDR5 memory.

What's new:

* Added ForceWare 178.xx and 180.xx drivers families support.
* Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 178.13, 178.15, 178.24, 180.10, 180.20, 180.42, 180.43, 180.44, 180.47 and 180.48.
* Added Catalyst 8.9, 8.10 and 8.11 driver families detection.
* 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.
* Updated PCI DeviceID database for both AMD and NVIDIA display adapters.
* Added NVIDIA G98 graphics processors support.
* Added AMD RADEON HD 4830 display adapters family support.
* Added support for direct assess to flashrom chips of AMD RV7xx graphics processors family.
* Updated exceptions list for bundled D3DOverrider utility.
* 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:
o 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.
o 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.
+ Added set of new hardware access functions allowing the plugins to access multiple physical display devices simultaneously and provide multi-GPU monitoring.
+ 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).
o Improved software TSS calibration algorithm for RV7xx graphics processors family.
* Improved launcher module:
o 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.
o 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:
o 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.
o New 'Pause scheduler' module allows you to suspend the scheduler's activity if necessary.
o 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.
o 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.
o 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.
o 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.
* Improved low-level hardware overclocking module for ATI display adapters:
o 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).
o Now RivaTuner locks obsolete options in additional overclocking properties on PowerPlay support capable display adapters (RV630 and newer series).
* Now undocumented command line based hardware access interfaces also support queued current display device selection via /SD and /SELECTDEVICE command line switches.
* More tweaks improving target value generation accuracy have been done into floating point duty cycle calculation routines for all types of internal and external fan controllers.

Link.

 

[aatf510]

Neat! Just in time for the 180 series driver release!

 

[PeanutButter]

About time! Maybe my scheduler will actually work right this time.

 

[LittleNemoNES]

I don't know what values to use for the sampling period.
What would be considered the default values?

 

[Psynaut]

I have it set to bring my GPU fan speed up at 70% on boot-up, but it only does it when booting up fresh, and not when coming up from sleep mode in Vista, where it resets it to the stock 30% every time. It would be nice if they fixed this.

 

[cmdrdredd]

I wish there was a way to use Rivatuner in conjunction with ATI's little utility that can tell when you're running a 3D app or not so that I could overclock past 790/1100 but still down clock to 500/900 when just using 2D. I don't want to have to keep doing it manually by enabling a profile each time I want to game. I want it automatic.

 

[IcePickFreak]

Originally posted by: cmdrdredd
I wish there was a way to use Rivatuner in conjunction with ATI's little utility that can tell when you're running a 3D app or not so that I could overclock past 790/1100 but still down clock to 500/900 when just using 2D. I don't want to have to keep doing it manually by enabling a profile each time I want to game. I want it automatic.

You should be able to do this, just set it in the fps, say when fps>10. It only registers fps when in d3d or opengl so that's the only time you'll be at more than 10 fps. I use to use this method with no issues. The only reason I went back to manual is I don't need to OC my card for everything I play.

 

[cmdrdredd]

Hrm...yeah I could do that but never thought about it...


Actually I did it by enabling hardware acceleration monitoring. When it's @ 1 which means it's using hardware acceleration it clocks up and when it's at 0 it goes down. Every game when run uses hardware acceleration these days and 2D wouldn't need the higher clock speed.

Seems good to go, even works in a window (tested using furmark)

500/900 default
800/1120 overclock

 

[zagood]

Originally posted by: cmdrdredd
I wish there was a way to use Rivatuner in conjunction with ATI's little utility that can tell when you're running a 3D app or not so that I could overclock past 790/1100 but still down clock to 500/900 when just using 2D. I don't want to have to keep doing it manually by enabling a profile each time I want to game. I want it automatic.

Set Hardware Acceleration=1 in Scheduler. You need to have the statistics server running (you would if you used the FPS trick anyway).

guide to help:
http://www.vaguetech.com/index.php?pageid=rt207

-z

 

[cmdrdredd]

Originally posted by: zagood

Originally posted by: cmdrdredd
I wish there was a way to use Rivatuner in conjunction with ATI's little utility that can tell when you're running a 3D app or not so that I could overclock past 790/1100 but still down clock to 500/900 when just using 2D. I don't want to have to keep doing it manually by enabling a profile each time I want to game. I want it automatic.

Set Hardware Acceleration=1 in Scheduler. You need to have the statistics server running (you would if you used the FPS trick anyway).

guide to help:
http://www.vaguetech.com/index.php?pageid=rt207

-z

Thanks, I figured that out just a minute ago and set 2 profiles. One runs when HW accel is 0 and one runs when it is at 1.

I'm surprised I had not ever thought about this before. *shrug*