RivaTuner

[deathvirus_me]

Version 2.0 Final Release:

Minor bugfixes:

- Removed obsolete warning message, offering user to enable alternate startup daemon mode when applying custom LowPower 3D clock frequencies at Windows startup. New alternate daemon usage approach is no longer compatible with switching alternate startup mode on the fly, so now LowPower 3D clock controls are simply blocked when alternate startup daemon mode is disabled.
- Minor UI and localization fixes.

What's new:

- Added ForceWare 97.28 and 97.44 drivers support.
- Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 93.28 and 97.44 drivers.
- Added ForceWare 97.44 compatible gamma corrected antialiasing control.
- Added Catalyst 6.12 drivers detection.
- Updated Catalyst 6.12 certified SoftR9x00 patch scripts.
- Updated PCI DeviceID database for NVIDIA graphics processors.
- Added workaround for G80 memory clock frequency generation bug of the ForceWare 97.28 and newer drivers. Unfortunately a lot of gamers with GeForce 8800 graphics adapters seem to be unable to understand the principles of multiple hardware clocking and aggressively react on any attempts to explain it. Due to that reason now by default RivaTuner displays memory clock of the only memory clock frequency generator programmed by all versions of the ForceWare drivers. The clocks of the rest two generators, which are erroneously left by the driver in BIOS default 400MHz state, are now hidden from eyes of beginners. The power users still can monitor independent clocks of all 3 memory clock frequency generators on G80 via GPUProbe.dll plugin. And the gamers unable to get technical details may relax and continue "fellas, my new 8800 is so cool" related discussions in the forums.
- Previously available experimental driver-level overclocking workaround is now enabled by default on RV560 and RV570 based display adapters. Power users may disable it with EnableDriverLevelClockControl registry entry.
- Hardware monitoring module's screenshot watermark image is now stored into .\Graphics\Watermark instead of .\Watermark folder.
- Updated RivaTunerStatisticsServer v2.2.0 bundled utility:
- Added new pseudo 3D applications to the profiles list.
- Added RivaTuner styled startup links checking, aimed to prevent conflicts between multiple simultaneously installed versions of the server. Now the server checks the startup registry link and offers you to correct it, it if is referring to other folder.
- Added workaround for 3D applications, wasting CPU time into erroneous page flip calls (e.g. Company of Heroes during movies rendering). Now the server checks flip call status and throws failed page flip calls from the statistics to avoid registering abnormally high framerate in such applications.
Improved hardware monitoring plugin API. Now the plugins can directly access NVIDIA driver resource manager's internal configuration and extended configuration data.
- Improved hardware monitoring module:
- The list of active hardware monitoring plugins is stored in the registry instead of the configuration file. This allows avoiding reenabling the plugins when reinstalling RivaTuner while keeping the previous version's settings.
- Previously available experimental OSD and tray tooltip values grouping modes are now enabled by default. Power users may disable these modes with EnableOSDGroups and EnableTooltipGroups registry entries.
- The font used to display hardware monitoring statistics in system tray icon is no longer fixed and can be customized by user. By default RivaTuner uses intelligent font size selection algorithm and automatically chooses the best font for currently selected display mode (large 7x9 pixels raster font for 1600x... and greater display modes, medium 7x7 pixels raster font for 1280x... and greater display modes and previously used small 5x7 pixels raster font for display modes below 1280x...). However, power users may redefine this behavior and select desired font manually by editing TrayFont registry entry. Furthermore, all the fonts are stored in .\Graphics\Tray folder as bitmap files so you can easily create your own font if necessary and force RivaTuner to use it with TrayFont registry entry.
- Improved tray icon text fitting algorithm. Now RivaTuner is able to display negative values in tray icon and uses more accurate algorithm when trying to fit too large values in the icon and displays as many significant digits as possible.
- Added barchart mode for values displayed it system tray icon. Now RivaTuner may optionally display either text values or barcharts in tray icon. Barchart mode is useful for the graphs, reflecting CPU usage, memory usage, etc.
- Now "Show ... in tray icon tooltip" option affects both primary and data source icon's tooltips. Displaying text value in the data source icon's tooltip is useful in conjunction with newly introduced barchart mode.
- Improved hardware monitoring plugins:
- Improved GPUProbe.dll plugin. Now besides GPIO pin reading for NV1X - NV4X GPU families the plugin also provides MPLL0 - MPLL2 clock reading for G80 GPU family. Power users may use it for monitoring clocks of all G80 memory clock domains.
- Added NVHwAccel.dll plugin. The plugin demonstrates developers usage of newly introduces functions for accessing NVIDIA driver resource manager's configuration and extended configuration data. The plugin accesses NV_CFGEX_PERF_MODE extended configuration data and provides hardware monitoring module "Hardware acceleration" graph, showing if any application using NVIDIA driver's hardware acceleration is currently running. Power users may define the thresholds on this graph for simple 3D application events start / stop detection, e.g. when defining a threshold for separating 2D/3D fan speeds on the cards with temperature based fan controller.
- Improved low-level graphics subsystem diagnostics module:
- Added boot core clocks and memory clock for G80 VGA BIOS images to "NVIDIA VGA BIOS Information" diagnostic report category.
- Improved multilanguage engine debugging features for third party localization pack creators:
- Added localization pack comparison mode. Now third party localization pack creators can use RivaTuner's /CL or /COMPARELOCALIZATION command line switches to generate LocalizationDifferences.log, containing the list of differences between currently selected localization pack and specified one. The list of differences allows you to see which localized files or translation database entries have to be added to or removed from your localization pack when updating it for new version of RivaTuner. Please refer to "Updating localization pack" chapter of RivaTuner SDK documentation to get more detailed information.
- Special New Year present for all RivaTuner users. Direct3D triple buffering forcing feature, one of the most deeply hidden and most wanted Easter Eggs, is now unlocked and available for everybody! Deepest respect and personal thanks goes to Demirug, the developer of DXTweaker project and author of original Direct3D triple buffering concepts, for allowing it to happen. Now RivaTuner's distributive includes bundled DXTweaker concepts based D3DOverrider v1.3 tool, providing the following feature set:
- Simple, effective and beginner friendly user interface. Just start the utility and it will automatically force Direct3D triple buffering in all subsequently started applications. The utility is not limited to any OS or any graphics hardware, so it can be used for forcing triple buffering on the NVIDIA as well as on ATI graphics cards.
- RivaTunerStatisticsServer styled global and application specific profiles. You may globally enable or disable triple buffering forcing as well as do it for desired executable files only.
- Sound indication feature. D3DOverrider uses standard OS defined success and failure beeps on each back buffer count override event, allowing you to control triple buffering forcing status really easy.
- Triple buffering forcing support for fullscreen DirectDraw and DirectDraw derived Direct3D applications (DirectX7 and older).
- Triple buffering forcing support for windowed and fullscreen Direct3D8 applications.
- Triple buffering forcing support for windowed and fullscreen Direct3D9 applications.

