Dear forum visitors! RivaTuner v2.03 is now available for download: http://downloads.guru3d.com/download.php?det=163 Final changes list includes: 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. Important info for Vista x64 users: Gentlemen! Say really BIG thanks to our old good friends from www.techpowerup.com. They were extremely kind to sign RivaTuner drivers with their signature allowing RivaTuner to run under Vista x64 OS with no limitations. Signed drivers are provided as separately downloadable RivaTuner203Drv.rtu update file: http://files2.guru3d.com/rivatuner/RivaTuner203Drv.rtu There are two ways to install this update under Vista x64: 1) You may copy this file to the same folder where RivaTuner installer (RivaTuner203.exe) resides then simply reinstall RT. RivaTuner's update installation system will automatically detect update file in this folder and offer you to install it. Please take a note that Guru3D distributes RivaTuner as self-extracting 7-zip archive. This file is not the installer and the update must be copied to the folder containing RivaTuner203.exe installer extracted from the archive. This is recomended way for beginners. 2) If you're power user and if you don't want to reinstall RivaTuner then you may update the driver on the fly. To do it either boot Vista with F8 to temperarily disable driver signing, start RivaTuner once to register it as update file handler then simply open the file with Windows explorer. Alternately, you may avoid booting Vista with F8 and try to open update file with Windows explorer then tell Windows that it must be processed with installed RivaTuner 2.03 executable file. After doing that the update will be installed by RivaTuner too. Note: We’ve just re-uploaded RivaTuner’s archive on the server. Now the archive contains previously available RivaTuner203.exe distributive together with RivaTuner203Drv.rtu update. Now you don't need to perform any file copying procedure, RivaTuner's installer will automatically offer you to install the update with signed drivers in the end of installation process. Please take a note that currently update installation system is able to install the updates properly only if path to the installer doesn't contain spaces. So it is recommended to extract downloaded archive to C:\Temp folder and install it from this location.