RivaTuner Changelog

What's new in RivaTuner 2.24

Feb 26, 2009
  • Minor bugfixes:
  • Fixed bug in hardware monitoring module causing hardware monitoring based scheduled tasks to be ignored due to improper initialization on RivaTuner startup.
  • Fixed erroneous 100MHz memory clock reading on G9x GPU series based display adapters caused by bug in memory clock frequency generator source clock detection code.
  • File system redirection is no longer disabled when executing a patch script under 64-bit OS to prevent the issues with missing file system browser dialog when pressing the "Continue" button.
  • Heights of sticky graphs in the group are now updated properly when manually editing fixed graph height settings in the properties of any graph of the group.
  • Fixed bug into startup daemon routine of RivaTunerStatisticsServer and D3DOverrider utilities causing these tools to be started and reside in memory without displaying tray icon under certain conditions.
  • What's new:
  • Added database for ForceWare 182.06.
  • Added Catalyst 9.2 drivers family detection.
  • Updated PCI DeviceID database for ATI display adapters.
  • Improved Logitech G15 keyboard LCD support in hardware monitoring module:
  • RivaTuner no longer maps OSD text to Logitech keyboard LCD, now there is separate "Show in LCD" option in the data source properties window allowing you to define independent output configurations for OSD and LCD. Previously available power user oriented MapOSDToLCD regitry entry is no longer in use.
  • Previously available power user oriented LCD font size adjustment option is now also available in the data source properties.
  • New dynamic LCD re-connection mode ensures proper LCD output when LCD software is being restarted dynamically.
  • Added heuristic on-die fan PWM controller detection for G92 based display adapters to provide proper low-level fan control and reference fan duty cycle monitoring for both reference desing and alternate display adapters using the fan connected to alternate on-die PWM controller (e.g. Palit GeForce 9800GT series).
  • Improved detection algorithms for core and memory clock frequency generators switching to PCIE bus clock on NV40 and newer NVIDIA graphics processors. The algorithms are still experimental, so both core and memory clock frequency generator bypassing detection can be forcibly disabled via EnableNVPLLBypassingDetection and EnableMPLLBypassingDetection registry entries.
  • Updated RivaTunerStatisticsServer v3.1.1 bundled utility. This version is a maintenance release, it doesn't contain new features besides the fix mentioned above.
  • Updated D3DOverrider v2.0.1 bundled utility. This version is a maintenance release, it doesn't contain new features besides the fix mentioned above.

