RivaTuner v2.07

Unwinder · *Last edited by Unwinder; 03-05-2008 at 12:22.*

Dear forum visitors,

RivaTuner v2.07 is ready for release and available for download.

Download - Click here
Faq/Infos - Click Here

Changes list includes:

Version 2.07:
Minor bugfixes:
Fixed default values for Direct3D Intellisample slider and "Clamp negative mipmap LOD bias" option.

State of global OSD visibility setting is no longer lost when any other option is being changed immediately after changing the global OSD visibility setting in the properties of bundled RivaTunerStatisticsServer application.

Minor UI and localization fixes.

What's new:
Added ForceWare 171.xx, 173.xx and 174.xx drivers families support.

Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 169.09, 169.13, 169.17, 169.21, 169.25, 169.28, 169.32, 169.38, 169.39, 171.16, 171.17, 171.23, 173.65, 173.80, 174.12, 174.13, 174.16, 174.23 and 174.31.

Added Catalyst 7.11, 7.12, 8.1 and 8.2 drivers detection. Please take a note that both Catalyst 8.1 and 8.2 share the same binary file versions, so both Catalyst 8.1 and 8.2 will be detected as Catalyst 8.1 or newer.

Updated Catalyst 7.11, 7.12, 8.1 and 8.2 certified SoftR9x00 patch script (for Windows 2000/XP drivers only).

Updated PCI DeviceID database for both ATI and NVIDIA graphics processors. Added PCI DeviceIDs for RADEON 2600XT AGP, RADEON 2900GT, RADEON HD 3870 X2 and GeForce 8800GTS 512 SKUs. Please take a note that RivaTuner doesn't provide official Crossfire support, so RADEON HD 3870 X2 support can be limited to single GPU functionality under certain conditions.

Unlocked previously available experimental RV635 graphics processors support. Thanks to Andrey Vorobiev for testing RivaTuner with ATI RADEON HD3650.

Added experimental G94 graphics processors support. Thanks to Andrey Vorobiev and Hilbert Hagedoorn for testing RivaTuner with NVIDIA GeForce 9600GT.

Added powerful built-in task scheduler module. Task scheduler has been designed as more flexible and more programmable replacement for the previously available programmable monitoring thresholds technology, providing you the following functionality:
Ability to automate startup of any desired application (e.g. RivaTunerStatisticsServer) or launch item (e.g. combination of fan and overclocking profiles or shortcut to RivaTuner's hardware monitoring module GUI) on specified schedule. The following schedule types are currently supported:
Run task at Windows startup. This schedule type can be used as a replacement for RivaTuner's own "Run ... at Windows startup" options by means of loading desired overclocking / fan / color profiles as well as for programming additional sophisticated tasks (e.g. for programming VRM module at OS startup by means of RivaTuner's command line interface for direct access to GPU registers).

Run task at RivaTuner startup. This schedule type can be used to automate startup of some applications, which you need to run in conjunction with RivaTuner only (e.g. RivaTunerStatisticsServer) or for activating some GUI windows (e.g. Hardware monitoring window) at RivaTuner startup.

Run task at RivaTuner shutdown. This schedule type can be used to automate shutdown of some applications, which you need to run in conjunction with RivaTuner only (e.g. RivaTunerStatisticsServer).

