Download RivaTuner 2.0 RC 15.4

RivaTuner was developed a few years ago to tweak nVidia Riva TNT video cards, such as adjusting (hidden) DirectX and OpenGL setting and overclocking the memory speed and the graphics processor. Over the years, several new tweaks have been added and support has been added for the other video cards from nVidia and the Radeon series from ATi. Today Unwinder, the developer of RivaTuner, has a new version released† The update is numbered Release Candidate 15.4 of the 2.0 branch and is available via this page download from different servers. The associated changelog looks like this:

Minor bug fixes:

• Fixed crash on dual-head display adapters with display connected to the secondary RAMDAC under Windows 2000.
• Duty cycle is no longer rounded improperly when trying to apply a fan speed matching with the current one.
• Daylight saving time correction is no longer applied when viewing .hml files.
• Minor UI fixes.

what’s new:

• Added ForceWare 75.xx driver family support.
• Updated databases for Detonator and ForceWare driver families. Added databases for ForceWare 67.66, 71.22, 71.24, 71.25, 71.40, 71.50, 71.80, 71.81, 71.84, 71.90 and 75.90 drivers.
• Added Catalyst 5.1 and 5.2 detection.
• Updated Catalyst 5.1 and 5.2 certified SoftR9x00, ATIOverclockingAntiprotection and ATIOverclockingAntiprotectionRuntime patch scripts.
• Added NV4x-compatible driver-level overlay color correction.
• Added “OpenGL version string override” option to the “Compatibility” tab of “OpenGL tweaks” dialog for the Detonator 27.xx and newer drivers. This option is useful for troubleshooting and can be used to solve problems with some incorrectly written OpenGL application, expecting harcoded OpenGL version string. For example, this option can be used to launch “The Chronicles of Riddick – Escape from Butcher Bay”, which expects OpenGL 1.3 and doesn’t work properly on OpenGL 2.0 drivers like ForceWare 75.90.
• Now the list of application profiles for the ForceWare 56.xx and newer drivers in the main tab and the list of profiles accessible via the “Scan registry for existing profiles” button are sorted in ascending order.
• Now RivaTuner displays / adjusts internal model ID instead of hardwired PCI DeviceID in the NVStrap driver configuration tab when custom graphics adapter identification mode is selected on display adapters with BR02 PCI-E to AGP or AGP to PCI-E bridge.
• Added %RT% and %RTFolder% macro names support to RivaTuner’s launcher tab. These macro names can be specified to launch RivaTuner itself or to specify path to RivaTuner’s folder.
• Updated ATI and NVIDIA graphics processors’ PCI DeviceID database.
• Added an ability of starting RivaTuner’s launcher items via the command line by the name instead of GUID. The syntax is: RivaTuner.exe /L:””, where is a name of the item you want to launch. Take a note that this syntax is ambiguous, as it is allowed to create multiple items with the same name, so use it with caution.
• Improved low-level graphics subsystem diagnostic module:
  • Added PCI-E bus type detection.
  • Added maximum / current PCI-E link width detection for PCI-E display adapters.
  • Internal “NVIDIA CK804” codename is replaced with “NVIDIA nForce4 series” in RivaTuner’s northbridges database.