New in RivaTuner 2.23 (Feb 16, 2009)

  • Minor bugfixes:
  • Fixed abnormal negative VRM temperature reading for temperatures above 128°C in VT1103 plugin.
  • Data sources is no loner erroneously displayed twice in the list of data sources in hardware monitoring history setup window after disabling data source, enabling it and pressing "Defaults" button.
  • Data source setup button is no longer grayed in hardware monitoring history setup window when localized GUI is selected.
  • Localization database host resize tokens are no longer ignored in hardware monitoring history setup window when localized GUI is selected.
  • Fixed bug in hardware monitoring log file viewer causing empty graphs to be displayed when opening multi-GPU log file on single-GPU system.
  • Fixed idle memory clock frequency detection for G9x GPU based systems supporting memory clock frequency generator switching to PCIE bus clock (e.g. GeForce 9800GTX+ series display adapters).
  • Minor localization and GUI fixes.
  • What's new:
  • Added ForceWare 182.xx drivers family support.
  • Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 181.20, 181.22 and 182.05.
  • Added Catalyst 9.1 drivers family detection.
  • Updated PCI DeviceID database for NVIDIA display adapters.
  • Added reference fan duty cycle monitoring and low-level fan control tab for G92 based display adapters using integrated on-die fan controller (e.g. GeForce 9800GTX series). Please take a note that low-level fan control tab for display adapters using integrated fan controller is provided only as a workaround allowing you to control the fan if the drivers are completely unable to do it. It is strongly not recommended to use low-level fan control for integrated fan controllers if driver-level fan control functions properly.
  • Added heuristic driver version detection for unattached display devices (for example the secondary GPUs in SLI/Crossfire mode invisible to OS) under Windows Vista.
  • Improved driver-level overclocking and fan control for NVIDIA multi-GPU systems. Thanks to Jacob Freeman @ EVGA for providing GeForce 9600GT SLI system for new features development and debugging. Multi-GPU related improvements include:
  • Added optional independent driver-level overclocking and fan control support for display adapters working in SLI mode. Now RivaTuner provides independent driver-level overclocking and fan control by default for the secondary GPUs in SLI configuration. Driver-level overclocking and fan control on the primary GPU is still mirrored to all secondary GPUs joined into SLI configuration, however this behavior can be disabled via NVAPIMultiGpuClockControl and NVAPIMultiGpuFanControl registry entries if completely independent control is needed.
  • Ability to overclock and control fan speed at driver level for display devices unattached to windows desktop (e.g. display adapters dedicated for PhysX acceleration).
  • Improved hardware monitoring module:
  • New sticky graphs mode was designed special for multi-GPU systems and it greatly improves monitoring window layout and readability on the systems with many active hardware monitoring graphs, which cannot be displayed simultaneously without window scrolling. Now you can easily stick any hardware monitoring graph to other graph(s) and view multiple overlapping graphs on the master graph. The groups of sticky graphs can be easily edited on-the-fly in both manual and automatic modes, dynamic master graph selection allows you to switch between multiple vertical scaling modes for any sticky graphs group. The following sticky graphs related GUI enhancements are available in this version:
  • Added "Stick to other graph" button to the system area of each hardware monitoring graph. You may click this button on any graph you're about to stick to other graph(s) then point desired target graph(s) to manually create groups of sticky graphs with just two mouse clicks.
  • Each graph (for both normal and clipped states) and grid color can be customized in the graph properties now. Custom colors are useful for visual color identification of graphs in a group.
  • Added master graph selection tabs to each group of sticky graphs. Master graph selection affects graphs Z-order and ensures that the master is rendered on top of all graphs in the group, as well as it affects group vertical scaling and grid color settings. Current and tracking marker values also apply to the master.
  • Added "Unstick graph from group" button to the system area of each group of sticky graphs. You may click this button to unstick master graph from the group. You may also hold when clicking this button to unstick all graphs from the group and hold + to unstick all graphs from all groups.
  • Added "Auto stick graphs" button to hardware monitoring window toolbar for both realtime monitoring and postreal monitoring history viewing modes. You may click this button to activate wizard allowing you to create the groups of sticky graphs automatically. The following automatic modes are available:
  • "Stick by graph units" - groups of sticky graphs are created by graph units similarity. In this mode wizard creates group of sticky graphs with all temperatures in °C units, group of sticky graphs with all clock frequencies in MHz units and so on.
  • "Stick by graph name on multi-GPU systems" - groups of sticky graphs are created by multi-GPU graph names similarity. In this mode wizard creates group of sticky graphs with core temperatures for all GPUs in the system, group of sticky graphs with core clocks for all GPUs in the system and so on.
  • Improved print friendly monitoring graphs screenshot capture:
  • Now besides previously available F11 keyboard shortcut print friendly screen capture can be also performed by pressing new "Capture print friendly screenshot" button on hardware monitoring window toolbar for both realtime monitoring and postreal monitoring history viewing modes.
  • Legend is now displayed on print friendly screenshots for the groups of sticky graphs.
  • Current tracking marker no longer displayed on print friendly screenshots.
  • Improved hardware monitoring plugin API. Now GPU index is passed to API SetupSource function allowing plugin developers to implement GPU specific hardware monitoring settings customization.
  • Updated bundled RivaTunerStatisticsServer v3.1.0 utility:
  • Minor skin appearance changes, "Normal" application detection level has been renamed to "Low" for better understanding.
  • Improved hooking system injects code into OS kernel's LoadLibrary functions by precached offsets and improves compatibility with some protective systems, faking the real LoadLibrary function offsets (e.g. latest revisions of SecuRom coming with new games like Dead Space, Need for speed : Undercover etc). Now such games no longer crash on startup when the server is running and LoadLibrary hooking is enabled by selecting "High" application detection level.
  • Added pre-created profiles for 3D applications, which require non-standard On-Screen Display coordinate space settings (e.g. Codename Panzers : Phase Two and Alpha Prime).
  • Added pre-created profiles for new pseudo-3D applications.
  • Updated bundled D3DOverrider v2.0.0 utility:
  • Fully redesigned user interface:
  • Now D3DOverrider follows by RivaTunerStatisticsServer and also supports user interface skins. User interface skinning usage approach allows RivaTuner fans community to change D3DOverrider's appearance completely and to express themselves in new skins design. Skin format is completely open, skin compiler and decompiler are integrated in D3DOverrider, so please visit techsupport forums to get more detailed information and help on the skin creation.
  • Simplified beginner oriented profile settings. Many previously available power user oriented options, such as per-3D API triple buffering and VSync forcing options, are now merged into unified options and more simple multi-buttons, e.g. "Application detection level" multi-button.
  • Improved help system. Now context sensitive help system is activated by hovering mouse over the control, instead of traditional right-click and "What's this?" based access in the previous versions.
  • Fully redesigned profiles architecture:
  • Now pre-created and user profiles are no longer stored into single file, so user profiles are no longer lost after D3DOverrider reinstallation. Please take a note, that the user profiles are preserved only when D3DOverrider is reinstalled in the same folder.
  • Now it is no longer possible to remove critically important pre-created profiles and pre-created profile settings can be easily restored due to template based profiles architecture.
  • Previously available debug features (sound indication and RivaTuner events logging) can be controlled via profile GUI now.
  • Greatly improved triple buffering forcing safety. Now D3DOverrider analyzes the application's 3D engine specifics and avoids forcing triple buffering for the applications, incompatible with triple buffering by design. Triple buffering is no longer forced under when the application is creating overlay swap chain or swap chain without hardware flipping support. This feature greatly reduces the need of adding new 3D applications to the exceptions list. Now most of such applications (e.g. different video players creating overlay swap chain or some games like Cryostasis, using D3DSWAPEFFECT_COPY swap chain) can start when D3DOverrider is running.
  • Changed sound indication ideology. Now attempt to force triple buffering in the application having native triple buffering implementation is indicated by success beep instead of failure beep in the previous version. Failure beeps are now reserved for indicating triple buffering forcing failures due to specifics of 3D engine incompatible with triple buffering by design (please refer to the previous item description).
  • Improved hooking system injects code into OS kernel's LoadLibrary functions by precached offsets and improves compatibility with some protective systems, faking the real LoadLibrary function offsets (e.g. latest revisions of SecuRom coming with new games like Dead Space, Need for speed : Undercover etc). Now such games no longer crash on startup when D3DOverrider is running and LoadLibrary hooking is enabled by selecting "Medium" or "High" application detection levels.
  • Added power user oriented profile settings allowing D3DOverrider to disable injection into Direct3D device reset functions and prevent possible application crashing due to concurrent reset function hooking by D3DOverrider and game's own OSD implementation (e.g. crashing when changing display settings in Team Fortress 2 and D3DOverrider is running). Pre-created profile for Half-Life 2 engine based games demonstrates new setting usage.
  • Updated exceptions list.
  • Extended Direct3D9 capability bits decoding in low-level diagnostic report module.
  • Improved command line interface. Added /SG and /SELECTGPU command line switches allowing selecting tweak target by GPU index rather than by logical display device index represended by previously available /SD and /SELECTDEVICE command line switches. New command line switches are supported for both queued hardware access scripts and for command line based GUI device selection changing.
  • Added experimental display configuration tracking mode. Power users may enable this mode using DisplayConfigurationTracking registry entry to force RivaTuner to track changes in your display adapters configuration (e.g. toggling SLI mode on/off or disabling secondary display adapter in the device manager). RivaTuner will reinitialize logical devices list and restart hardware monitoring module on display configuration change.
  • Minor GUI changes and improvements.

