RivaTuner FAQ

[Robert]

Riva Tuner 2.0 Final
http://downloads.guru3d.com/download.php?det=163

info,co je noveho
http://www.guru3d.com/index.php?page=rivatuner&menu=8

[Spajdr]

Jsem si toho všiml až teď, další verze pár měsíců nebude
http://forums.guru3d.com/showpost.ph...9&postcount=28

Aneb unwinder toho má a nejenom rivatuneru nejspíš plné koule

[Over]

RivaTuner 2.01
Download
http://nvworld.ru/downloads/rivatuner.zip

What`s New in this version...
http://www.guru3d.com/index.php?page=rivatuner

[MV]

RivaTuner 2.02
Download
http://downloads.guru3d.com/download.php?det=163

What`s New in this version...
http://www.guru3d.com/index.php?page=rivatuner

[Masster]

Rivatuner 2.03 released

Download

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:
o Added OSD rendering support for Direct3D10 applications.
o 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.
o 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.
o Updated list of pseudo 3D applications.
* Updated D3DOverrider v1.4 bundled utility:
o Internal hook infrastructure has been seriously changed to provide support for Vista and future operating systems.
o Added experimental triple buffering forcing support for Direct3D10 applications.
o 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:
o 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.
o 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:
o 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.
o 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.
o 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.

A co je jeste lepsi:

Important info for Vista x64 users:

Gentlemen!

Say really BIG thanks to owr 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://www.nvworld.ru/downloads/RivaTuner203Drv.rtu

There are two ways to install this update under Vista x64:

1) You may copy this file to the same folder where RivaTuner203 installer resides then simply reinstall RT. RivaTuner's update installation system will automatically detect update file in this folder and offer you to install it. 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.

[Masster]

Rivatuner v2.04 released

Download

Version 2.04, wat'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:
• 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.
• 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:
• 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.
• 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.
• 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:
• 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.

[Masster]

Rivatuner v2.05 released

Download

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:
• 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.
• 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.
• 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.
• Power user oriented adjustable minimum and maximum clock slider limits have been expanded from 25%-300% to 10%-800%.
• 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.