Please take a note that D3DOverider is also included in encrypted format in the previous versions of RivaTuner, so if you're not willing to upgrade RivaTuner to a final release due to some reason, you can extract D3DOverrider from the previous versions by adding the following key to the registry then typing "RivaTuner.exe /E D3DOverrider" in the command line:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Unwinder\RivaTuner\Eas terEggs]
"86547637"=dword:72395256

Greatest thanks and the best wishes goes to all RivaTuner users, privately testing and using D3DOverrider tool during the last few years and honestly keeping their promises on not leaking it or not disclosing a key for unlocking it. I really appreciate it and deeply thank you for that.

- Added new Easter Eggs.
- FAQ updated.
- Minor UI changes and improvements.

Get it here :

Link : RivaTuner v2.0

Also , Guru3d got a contest running on Rivatuner and giving away two X1950 Pro .. go here :

Rivatuner contest 2006

Moderator Edit:

Moved thread to video cards/displays as more suitable forum, Sharpy

[Koroush Ghazi]

Thanks for the heads-up on this, I've noted it on the front page as RivaTuner is quite a popular utility. As I mention on the front page, one of the major new features is the ability to force Triple Buffering in Direct3D, for both ATI & Nvidia cards, which should help a lot of people.

I've also renamed the thread slightly so that we can keep all RivaTuner 2.0 related discussions in this thread now. I'll be interested to see the feedback from both ATI and Nvidia users as to how this goes.