New in RivaTuner 2.22 (Dec 30, 2008)

  • Minor bugfixes:
  • Fixed bug in LM63.dll plugin, causing empty graphs with no data to be displayed in hardware monitoring module and introduced during porting the plugin to multi-GPU architecture in version 2.20.
  • Multifunction PCI devices are no longer scanned and no longer detected as multi-GPU devices.
  • Fixed pipeline count detection code for NVIDIA G98 GPU family.
  • What's new:
  • Added ForceWare 181.xx drivers family support.
  • Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 180.87, 180.88 and 181.00.
  • Updated bundled RivaTunerStatisticsServer v3.0.0 utility:
  • Fully redesigned user interface:
  • Now the server supports user interface skins to conform requirements of AIB/AIC partners bundling the server with their products. User interface skinning is based upon proprietary engine, which was previously used only in commercical RivaTuner technology based products. User interface skinning usage approach allows RivaTuner fans community to change the server's appearance completely and to express themselves in new skins design. Skin format is completely open, skin compiler and decompiler are integrated in the server, so please visit techsupport forums to get more detailed information and help on the skin creation.
  • Simplified beginner oriented profile settings. Many previously available power user oriented options, such as per-3D API hooking options, are now merged into more simple multi-buttons, e.g. "Application detection level" multi-button.
  • Improved help system. Now context sensitive help system is activated by hovering mouse over the control, instead of traditional right-click and "What's this?" based access in the previous versions.
  • On-Screen Display preview window greatly simplifies realtime On-Screen Display position, color and zoom adjustment.
  • Fully redesigned profiles architecture:
  • Now pre-created and user profiles are no longer stored into single file, so user profiles are no longer lost after the server reinstallation. Please take a note, that the user profiles are preserved only when the server is reinstalled in the same folder.
  • Now it is no longer possible to remove critically important pre-created profiles and pre-created profile settings can be easily restored due to template based profiles architecture.
  • Improved screen capture safety. The server no longer crashes on attempt to capture screenshot in DirectX9 applications without October 2006 or newer DirectX runtime libraries installed.
  • Improved product customization features:
  • In addition to skins and previously available product name customization feature, bundling partners can also customize product icon (including system tray icon) and define a link to own online product help page.
  • Product customization information is no longer stored in editable text OEM file, now this information is encoded to protect the product from illegal modification and distribution by third parties.
  • Improved installer and uninstaller:
  • Improved installation and uninstallation routines for statistics server's hook libraries.
  • Now the uninstaller also removes the files installed by 64-bit signed driver update.