Run task on entering suspended mode. This shedule type can be used as a workaround for some driver and hardware-specific issues (e.g. some old ATI display adapters don't resume from suspended mode properly when entering it in overclocked state).

Run task on leaving suspended mode. This schedule type can be used as a replacement for RivaTuner's own "Restore ... after suspended mode" options by means of loading desired overclocking / fan / color profiles as well as for programming additional tasks (e.g. for reconnecting RivaTuner to G15 LCD after resuming from suspended mode).

Run task on hardware monitoring threshold event. This schedule type replaces previously available programmable monitoring thresholds and it can be used for programming different dynamic overclocking / fan control / gamma correction algorithms depending on different monitored parameters (e.g. dynamic fan control depending on temperature threshold or dynamic clock control depending on hardware acceleration threshold).

Run task on hardware monitoring range event. This schedule type provides you alternate way for programming different dynamic overclocking / fan control / gamma correction algorithms depending on different monitored parameters, which can be more convenient in case of using multiple thresholds (e.g. when you define dynamic fan control rule based upon 3 or more thermal zones).

Standard safety measures, allowing you to skip scheduled tasks if necessary (e.g. if you have programmed loading a profile with too agressive overclocking at Windows startup or if you have programmed RivaTuner to close itself at startup). You can hold <Ctrl> key after logging in Windows to skip RivaTuner's tasks scheduled to be started with Windows or you can hold <Ctrl> key during RivaTuner startup to skip RivaTuner's tasks scheduled to be started with it.

Better thresholds visualisation features comparing to the previously available technology:
Now threshold visualitation can be optionally disabled in the corresponding schedule properties.

Now programmed threshold crossing direction is visualised on the graph.

Improved built-in launcher module:
Predefined applicaitons list has been removed from the regular launch item editor window. Now the list of predefined applications is integrated directly in file system browser window accessible via the "Browse" button.

Improved experimental SLI support. Please take a note that I have no SLI rig for testing and development, so all SLI related improvements are done blindly and RivaTuner still doesn't provide official SLI support:
Added workaround for NVAPI GPU handle leak issue under Windows XP. It is no longer necessary to disable NVAPI usage and loose independent shader domain overclocking features to get multi-GPU overclocking working under Windows XP.

Added driver-level NVAPI multi-GPU fan control. Now RivaTuner synchronically applies the same driver-level fan settings to all graphics processors in SLI configuration. Please take a note that it applies to driver-level fan control only, low-level fan tweaks such as custom automatic fan control rule can be applied to the physically selected display adapter only.

Now you can disable driver-level NVAPI multi-GPU clock control and fan control via NVAPIMultiGpuClockControl and NVAPIMultiGpuFanControl registry entries if necessary.

Improved compatibility with Vista UAC:
Now RivaTuner can be started at Windows Vista startup via special wrapper application, which doesn't require full administrative privileges and which is not being blocked by UAC's startup infrastructure. Please take a note that RivaTuner itself is still the administrative application so it still requires your evaluation during each startup; wrapper application usage just changes the way of evaluating RivaTuner launch during each OS startup. Now you will see standard UAC evaluation message when Windows starts instead of seeing a message about blocked application in the tray. Take a note that by design of UAC evaluation messages automatically get canceled after 120 seconds timeout, so avoid using new mode if your system is booting itself without your control. The previous startup mode can be also enabled via setting RivaTunerWrapperUsageBehavior to 0.

Added power user oriented RequestedExecutionLevel registry entry, allowing changing RivaTuner's execution level without editing the manifest file. This feature can be useful for those who schedule RivaTuner to be started with full administrative rights via other applications like Vista Scheduler.

Improved RV6xx graphics processors family support:
Extended list of tweakable automatic fan speed control rule parameters for RV6xx fan controllers. Now besides editing previously available thermal lookup RivaTuner can be also used to alter automatic fan speed control mode and select either temperature transfer function mode or thermal lookup mode as well as tweak parameters for temperature transfer function mode (minimum duty cycle, minimum temperature, temperature slope etc.). These settings allow power users to fix infamous HD 38x0 BIOS automatic fan control issues without flashing so called fan fix BIOS.

Personal note for unlucky owners of 38x0 bugware (yes, it is not a typo and I really meant bugware, not hardware):

Problems in your display adapter's BIOS won't magically disappear and it won't start working itself automatically after installing RivaTuner, you need to calibrate fan controller manually in order to fix automatic fan speed adjustment. RivaTuner provides you the features allowing you to access fan controler directly and fix problems at software level, but it doesn't do all the job automatically for you.
So you may either read instructions in the post #4 to understand fan controller calibration procedure or continue whining about broken fan control in RT and continue waiting for alternate ATI fan control tools.

Added direct access to ATI RADEON HD 2xxx/3xxx flashrom chips. Now you can use RivaTuner's /BI command line switch for dumping VGA BIOS image on ATI RADEON HD 2xxx/3xxx family display adapters.

Now RivaTuner uses additional reference dividers to provide correct core clock frequency reading on ATI RADEON HD 3870 series after flashing BIOS with PLL VCO divider fix.

Now RivaTuner restores default clocks when disabling low-level hardware overclocking by means of the driver's PowerPlay table reset if possible.

Updated RivaTunerStatisticsServer v2.5.0 bundled utility:
Now the server supports %FRAMERATE% macro in the OSD text slot, allowing it to display application specific framerate and 3D API usage information instead of shared framerate and 3D API usage information directly sent to OSD by the client application. Power users may prevent RivaTuner from using %FRAMERATE% macro via the EnableFramerateMacroEncoding registry entry.

Now the server is able to detect client specific framerate rendering requests and disable own statistics rendering in this case to prevent duplicating framerate info in the OSD.

Added Direct3D10 (for non-multisampled frame buffers only) screen capture support.

Extended list of supported screen capture formats. Now the server is able to capture screenshots in *.jpg and *.png formats for Direct3D9 and Direct3D10 applications. Please take a note that these formats can be also specified while capturing desktop, DirectDraw, Direct3D8 ans OpenGL screenshots, but in fact it will result in storing .bmp file with *.jpg or *.png extensions.

Now the server is able to capture multiple screenshots at once if multiple 3D applications are running simultaneously.

The server's startup routine is no longer trying to precache Direct3D10 runtime info under Windows XP to reduce startup time under this OS and avoid stealing the focus from other running applications.

Improved compatibility with applications using multithreaded 3D engines. Reduced risk of crashing the server when unloading it while such 3D application (e.g. Lost Planet : Exteme condition) is running.

Now the server is able to provide per-frame frametime statistics of any 3D application to automated third party benchmarking applications (e.g. TPUBench) via the named pipe.

Updated list of pseudo 3D applications.

Improved hardware monitoring module:
Now "Framerate" graph shows framerate from the focused application if there are multiple 3D applications running simultaneously.

Added SEH for clock calculation routines for better protection against incorrect hardware emulation.

Changed default Core/Memory clock graph ranges from 1.5GHz to 2GHz.

Improved NVThermalDiode.dll hardware monitoring plugin. Now the plugin supports G84, G86, G92 and G94 thermal diodes. Please take a note that G92 thermal diode calibration logic seem to be broken in this GPU, that is why the plugin uses approximated conversion of raw G92 thermal diode reading to temperature similar to ASUS SmartDoctor software. Such approximated conversion can be really inaccurate, that is why it is strongly recommended to use the plugin only on non-reference design G92 based display adapters not equipped with external ADT7473 sensor.

Improved driver-level fan control module:
Now driver-level fan profiles can be used for storing and recalling automatic fan control mode.

Now all low-level profiles are linked with target display device by physical display adapter location identifier instead of logical display adapter name. Due to this change all previously created low-level profiles will be invisible to new version and you will need to recreate them.

Improved generic RivaTuner file format. Now all RivaTuner's files based upon this format (i.e. database build scripts, databases, presets and patch scripts) can use global autoincremental indices similar to previously supported local autoincremental indices, which greatly simplify large files editing and updating.

Improved context help source format. Now all context help topics added to new version are represented by separate .RTF file to simplify context help translation process for third-party localization packs creators.

MMIO protection fallback warning is no longer displayed on any MMIO range allocation failure, unprotected MMIO failure warning message has been added.

Now power users may customize the range of scanned PCI buses to allow using RivaTuner with some sophisticated mainboards having more than 16 physical PCI buses. By default RivaTuner scans just the first 16 PCI buses for display adapter presence, however power users may extend the range of scanned PCI buses using the MaxPCIBusNum registry entry.

Protected tabs (i.e. the tabs like "Main" in the main property sheet that cannot be hidden) are now displayed in preview area of the tab order customization window.

Updated Easter Eggs.

Minor UI changes and improvements.

roguesn1per · 03-03-2008, 10:23 | posts: 9,514 | Location: Aussie Perth WA

Nice work.!

Rammstein · 03-03-2008, 10:35 | posts: 408 | Location: Germany, Munich

thanks a lot. I will try it out today.

Unwinder · *Last edited by Unwinder; 03-07-2008 at 08:16.*

Considering that advanced RV6xx fan controller’s parameters are not documented anywhere, I provide short summary for those who’ll be tweaking it. Now besides previously available standard thermal table defined by lookup entry 0 .. lookup entry 7 parameters you'll have access to additional parameters of RV6xxx automatic fan controller:

PWM mode - defines fan control mode (fixed, automatic etc). The controller supports 2 different automatic control modes defined by values 2 and 3, it is NOT recommended to use other values. Value of 2 enables automatic temperature transfer function mode, value of 3 enables automatic thermal lookup table mode.
Duty cycle 100% - defines duty cycle maximum in relative units, which will be internally mapped by the controller to 100%. This value directly affects amount of possible duty cycle gradations (i.e. Duty cycle 100% = 3 means that fan controller is able to set duty cycle to 0 (0%), 1 (33,3%), 2 (66.6%) and 3 (100%). This value also indirectly affects transfer function based automatic fan speed adjustment mode.
Duty cycle spinup – defines spinup duty cycle.
Duty cycle min - defines minimum fan duty cycle for temperature transfer function mode.
T min - defines minimum temperature for temperature transfer function mode.
T max - defines maximum temperature for both automatic modes and fixed mode. When this value is exceeded, fan control circuit is forcibly switched into fixed 100% mode.
T slope - defines temperature slope for temperature transfer function mode.
T hysteresis - defines temperature hysteresis for both automatic modes.

Temperature transfer function uses the following equation for automatic fan duty cycle adjustment:

Duty_cycle = Duty_cycle_min + 6.25 * (T - T_min) * T_slope / Duty_cycle_100%

There is one more parameter affecting transfer function based automatic fan control scheme and important for understanding the nature of infamous auto fan speed control bug existing in reference 3850/3870 BIOS images. This parameter is called spinup duty cycle and it defines initial duty cycle used by controller to spin up the fan during engine start. This parameter is required because due to fan engine nature it is physically impossible to start it on any desired duty cycle. The minimum duty cycle allowing starting fan engine is called spinup duty cycle and it is equal to 30% in reference BIOS images. This parameter is critically important and shouldn't be altered. In transfer function based automatic fan control mode fan control logic sets fan duty cycle to Duty cycle spinup when temperature is entering [T_min - T_hysteresis;T_min] range to allow the fan engine to spin up properly before starting actually autoadjusting the fan speed. Here we've came to the reason of our bug:
Reference HD 38x0 BIOS images have T_min set to 0 and T_hysteresis set to 4, which makes T_min-T_hysteresis difference negative. Fan controller cannot handle negative value properly so it is always trying to spin up the fan instead of autoadjusting it. Easiest way of fixing this problem and getting auto fan speed control working would be making T_min-T_hysteresis difference positive (e.g. by setting T_min to value greater than T_hysteresis or by setting T_hysteresis to 0).
If you're going to tweak and understand transfer function deeper, I'd recommend to start from programming fan controller to use 1-to-1 transfer function by setting the following parameters:

PWM mode = 2
Duty cycle min = 0
T min = 0
T slope = Duty cycle 100% / 6.25 (e.g. 22, if your Duty cycle 100% is set to 135 by default)
T hysteresis = 0

After applying these settings, fan duty cycle must follow temperature almost 1-to-1:

Then you can tweak Duty cycle min, T min and T slope seeing how they affect your fan duty cycle.

Please take a note that RV6xxx fan controller is designed to work in passive mode and stop fan completely when temperature is below T_min. However, each ASIC sample has different thermal characteristics and during manufacturing minimum allowed fan PWM output seem to be is fused into each ASIC sample. In other words, it means that fan controller will ignore all attempts to set duty cycle to value below ASIC's fused minimum. So fans on such display adapters may spin even when automatic fan controller is shutting the fan down (i.e. when duty cycle is set to 0%) or when duty cycle is manually set to 0%.

P.S. I remind users that automatic fan control rule parameters editing is a power user oriented feature so parameters editing is locked by default. You can unlock it by setting AutoFanSpeedControl value to 3 in the "Power user" tab and restarting RivaTuner.

P.P.S. AMD definitively have a talent of doing things improperly. One more bug affecting fan control (both fixed and automatic) have been found in some VGA BIOS images of 38x0 bugware series.

== x86 == · 03-03-2008, 11:25 | posts: 161 | Location: Indonesia

grab it right now... thanks a lot!!!

ToKa · 03-03-2008, 11:29 | posts: 17

thanks Unwinder

YWAGMOTH · 03-03-2008, 11:33 | posts: 621

i can´t set temps so i can have autofanspeed,is there a bug here?
it doesn´t give me the option

EnF70 · 03-03-2008, 11:59 | posts: 20 | Location: Ireland

Thank you for the new release.

TheHunter · 03-03-2008, 11:31 | posts: 13,439 | Location: √╥²

w00t i was kinda hoping it would be released soon, thanks

cowie · 03-03-2008, 12:02 | posts: 10,880 | Location: new jersey

very many thanks
now to re-install my 780i
happy you make me icant tell you enuff

YWAGMOTH · 03-03-2008, 12:10 | posts: 621

i can´t set temps so i can have autofanspeed,is there a bug here?
it doesn´t give me the option

anyone with this problem to?

Unwinder · 03-03-2008, 12:40 | posts: 10,322 | Location: Taganrog, Russia

If you have non-reference 8800GT with no ADT7473 installed - forget about fan control. And check this thread:

http://forums.guru3d.com/showthread.php?t=251554

Joshua · 03-03-2008, 12:42 | posts: 6,830 | Location: Seattle, WA

Awesome. Thanks UW.

YWAGMOTH · 03-03-2008, 12:56 | posts: 621

Quote:

If you have non-reference 8800GT with no ADT7473 installed - forget about fan control. And check this thread:

http://forums.guru3d.com/showthread.php?t=251554

but with rivatuner 2.06 it work just fine,what´s the deal with this one?

Unwinder · 03-03-2008, 13:02 | posts: 10,322 | Location: Taganrog, Russia

Quote:

Originally Posted by YWAGMOTH

but with rivatuner 2.06 it work just fine,what´s the deal with this one?

Then explain why do you mean by "can´t set temps so i can have autofanspeed".

YWAGMOTH · 03-03-2008, 13:08 | posts: 621

everything is fine except i don´t get this option in the picture

Unstable_Hero · 03-03-2008, 12:59 | posts: 1,561

Thanks unwinder!

Unwinder · 03-03-2008, 13:16 | posts: 10,322 | Location: Taganrog, Russia

I don't see the picture. I hope you don't mean thresholds customization options, which are no longer available in hardware monitoring graphs properties? If you do then please reread release notes - this UI has been removed because the functionality is now fully replaced by new task scheduler module.

Unstable_Hero · 03-03-2008, 13:18 | posts: 1,561

where are the screenshot options?

doodle333 · 03-03-2008, 13:22 | posts: 458 | Location: stockport,uk

fan settings in SLI work on 2x 8800 GTX. I mean both fans are on 75%
thanks for all your work Unwinder.

Unwinder · 03-03-2008, 13:24 | posts: 10,322 | Location: Taganrog, Russia

Quote:

where are the screenshot options?

Nothing changed in this area, like before screenshots can be captured by StatisticsServer's command line options. You can create Launch item to add screenshot capture item to tray menu or associate it with a hotkey. To do it:

Open Launcher tab -> Add regular item -> tick "Associated application" -> Click Browse -> Select screen capture action from the list of predefined applications.

YWAGMOTH · 03-03-2008, 13:32 | posts: 621

in rivatuner 2.07 i get this

so there is no menu for me to set temps and apply them a certains fanspeed

Bhairava · 03-03-2008, 13:52 | posts: 221 | Location: ITALY

Finilly i can post.
Hi thanks for this release. I getting crazy trying monitoring 3870 fan cycle.
I read your little guide and i tried to follow your raccomandation

PWM mode = 2
Duty cycle 100% = default
Duty cycle spinup = default
Duty cycle min = 0
T min = 0
T slope = Duty cycle 100% / 6.25 (e.g. 22, if Duty cycle 100% is set to 135 by default)
T hysteresis = 0

With this parameters fan is fixed on 47%, i tried to change them in every possible combination, (keeping T min larger than T hysteresis) but fan cycle do not follow temperature table. Fan cycle is fixed sometime to 41%, sometime to 51%, and increase when i close 3d application and the temperaure drop down.
Thank you for your answer.

Unwinder · 03-03-2008, 14:06 | posts: 10,322 | Location: Taganrog, Russia

Quote:

Originally Posted by Bhairava

With this parameters fan is fixed on 47%, i tried to change them in every possible combination, (keeping T min larger than T hysteresis) but fan cycle do not follow temperature table.

Please reread post #4 carefully, you're misunderstanding the controller's settings. While operating in PWM mode 2 (transfer function mode) fan controller is not supposed to follow thermal lookup table, PWM mode 3 serves for that. And the parameters given in that post are provided for better understanding of temperature transfer function based mode.
I strongly recommend everyone to avoid experimenting with fan controller if you don't understand the instructions completely or partially, otherwise you can hurt your system.

TheHunter · 03-03-2008, 14:10 | posts: 13,439 | Location: √╥²

i usually just manually override auto fan speed to fixed and set it to 75%, then set it to autostart... problem solved