/EDIT: I've clarified in my front page post that you can find more details of this new Triple Buffering 'feature' (it's actually a separate utility called 'D3DOverrider') at the bottom of this page of the Nvidia Forceware Tweak Guide which I just updated.

Basically it looks to be a very neat way of doing things, less of a hassle than DXTweaker, but for ATI users who have ATI Tray Tools they can just use that to force-enable Triple Buffering (See ATI Catalyst Tweak Guide).

And as Unwinder notes in the change details for RivaTuner 2.0, this utility was included in earlier versions and can be enabled if required without having to update to RT2.0 Final:

Please take a note that D3DOverider is also included in encrypted format in the previous versions of RivaTuner, so if you're not willing to upgrade RivaTuner to a final release due to some reason, you can extract D3DOverrider from the previous versions by adding the following key to the registry then typing "RivaTuner.exe /E D3DOverrider" in the command line:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Unwinder\RivaTuner\ EasterEggs]
"86547637"=dword:72395256

[bagman]

Hi there

In the Nvidia Forceware Tweak Guide under RivaTuner it states, relative to D3D Overrider, " By default this utility will simply sit in your system tray whenever it is launched and while it is active any Direct3D game you launch will automatically have Triple Buffering force-enabled ".

I would greatly appreciate someone confirming my understanding of this application being that there is nothing further for me to do once I have enabled V-Sync within the game ? There is no need to set Triple Buffering either in-game or in the nVidia control panel ?

Many thanks in advance

Administrator Edit:

Moved to Video Cards forum and Merged into existing Rivatuner thread - please search before posting.

[Krippledgamer]

Read this and see if it answers your questions.

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

[Koroush Ghazi]

This information is also fairly clearly laid out in the Triple Buffering section of the Gamer's Graphics & Display Settings guide - please don't post asking for 'confirmation' of a tweak, as if it is clearly explained, and with a bit of research and experimentation, you can figure this out for yourself.

[Jonas Beckman]

New version out:
http://downloads.guru3d.com/download.php?det=163

Changelog:

Minor bugfixes:

Fixed gamma correct antialiasing option for the ForceWare 1xx.xx drivers families.
Fixed 'HDD0 temperature' ... 'HDDn temperature' graph labels in SMART.dll plugin for the systems with more than one hard drive installed.
Minor UI and localization fixes.

What's new:

Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 162.18, 162.22, 162.50, 163.16 and 163.44.
Added Catalyst 7.7 and 7.8 drivers detection.
Updated Catalyst 7.7 and 7.8 certified SoftR9x00 parch script (for Windows 2000/XP drivers only).

Updated RivaTunerStatisticsServer v2.4.0 bundled utility:
Added OSD rendering support for Direct3D10 applications.
Added OSD rendering support for Direct3D9 applications redefining render target in the end of frame rendering process (e.g. Overlord). Now the server is able to detect such conditions, bind render target to back buffer, render OSD then restore the previously set render target. This feature is implemented as compatibility flag and enabled by default for all applications, however power users may disable it via editing profile flags in the server's configuration file.
Improved 3D API usage detection for applications using multiple OpenGL / Direct3D renderers (e.g. Colin McRae : DIRT). Now the server stores information about the last used renderer instead of the first one.
Updated list of pseudo 3D applications.

Updated D3DOverrider v1.4 bundled utility:
Internal hook infrastructure has been seriously changed to provide support for Vista and future operating systems.
Added experimental triple buffering forcing support for Direct3D10 applications.
Added RivaTuner's event history panel support. Now besides sound indication of triple buffering forcing success/failure events D3DOverrider is also able to display triple buffering forcing related event markers in RivaTuner's event history panel. This feature is implemented as compatibility flag and enabled by default for all applications, however power users may disable it via editing profile flags in the configuration file.