New in RivaTuner 2.21 (Dec 12, 2008)

  • Minor bugfixes:
  • FOURCC INTZ and RAWZ formats are no longer forcibly disabled on GeForce 6 and newer display adapters when closing the 'Textures' tab in Direct3D tweaks dialog. Please take a note that these formats are required for proper GTA IV functionality, so if you experience problems with missing textures in this game on NVIDIA GeForce 6 and newer display adapters then please try to open the 'Textures' tab and press the 'Defaults' button.
  • Fixed 'Restore after suspended mode' option in low-level fan control tab, corrupted in the previous release due to multi-GPU related core changes.
  • What's new:
  • Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 180.60, 180.70 and 180.84.
  • Added Catalyst 8.12 driver family detection.
  • Added 'Enable FOURCC INTZ surfaces' and 'Enable FOURCC RAWZ surfaces' options to the 'Textures' tab of the Direct3D tweaks dialog.
  • 'Restore after suspended mode' option in low-level fan control tab is multi-GPU oriented now. Now the option affects all display adapters in the system instead of currently selected display adapter only.
  • 'Allow separate 2D/3D clock frequency adjustment' option is no longer provided when enabling driver-level hardware overclocking. The option is now hidden to reduce the amount of false bugreports posted by the beginners trying to disable 2D/3D clock frequncy then claiming that the hardware stays at extremely low boot clocks. Power users can still control this option via AllowMaxPerf registry entry.
  • Extended list of detectable supported FOURCC formats in 'IDirect3D9 HAL adapter formats' diagnostic report category.

New in RivaTuner 2.20 (Nov 20, 2008)

  • 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
  • Improved launcher module: 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
  • Improved low-level hardware overclocking module for ATI display adapters: 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) / 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.