• Considering that some competing developers started bad practice of cloning RivaTuner’s hardware monitoring module concepts, features and even visual appearance, this version introduces bunches of hardware monitoring related user interface enhancement and new features to leave clonemakers back in the dust. The list of enhancements includes:
  • Added experimental fan voltage level monitoring for reference design NV30, NV35, NV38 and NV40-based display adapters. This graph is helpful for understanding driver-level fan speed adjustment system. Take a note than this graph is trustworthy only when the fan is physically connected to the PCB’s fan voltage control circuit. So don’t rely on this graph if you have a boards with non-reference cooling system with no software voltage-based fan speed adjustment capability (eg ASUS or MSI 6800 series).
  • Added monitoring threshold support. Now you can define unlimited count of thresholds for each monitoring data source and setup each threshold to launch any external application on upward / downward threshold crossing event. The primary aim of this feature was to give users an ability of performing emergency system shutdown when a temperature exceeds the threshold. However, considering that you may use a threshold’s command line to access to RivaTuner itself, the threshold can be configured to execute any of RivaTuner’s launcher items, so you may implement temperature based overclocking etc via newly introduced thresholds technology.
  • Considering that the graphs with multiple defined thresholds usually require more detailed Y-axis than the graphs with the rest monitored parameters (eg clock frequencies), now each graph can use either the previously available automatic height scaling mode to fit in the entire window or fixed size-height fashion. Fixed graph height mode can be activated either visually by dragging its’ upper / lower sizing border or manually by entering desired height in the graph’s properties window.
  • Added button to the bottom-right corner of fixed height graph for quick switching it to automatic height mode.
  • Added button to the top-right corner of the graph for quick closing a graph window. Take a note that this button is available only when two or more graphs are displayed simultaneously.
  • Added frame rate monitoring graph. Take a note that framerate monitoring can be implemented via API hooking only, and I treat this technology as potentially troublesome and virus-styled, affecting whole operating system and all running applications. That is why I continue “no API hooks in RivaTuner” politics, so framerate statistics collecting is performed via external RivaTunerStatisticsServer application, which must be loaded simultaneously with RivaTuner in order to monitor framerate via RivaTuner’s hardware monitoring module. Take a note that RivaTuner’s installer creates a shortcut for RivaTunerStatisticsServer in the Start menu. RivaTunerStatisticsServer can be also started via launcher by specifying %RTSS% macro as the path to the application. RivaTunerStatisticsServer v1.0 provides the following features:
    • Framerate statistics collecting for fullscreen Direct3D8 / Direct3D9 applications (for Windows XP only). RivaTunerStatisticsServer uses original OS GDI thunk hooking approach, which is not used in any of currently existing framerate monitoring software and greatly simplifies DirectX framerate monitoring implementation.
    • Framerate statistics collecting for both windowed and fullscreen OpenGL applications. Known limitations: currently total FPS is monitored when multiple windowed OpenGL applications are running simultaneously.
    • Ability to unload currently loaded RivaTunerStatisticsServer via launching new RivaTunerStatisticsServer instance with “-u” command line switch.
    • Even considering that performance impact of RivaTunerStatisticsServer is rather low (above 1%), there is still room for optimization left, so the performance impact can be and will be reduced in the future versions.
    • An ability of using RivaTunerStatisticsServer’s statistics in any other application via named shared memory. The sample code is available upon email request, sample application will be included in SDK in the next version.
  • Added range selection operations support. Now you can hold when pressing left mouse button on the first position on the graph, then move mouse cursor to the second position and release left mouse button to select this range. As soon as the range is selected, you may see its’ statistics (minimum, average and maximum values) and perform some selection-specific operations (discussed above). This feature was added special for simplifying framerate statistics analysis.
  • Added asynchronous operations support. Now all tracking markers related operations (eg manual tracking marker setting, “Mark minimum …” / “Mark maximum …” / “Remove all markers” commands) and all selection related operations can be applied to all graphs simultaneously as well as to the focused graph only. modifier is reserved for asynchronous operations now, for example left mouse button click synchronously sets tracking markers on all graphs, but + left mouse button click sets tracking marker on the focused graph only.
  • Added “Select all” / “Deselect” and “Select range” commands to the graph’s context menu. The last command is only active when two tracking markers are set in the graph and allows you to select a range between these markers.
  • Added monitoring statistics filtering functions, available via “Filter … over maximum limit” / “Filter … under minimum limit” commands from the graph’s context menu. These functions force RivaTuner to process statistics and to clean up the values, which lie outside the range specified with vertical scaling sliders. These functions were added for framerate statistics analysis simplification and they allow you to remove abnormally high or abnormally low values ​​from it (eg abnormally high framerate caused by splash screen rendering between the tests in 3DMark, or 0 framerate during level loading in Quake III).
  • Now all the commands depending on hardware monitoring statistics (eg “Mark minimum …” / “Mark maximum …” / “Scale to fit” etc) are applied to selected range only, or to whole statistics when there is no range selected.
  • Changed tracking marker removal approach. Now existing marker can be removed by double-click instead of + click, which is reserved for different purposes.
  • Optimized graph rendering code (up to 10 times faster under certain conditions).
  • Monitoring graph’s statistics is no longer reset when graphs’ list is changed or reordered.
  • Monitoring window can be maximized now by double clicking its’ caption.
  • It is no longer necessary to close RivaTuner in order to save the states of monitoring window control buttons (eg “Enable background monitoring”).
  • Added monitoring log file size limiting option.
  • Removed obsolette “Fan duty cycle” option from the data sources list in hardware monitoring setup window for RV360 based display adapters.
  • Added negative temperatures monitoring support for LM63-capable ATI display adapters.
  • Added clipping for above 100% duty cycle values ​​displayed on the monitoring graphs for LM63-capable ATI display adapters.
  • Added fan duty cycle monitoring for F75373S-capable ATI display adapters.

[break]