Improved hardware monitoring module:
Added generic support for Logitech G15 keyboard LCD display. Now RivaTuner automatically maps all hardware monitoring statistics displayed in the server's On-Screen Display to the keyboard's LCD display, however power users may disable this behavior with MapOSDToLCD registry entry. Also RivaTuner provides command line switches for connecting to (LCDC/LCDCONNECT) or disconnecting from (LCDD/LCDDISCONNECT) G15 LCD, allowing you to bind these actions with hotkeys and easily reconnect to LCD (e.g. after resuming PC from suspended mode). Please take a note that these command line switches are added to the list of predefined applications available in regular launch item editor.
Improved hardware monitoring plugins:
Improved LCDHype plugin. Now the plugin contains LCDHype output scripts calibrated for both AlphaCool 240x128 and Logitech G15 160x43 LCD displays.
Improved VidMem.dll plugin. Now the plugin totally hides videomemory usage graphs under Vista to avoid confusing the beginners ignoring plugin description, telling that videomemory usage monitoring is not available under this OS due to videomemory virtualization.

Added protective technologies aimed to jam unsafe memory scanner of PunkBuster anticheat system and this way prevent this anticheat system from crashing graphics hardware when RivaTuner resides in memory. Unfortunately new 1.7xx versions of PunkBuster client (debuted on 04.17.2007 with Battlefield 2142 client) caused major system stability issues in conjunction with wide range of applications accessing hardware via user mode MMIO address ranges. Apart from scanning executable code new PunkBuster services also fully scan data memory ranges of each process, which is critically dangerous when it comes to applications accessing hardware registers via memory mapped I/O port user address ranges. Unauthorized access to hardware mapped memory ranges performed by anticheat system's memory scanner may cause unpredictable results including hardware failures and freezing. The problem is not specific to RivaTuner and also covers wide range of ATI and NVIDIA oriented diagnostic, overclocking and monitoring tools (e.g. ATITool, PowerStrip, HIS iTurbo etc) developed by third parties as well as by certified AIB/AIC partners. The situation had been investigated with help of Battlefield 2142 gamers community and is fully documented in RivaTuner's support forums, however, many inexperienced gamers never visit forums or read documentation and still wrongly interpret these crashes as instability of third party tools including RivaTuner, hurting software reputation in different forums this way. Unfortunately, the problem is still neither fixed nor documented by Evenbalance, furthermore, the situation got critically worse in the end on June 2007 when Evenbalance launched the same unsafe PunkBuster clients v1.7xx for America's Army, Call of duty, Call of duty 2, Enemy territory: Quake Wars, F.E.A.R etc. Due to this sad reason I cannot longer wait for response and fix from Evenbalance and risk RivaTuner software reputation because of anticheat system issues. The following features are introduced and aimed to prevent RivaTuner from being improperly accessed by PunkBuster or any similar memory scanner:
Process protection. Now RivaTuner reduces its own access privileges after startup to prevent simple user mode memory scanners from accessing RivaTuner's process virtual memory. This protective technique is enabled by default, but it can be disabled by setting ProtectProcess registry entry to 0.
MMIO protection. Now RivaTuner hides MMIO range into kernel mode address space instead of user mode address space to prevent any other user mode application form accessing hardware improperly. This protective technique requires each graphics hardware access operation to be transferred via RivaTuner's kernel-mode driver, so it increases CPU performance hit caused by RivaTuner's background processes (e.g. hardware monitoring) with approximate factor of 3x - 5x. This protective technique is also enabled by default, but it can be disabled by setting ProtectMMIO registry entry to 0.
Paged MMIO access mode. Now RivaTuner is able to use paged access to MMIO range, mapping only desired MMIO pages for access instead of mapping whole registers aperture. This mode is only available when MMIO protection mode is disabled. Paged acces mode can be activated by specifying power-of-two page size with MMIOPageSize registry entry.
Note: most of these protective techniques will be enabled by default until the problem is fixed in PunkBuster. I realize that the protective techniques will cause side effects such as increased CPU load even to those who never play PunkBuster protected multiplayer games, but unfortunately I see no other ways of protecting software reputation against inexperienced gamers spreading rumors about RivaTuner instability. It you don't play multiplayer PunkBuster protected games or if you're not affected by crashing caused by it then it is strongly recommended to disable all the protections mentioned above.

Minor UI changes and improvements.