New in RivaTuner 2.08 (Mar 10, 2008)

  • RivaTuner no longer crashes when RivaTuner module activation launcher item is scheduled to run at Windows startup.
  • Fixed association between low-level refresh overrider rules and target display adapter, broken due to low-level profiles association related changes in the previous version.
  • Minor UI and localization fixes.
  • Updated databases for Detonator and ForceWare drivers. Added database for ForceWare 169.44.
  • Added Catalyst 8.3 drivers detection.
  • Updated Catalyst 8.3 certified SoftR9x00 patch script (for Windows 2000/XP drivers only).
  • Updated PCI DeviceID database for ATI graphics processors. Added PCI DeviceID for RADEON HD 3850 AGP.
  • Improved G94 graphics processors support. Thanks to Jurgen in 't Zandt @ Point of View for providing NVIDIA GeForce 9600GT sample for testing. The list of G94 related improvements includes: Added low-level fan control support for integrated PWM controllers of G94 graphics processors. / Improved driver-level fan control support for integrated PWM controllers of G94 graphics processors. Now RivaTuner can be used for switching between driver-level automatic and driver-level direct fan control modes on GeForce 9600GT series.
  • Improved RV6xx graphics processors family support. With this version RivaTuner continues tradition of providing workarounds for bugs existing in fan controller calibration routines of many reference AMD HD 38x0 BIOS images. The list of new workarounds and enhancements includes: Extended list of tweakable automatic fan speed control rule parameters for RV6xx fan controllers. Now besides editing previously available thermal lookup and temperature transfer formula parameters RivaTuner also allows editing parameters of RV6xx fan controller's acoustic management system. Acoustic management related parameters include PWM hysteresis and PWM ramp settings, which are also improperly calibrated in certain AMD HD 38x0 BIOS images. / Now RivaTuner forcibly resets fan controller's PWM hysteresis settings when adjusting fan speed in fixed mode. This enhancement provides fine fan speed adjustment in fixed fan speed mode instead of stepwise fan speed adjustment mode on the systems affected by erroneously programmed PWM hysteresis. / Changed representation format for temperature transfer function's T slope parameter. Now the parameter is displayed and edited in percents instead of PWM ticks to simplify transfer formula readability.
  • Minor UI changes and improvements.

New in RivaTuner 2.07 (Mar 3, 2008)

  • 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 key after logging in Windows to skip RivaTuner's tasks scheduled to be started with Windows or you can hold 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.
  • 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.