(Taken from http://www.guru3d.com/index.php?page=rivatuner&menu=8 )

[Chickenfeed]

Rivatuner 2.04 was released today as mentioned on the front page.

Changelog :

Version 2.04:

Minor bugfixes:

* Fixed overclocking algorithms for ATI R3xx/R4xx GPU families, broken due to MMIO protection introduced in the previous version.
* Fixed gamma correct antialiasing option for G7x GPU families, broken due to G8x related gamma correct antialiasing related changes in the previous version.
* Fixed bug in the installer script, preventing automatic update installation system from installing the updates from a folder containing spaces in the path.
* RivaTuner no longer stops working with access violation error when I/O driver is not loaded.
* Minor UI and localization fixes.

What's new:

* Updated databases for Detonator and ForceWare drivers. Added database for ForceWare 163.67.
* Added Catalyst 7.9 drivers detection.
* Updated Catalyst 7.9 certified SoftR9x00 parch script (for Windows 2000/XP drivers only).
* Added new ForceWare 163.67 overclocking interfaces support. Please take a note that by design of new NVIDIA drivers ForceWare's NVAPI overclocking interfaces no longer scale shader domain clock when raster domain clock is changed on G8x graphics processors and provides completely independent shader domain clock adjustment interface instead. It means that all overclocking tools supporting traditional overclocking interfaces (e.g. RivaTuner, ATITool or PowerStrip) change raster domain core clock only when overclocking core with these drivers. Now RivaTuner is the only third party overclocking tool supporting new independent shader domain clock adjustment interface too and able to overclock it with these drivers. Currently shader domain overclocking in RivaTuner is available for power users only and is exposed as user adjustable shader/ROP domain clock ratio represented by ShaderClockRatio registry entry. The next version of RivaTuner will provide independent shader domian clock control directly via overclocking GUI. Please take a note that by default it applies to Vista ForceWare 163.67 only, however Windows XP owners may also force RivaTuner to use Vista-specific NVAPI overclocking interfaces by setting NVAPIUsageBehavior registry entry to 1.
* Updated RivaTunerStatisticsServer v2.4.1 bundled utility:
o Added OSD coordinates bounds checking to Direct3D10 OSD rendering code. This feature is provided as a workaround for some early Direct3D10 drivers not performing internal bounds checking of supplied data and tending to work improperly when OSD is rendered outside the screen.
o Improved race condition preventing algorithm in the hooking system. New algorithm improves compatibility with multithreaded rendering engines (e.g. Bioshock) calling frame presentation routine concurrently from different threads.
* Updated D3DOverrider v1.5 bundled utility:
o Considering that triple buffering is normally being used in conjunction with vertical synchronization, now D3DOverrider gives you options for forcing VSync for DirectDraw, Direct3D8, Direct3D9 and Direct3D10 applications. Similar to triple buffering forcing options, new VSync forcing options are fully hardware and OS independent and can be used to force VSync under any OS on both NVIDIA and ATI GPU based display adapters.
o Similar to triple buffering forcing events, VSync forcing events are also automatically sent to RivaTuner's event history panel. Please take a note that it applies only to Direct3D8 and Direct3D9 VSync forcing events which are performed once per application lifetime. DirectDraw and Direct3D10 VSync forcing events are performed at per-frame due to specifics of DirectDraw and Direct3D10 API so they are not reflected into event history panel.
o Improved race condition preventing algorithm in the hooking system. New algorithm improves compatibility with multithreaded rendering engines (e.g. Bioshock) calling frame presentation routine concurrently from different threads.
* Improved hardware monitoring module:
o Improved event history panel. Now event history panel's tooltips are able to display text for multiple application specific even markers registered in the same time (e.g. triple buffering and VSync forcing events sent to event history panel by D3DOverrider).
* Added Vista power broadcast messages support. Now suspended mode related features like pausing monitoring module in suspended mode and restoring various settings after suspended mode are also available under Vista.
* Improved installer. Now the installer allows altering PunkBuster related protective options, so you can easily disable the protections completely if you don't play and games with PunkBuster or you can reduce protection level if you use some security related software products blocking protected processes activity.
* Added update installation logging feature. Now RivaTuner fully documents process of each update installation into Updates.log file in the application folder.
* Minor UI changes and improvements.

Download here : http://www.guru3d.com/index.php?page=rivatuner

This version now allows independent shaderclock adjustment on 8 series gpus with the newest 163.67 beta driver. Previous versions didn't allow shaderclock adjustment under vista.

This thread here on the rivatuner forums explains how to adjust the shaderclock http://forums.guru3d.com/showpost.ph...33&postcount=5

This will be simplified by means of a slider in the next revision.

[Whizzer]

The next revision of RivaTuner was released already some days ago it seems. Version number is 2.05 and the changes are numerous as always. Support for 163.69 and 163.71 has been added and the shader overclock trick on nVidia 8000 series has been refined with some more info in the change notes below.

Version 2.05:

Minor bugfixes:

* Fixed I2C write routine for ATI R600 graphics processors family, which has been erroneously commented the previous version's source code.
* Minor UI and localization fixes.

What's new:

* Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 163.69 and 163.71.
* Improved driver-level overclocking module for NVIDIA display adapters:
o Added new user interface for independent G8x GPU family shader clock control interfaces of the ForceWare 163.67 and newer drivers. New UI includes:
+ New independent slider for adjusting shader domain clock.
+ New "Link clocks" option allows you to use either traditional shader/ROP clock ratio based overclocking or completely asynchronous shader/ROP clock overclocking. Now you may either tick "Link clocks" options and adjust ROP clock only, allowing RivaTuner to overclock shader domain using VGA BIOS default shader/ROP clock ratio similar to pre-163.67 drivers, or untick "Link clocks" options and adjust domain clocks fully independently.
+ New overclocking profile format supporting independent shader clocks. Please take a note that old overclocking profiles are not supported by RivaTuner, so you must recreate previously existing overclocking profiles.
o Previously available power user oriented ShaderClockRatio registry entry is now obsolete and it no longer exists in RivaTuner's database. Previously available ratio based shader domain overclocking functionality is now fully covered by new independent shader clock slider and new "Link clocks" option.
o New user interface is provided by default under ForceWare 163.67 and newer drivers under Windows Vista, however Windows XP owners can also force Vista specific overclocking interfaces usage by setting NVAPIUsageBehaviour to 1. If needed, shader clock control can be forcibly disabled and old traditional overclocking module UI appearance can be forced by setting NVAPIShaderClockControl to 0.
o Power user oriented adjustable minimum and maximum clock slider limits have been expanded from 25%-300% to 10%-800%.
o Added experimental SLI overclocking for Vista. Please take a note that I have no SLI rig for testing and development, so this feature has been added blindly and RivaTuner still doesn't provide official SLI support.
* Minor UI changes and improvements.

[Chickenfeed]

Rivatuner 2.07 was released today as mentioned on the front page.

Changelog :

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:
o 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).
o 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.
o 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:
o 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:
o 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.
o 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.
o 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:
o 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.
o 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:
o 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.
o 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.
o 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.
o 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:
o 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.
o 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.
o Added Direct3D10 (for non-multisampled frame buffers only) screen capture support.
o 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.
o Now the server is able to capture multiple screenshots at once if multiple 3D applications are running simultaneously.
o 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.
o 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.
o 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.
o Updated list of pseudo 3D applications.
* Improved hardware monitoring module:
o Now "Framerate" graph shows framerate from the focused application if there are multiple 3D applications running simultaneously.
o Added SEH for clock calculation routines for better protection against incorrect hardware emulation.
o Changed default Core/Memory clock graph ranges from 1.5GHz to 2GHz.
o 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:
o 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.

Yet to try it out but these are some nice changes, particularly the new task scheduler. Its also nice to see that hes made it more UAC friendly for Vista users. The feature in this release that I've been waiting eagerly on is the SLI multi fan support. To this point, when using SLI under Vista ( and I believe in certain circumstances under XP ) you were only able to adjust one fan in Rivatuner. The only work around was to also use Ntune to set the other fans speed manually however this was irritating as it required you to do this everytime the machine started up. Hopefully it works okay but considering he is adding this support without having an SLI system to work with, thats pretty impressive.

[Snarl]

New version 2.20 is out;

Download: http://downloads.guru3d.com/RivaTune...nload-163.html

Read: http://forums.guru3d.com/forumdisplay.php?f=18