New in RivaTuner 2.02 Final (Jul 3, 2007)

  • Fixed "Enable LoadLibrary hooking" option in bundled RivaTunerStatisticsServer application, which was corrupted due to internal hooking system changes introduced in the previous version.
  • Fixed typo in PCI DeviceID database for certain AGP G71 GPU based display adapters, causing them to be improperly detected and handled as G73 based.
  • Added workaround for internal MFC buffer overrun bug, causing Launcher tab to crash after adding launch item with a name containing more than 256 characters.
  • Minor UI and localization fixes.
  • Added ForceWare 160.xx and 162.xx driver families support.
  • Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 158.22, 158.27, 160.03, 160.04 and 162.15.
  • Added Catalyst 7.5 and 7.6 drivers detection. Please take a note that Catalyst 7.5 and 7.6 driver files have the same file binary file versions so both drivers will be detected as 'Catalyst 7.5 or newer' in RivaTuner.
  • Updated Catalyst 7.5 and 7.6 certified SoftR9x00 parch script (for Windows 2000/XP drivers only).
  • Added ATI R600 GPU support. Now all RivaTuner's low-level features including overclocking, color correction, fan control and hardware monitoring are available on ATI RADEON 2900 family. Thanks to Peter Yeung @ HIS for providing ATI RADEON 2900XT for testing.
  • Added experimental ATI RV610 and RV630 GPUs support. Thanks to Andrew Worobiew for testing RivaTuner on ATI RADEON 2400XT, ATI RADEON 2600PRO and ATI RADEON 2600XT. Please take a note that RV6xx support is currently in very early experimental stage and nothing but hardware monitoring and diagnostic report modules has been tested seriously with these display adapter families.
  • Updated RivaTunerStatisticsServer v2.3.0 bundled utility:
  • Added framerate monitoring and OSD rendering support for Direct3D9 applications using IDirect3DSwapChain9 interfaces for page flipping under Vista (e.g. Tomb Raider: Legend).
  • Improved hardware monitoring module:
  • Now RivaTuner pauses hardware monitoring module before entering suspended mode and resumes monitoring when the system resumes. This improves stability on certain hardware configurations, critical to polling in suspended mode. Power users may disable this feature using PauseInSuspendedMode registry entry.
  • Added description buffer overrun protection to all plugins with generic localization support.
  • Added built-in provider for core temperature monitoring via RV610 and RV630 on-die thermal diodes.
  • Added built-in provider for GPU usage monitoring on RV610 and RV630 graphics processors.
  • Improved hardware monitoring plugins:
  • Improved SMART.dll plugin. Now the plugin contains user customizable minimum hardware polling interval, which can be used to lower performance hit caused by slow S.M.A.R.T. hardware access implementations on certain combinations of ATA controllers and hard drive models. By default minimum hardware polling interval is set to 60 seconds, however power users may redefine minimum polling interval for this plugin by editing MinPollingInterval field in [Settings] section of SMART.cfg file.
  • Improved VT1103.dll plugin:
  • Added average current monitoring for VT1105 and VT1165 voltage regulators. Now the plugin is able to monitor average current for core voltage regulators used on ATI display adapters equipped with VT1105 and VT1165 (e.g. ATI RADEON 2900 family).
  • Added programmable output voltage monitoring for VT1105 and VT1165 voltage regulators. Now besides hardwired VID-based output voltages the plugin also able to monitor programmable output voltages on ATI display adapters equipped with VT1105 and VT1165 (e.g. ATI RADEON 2900 family). Please take a note that output voltage programming implementation depends on voltage regulator's circuit design and may differ depending on the PCB. Currently the plugin's database contains programmable VID to voltage mapping for reference design ATI RADEON 2900XT series only.
  • Added temperature monitoring for VT1105 and VT1165 voltage regulators. Now the plugin is able to monitor temperature of voltage regulators used on ATI display adapters equipped with VT1105 and VT1165 (e.g. ATI RADEON 2900 family). Please take a note that VT1165 is multiphase voltage regulator and actually have multiple temperature sensors installed in each slave chip. However to simplify understanding and visualization the plugin monitors just a single value read from the first slave chip.
  • Added open source Everest.dll plugin. The plugin is able to import any monitoring data sources from Everest software and display them in RivaTuner Statistics Server's On-Screen Display. By default the plugin is configured to import 'CPU temperature', 'CPU fan speed', 'System temperature', 'System fan speed', 'PSU fan speed', 'CPU voltage', 'PSU 3.3V voltage', 'PSU 5V voltage' and 'PSU 12V voltage' data sources, however you can customize the list of imported data sources by editing Everest.cfg file. Please take a note that 'Enable shared memory' option must be ticked in Everest in File Preferences Hardware monitoring External applications tab to allow RivaTuner to import data from it.
  • Improved diagnostic report module:
  • Added new Intel chipsets to northbridges hardware database.
  • Added PowerPlay table info to 'ATI VGA BIOS information' diagnostic report category. Now RivaTuner is able to decode PowerPlay states defining 2D/3D clocks and voltages in ATI RADEON 2400/2600/2900 display adapters family.
  • Added unified voltage table info to 'ATI VGA BIOS information' diagnostic report category. Now RivaTuner is able to decode new ATi voltage table format and display information about voltage controller I2C registers and VID encoding information for ATI RADEON 2900 display adapters family.
  • Improved low-level hardware overclocking module:
  • Added PowerPlay based driver-level wrapper for 3D clock frequency adjustment on ATI RADEON 2400/2600/2900 display adapters family. Unlike Overdrive overclocking interface it doesn't require 8-pin power cable to be connected to card for proper functionality. Please take a note that due to ATI Catalyst driver's PowerPlay programming issues it will reset current fan settings to defaults after applying new 3D clock frequencies. It is recommended to reconfigure fan controls after changing 3D clock frequency until this issue is addressed in ATI driver.
  • Updated ATI VGA BIOS scripts parser. Added support for new tokens used in ATI RADEON 2900 VGA BIOS images.
  • Now visual frequency clock testing is disabled on ATI cards if Overdrive or PowerPlay base driver-level wrapper is in use.
  • Improved GUI for both driver-level and low-level hardware overclocking modules. Now to avoid confusing beginners RivaTuner hides 'Test' button instead of disabling it when clock frequency testing is forcibly disabled or not available.
  • Added Q and QUIT command line switches, allowing to unload RivaTuner from memory immediately either with hotkey or with desktop shortcut.
  • Improved refresh overrider module. Now it is possible to override refresh rate during partial display mode change when the application doesn't specify display mode bit depth explicitly (e.g. in Quake III when bit depth option is set to 'Default').
  • Improved numpad keys support for low-level keyboard hook based hotkey emulator.
  • Rarely used ATIProble and NVInfo DOS tools are no longer supported and no longer bundled with RivaTuner.
  • Improved Easter Eggs:
  • Added new Easter Eggs.
  • Improved built-in hardware emualtor. Added protections against incorrect MMIO emulation.
  • Improved hidden ATI VGA BIOS decompiler:
  • Added support for ATI RADEON 2x00 VGA BIOS specific script tokens.
  • Now the decompiler analyzes code branching and doesn't stop decomipling a script when meeting the first RET token.
  • Minor UI changes and improvements.