RivaTuner FAQ

[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.

[-Ja8k1-]

mam problem s novym riva tunerem v2.05 , rivery 163.67 (vista) a grafickou 8400M GS pokazde co se pokusim zmenit frekvence, tak se mi to vrati na puvodnich 400\800\400. pricemz uprevovat low power 3D i 2D lze. pri nastavovani performance 3d to po opusteni nabidky skoci zpet na puvodni.. vi nekdo co s tim?
diky

[Masster]

RivaTuner v2.06 Beta

Download

What's new:

• Added ForceWare 167.xx drivers family support including ForceWare 167.xx compatible overclocking. Please take a note that 2D/3D clock switching for some GPU families is completely broken in early 167.26 drivers. Until the problem is fixed in the driver RivaTuner bypasses this issue by mapping 2D, LowPower 3D and 3D performance level clocks to the same single clocking level provided by these drivers.
• Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 163.74, 163.75, 163.76 and 167.26.
• Added Catalyst 7.10 drivers detection.
• Updated Catalyst 7.10 certified SoftR9x00 patch script (for Windows 2000/XP drivers only).
• Added ATI RV670 graphics processors family support. Now RivaTuner's low-level features including overclocking, monitoring, diagnostics and fan control are available on ATI RADEON HD 38x0 family. Thanks to Anthony Tam @ HIS for providing ATI RADEON HD 3850 sample for testing.
• Added experimental support for the rest upcoming 55nm ATI RV6xx graphics processors families.
• Improved RV610/RV630 graphics processors families support. The improvements cover wide range of hardware overclocking, diagnostics, fan control and monitoring features.
• Added NVIDIA G92 graphics processors family support. Now RivaTuner's driver-level tuning and low-level features including overclocking, monitoring, diagnostics and fan control are available on NVIDIA 8800GT and other upcoming G92 based NVIDIA products.
• Improved driver-level fan control tab for NVIDIA display adapters:
• Added driver-level fan control tab for NVIDIA Vista drivers. Now RivaTuner is able to control fan on midrange NVIDIA display adapters with integrated fan controller under Vista via the ForceWare's NVAPI interfaces. Please take a note that unlike Windows XP fan control interfaces Vista's NVAPI fan control interfaces do not support independent 2D/3D fan speed adjustment and allow you to use either automatic or direct fixed fan control only. By default NVAPI fan control interfaces are used under Vista only, however Windows XP owners can also force RivaTuner to use Vista specific fan control interfaces if needed. The forcing can be useful to get fan control working on some graphics processors families, having broken separate 2D/3D fan control implementation in Windows XP driver (e.g. GeForce 8600 family).
• Driver-level fan control tab is now hidden on display adapters supporting binary fan control only (i.e. able either to run fan at full speed or shut it down completely) to avoid confusing beginners. Power users may unlock binary fan control if necessary by setting AllowBinaryFanSpeedControl registry entry to 1.
• Improved low-level overclocking tab for ATI R6xx/RV6xx display adapters:
• Now RivaTuner supports overclocking on ATI RV6xx display adapters using DPM (Dynamic Power Management) clock frequency adjustment.
• Now RivaTuner restores default clocks on ATI R6xx/RV6xx by means of the driver's PowerPlay table reset if possible.
• Improved low-level fan control tab:
• Improved duty cycle generation accuracy for display adapters using LM63, LM64, F75363 and ADT7473 external I2C fan controllers.
• Added low-level fan control support for ATI RV6xx integrated fan controllers.
• Added low-level fan control support for NVIDIA NV3x and newer integrated fan controllers. Please take a note that low-level fan control tab for display adapters using integrated fan controller (e.g. GeForce 6600, 7800GT, 7900GT etc) 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.
• Improved hardware monitoring module:
• Added ATI RV6xx DPM (Dynamic Power Management) technology support. Now RivaTuner is able to monitor dynamically changing RV6xx clock core and memory clock frequencies adjusted in real-time by DPM depending on the GPU usage.
• Added 'Reference fan duty cycle' graph for ATI RV6xx graphics processors families.
• Added 'Reference fan duty cycle' graph for NVIDIA G80 and newer graphics processors families. Please take a note that some non-reference G84 based display adapters use inverted PWM polarity fan control, which means that 'Reference fan duty cycle' displays inverted duty cycle as well as low-level fan control slider is inverted too. Such issues can be resolved by adding such display adapters to internal fan controller database represented by [FANPWM] section of RivaTuner.cfg file. The polarity can be inverted by adding the entry identifying such display adapter to the database and specifying inverted fan PWM controller ID (84h) for it instead of normal one (04h).
• Heavily optimized low-level I2C bus access algorithms for NVIDIA G80 and newer graphics processors families. Now the bus is accessed via new dedicated I2C registers instead of traditional I2C CRTC ports. Dedicated I2C access drastically reduces CPU time consumed by each I2C transaction (up to 5x - 7x times faster on certain hardware configurations). The effect of the optimization is the most visible in conjunction with MMIO mode when any device connected to I2C bus (e.g. ADT7473 thermal / fan controller) is being frequently polled. Power users may activate the previously available I2C access mode for performance comparison by setting NVI2CAccessModeG8x registry entry to 0.
• Now hardware monitoring graph renderer flushes bitmap caches after each display mode change to help display driver to render the graphs in optimal way. By default flushing is performed within a period of time defined by PostDisplayChangeBitmapFlushPeriod registry entry, the period can be changed by redefining it or the flushing can be disabled completely by setting the period to 0.
• Improved diagnostic report module:
• Improved navigation via the list of diagnostic report categories. Now report preview window is positioned on desired category more accurately when double clicking it in the list of diagnostic report categories.
• Improved PowerPlay table flags decoding in 'ATI VGA BIOS information' diagnostic report category.
• Added MMIO protection fallback support. Now RivaTuner automatically disables MMIO protection, notifies the user and starts in unprotected mode if the protective system is unable to allocate required protected MMIO range aperture (e.g. due to fragmented or limited kernel address space).
• Added #opt tag support to driver files database parser to allow including optional driver files in the database. This token was exclusively added to provide detection of ATI's ramdomly named OpenGL ICD drivers.
• Now RivaTuner uses %RTFolder% macro name when saving a path to external resources (e.g. databases or hardware monitoring log files) stored in the application folder. Power users can disable this feature by setting AllowRelativePathsEncoding registry entry to 0.
• Minor UI changes and improvements.

[Spajdr]

tohle bych tady nezmiňoval, je to leaknutá verze a unwinder byl kvůli tomu nasraný + betatester co to leaknul už dotestoval.

[Masster]

Sakra, to abych to dal rychle pryc

[Over]

RivaTuner v2.06 final

http://downloads.guru3d.com/download.php?det=163
http://rapidshare.com/files/66723933/RivaTuner2.06.exe

Minor bugfixes:

* Fixed DDR2 videomemory detection for G84/G86 graphics processors.
* Minor UI and localization fixes.

What's new:

* Added ForceWare 167.xx and 169.xx drivers families support. Please take a note that 2D/3D performance levels switching is broken in currently broken in these drivers, so adjusting 2D performance level settings (e.g. 2D clocks) via RivaTuner will also change 3D performance level settings and vice versa.
* Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 163.74, 163.75, 163.76, 167.26, 169.01, 169.02 and 169.04.
* Added Catalyst 7.10 drivers detection.
* Updated Catalyst 7.10 certified SoftR9x00 patch script (for Windows 2000/XP drivers only).
* Added ATI RV670 graphics processors family support. Now RivaTuner's low-level features including overclocking, monitoring, diagnostics and fan control are available on ATI RADEON HD 38x0 family. Thanks to Anthony Tam @ HIS for providing ATI RADEON HD 3850 sample for testing.
* Added experimental support for the rest upcoming 55nm ATI RV6xx graphics processors families.
* Improved RV610/RV630 graphics processors families support. The improvements cover wide range of hardware overclocking, diagnostics, fan control and monitoring features.
* Added NVIDIA G92 graphics processors family support. Now RivaTuner's driver-level tuning and low-level features including overclocking, monitoring, diagnostics and fan control are available on NVIDIA 8800GT and other upcoming G92 based NVIDIA products.
* Improved driver-level fan control tab for NVIDIA display adapters:
o Added driver-level fan control tab for NVIDIA Vista drivers. Now RivaTuner is able to control fan on midrange NVIDIA display adapters with integrated fan controller under Vista via the ForceWare's NVAPI interfaces. Please take a note that unlike Windows XP fan control interfaces Vista's NVAPI fan control interfaces do not support independent 2D/3D fan speed adjustment and allow you to use either automatic or direct fixed fan control only. By default NVAPI fan control interfaces are used under Vista or under 167.xx and newer drivers only, however Windows XP owners can also force RivaTuner to use Vista specific fan control interfaces with older driver versions if needed by setting NVAPIUsageBehaviour registry entry to 1. The forcing can be useful to get fan control working on some graphics processors families, having malfunctioning separate 2D/3D fan control implementation in Windows XP driver (e.g. GeForce 8600 family).
o Driver-level fan control tab is now hidden on display adapters supporting binary fan control only (i.e. able either to run fan at full speed or shut it down completely) to avoid confusing beginners. Power users may unlock binary fan control if necessary by setting AllowBinaryFanSpeedControl registry entry to 1.
* Improved low-level overclocking tab for ATI R6xx/RV6xx display adapters:
o Now RivaTuner supports overclocking on ATI RV6xx display adapters using DPM (Dynamic Power Management) clock frequency adjustment.
o Now RivaTuner restores default clocks on ATI R6xx/RV6xx by means of the driver's PowerPlay table reset if possible.
* Improved low-level fan control tab:
o Improved duty cycle generation accuracy for display adapters using LM63, LM64, F75363 and ADT7473 external I2C fan controllers.
o Added low-level fan control support for ATI RV6xx integrated fan controllers.
o Added low-level fan control support for NVIDIA NV3x and newer integrated fan controllers. Please take a note that low-level fan control tab for display adapters using integrated fan controller (e.g. GeForce 6600, 7800GT, 7900GT etc) 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.
* Improved hardware monitoring module:
o Added ATI RV6xx DPM (Dynamic Power Management) technology support. Now RivaTuner is able to monitor dynamically changing RV6xx clock core and memory clock frequencies adjusted in real-time by DPM depending on the GPU usage.
o Added 'Reference fan duty cycle' graph for ATI RV6xx graphics processors families.
o Added 'Reference fan duty cycle' graph for NVIDIA G80 and newer graphics processors families. Please take a note that some G84 based display adapters use inverted PWM polarity fan control, which means that 'Reference fan duty cycle' displays inverted duty cycle on such display adapters as well as low-level fan control slider is inverted too. Inverted polarity issues can be resolved by adding such display adapters to internal fan controller database represented by [FANPWM] section of RivaTuner.cfg file. PWM polarity for such display adapters can be forcibly inverted by adding the entry identifying such display adapter to the database and specifying PWM controller ID with forced negative PWM polarity for it (84h).
o Heavily optimized low-level I2C bus access algorithms for NVIDIA G80 and newer graphics processors families. Now the bus is accessed via new dedicated I2C registers instead of traditional I2C CRTC ports. Dedicated I2C access drastically reduces CPU time consumed by each I2C transaction (up to 5x - 7x times faster on certain hardware configurations). The effect of the optimization is the most visible in conjunction with MMIO mode when any device connected to I2C bus (e.g. ADT7473 thermal / fan controller) is being frequently polled. Power users may activate the previously available I2C access mode for performance comparison by setting NVI2CAccessModeG8x registry entry to 0.
o Now hardware monitoring graph renderer flushes bitmap caches after each display mode change to help display driver to render the graphs in optimal way. By default flushing is performed within a period of time defined by PostDisplayChangeBitmapFlushPeriod registry entry, the period can be changed by redefining it or the flushing can be disabled completely by setting the period to 0.
* Improved diagnostic report module:
o Improved navigation via the list of diagnostic report categories. Now report preview window is positioned on desired category more accurately when double clicking it in the list of diagnostic report categories.
o Improved PowerPlay table flags decoding in 'ATI VGA BIOS information' diagnostic report category.
* Now RivaTuner also uses Vista specific NVAPI interfaces for driver-level thermal monitoring, overclocking and fan control under Windows XP for the ForceWare 167.xx and newer drivers. NVAPI usage can be either completely restricted by setting NVAPIUsageBehaviour registry entry to 0 or alternately NVAPI usage can be partially restricted just for some driver-level tasks with NVAPIThermalControl, NVAPIClockControl and NVAPIFanControl registry entries.
* Added MMIO protection fallback support. Now RivaTuner automatically disables MMIO protection, notifies the user and starts in unprotected mode if the protective system is unable to allocate required protected MMIO range aperture (e.g. due to fragmented or limited kernel address space).
* Added #opt tag support to driver files database parser to allow including optional driver files in the database. This token was exclusively added to provide detection of ATI's ramdomly named OpenGL ICD drivers.
* Now RivaTuner uses %RTFolder% macro name when saving a path to external resources (e.g. databases or hardware monitoring log files) stored in the application folder. Power users can disable this feature by setting AllowRelativePathsEncoding registry entry to 0.
* Minor UI changes and improvements.

[Perplex]

Jedna otazka pro znalce RT. Funguje Vam locknuti refreshe na vybrane frekvence? Me se nedari aby se moje ulozene nastaveni projevilo v realu. Predem diky.

[meteor]

Přidám se také s jednou otázkou: RT mám nainstalovaný tak týden a teďko při zapnutí počítače mi to hodilo hlášku:

"MMIO protection system failed to allocate protected MMIO range.
MMIO protection has been forcibly disabled.

It is strongly not reccomended to start any applications equipped with PunkBlaster system while running in unprotected mode!"

Při hledání jsem našel, že možnost deaktivace MMIO protection je zahrnuta v RT.
Zajímá mě teda, kde si MMIO protection můžu opět aktivovat a taky co se může stát, když bude při hraní po síti deaktivovaná (počítám že člověk nachytá sajrajt do kompu).

[Doktor-Prase]

daji se nejak na GF8800GTS (G80) regulovat vetraky (abych snizil otacky v idle, ale zachoval jejich rust pri zvysujici se teplote?)

[mortician]

Ked nechas vetrak nastaveny na auto control nerobi to automaticky? Mne to funguje dobre... Pekne pocut ako sa rozhulaka so stupajucou teplotou, ked pustim nieco narocnejsie na grafiku...

[Doktor-Prase]

ano, tak to samozrejme funguje, ale ja chci snizit otacky v idle (+ zvysit teplotu, pri ktery se zacnou zvysovat otacky)

[Over]

ano, tak to samozrejme funguje, ale ja chci snizit otacky v idle (+ zvysit teplotu, pri ktery se zacnou zvysovat otacky)

...že by první post?

[Doktor-Prase]

...že by první post?

Mae culpa...

[Doktor-Prase]

Tak jsem se na to trošičku víc podíval, na moji 8800GTS G80 to switchování profilů pomocí launcheru nejde.
Nicméně pomocí editace parametrů pro automatickej režim to jde

[Masster]

RivaTuner 2.07

Download

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 <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.
  • 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.

[homberg]

Nefunkcni se Sapphire AGP HD3850...

[homberg]

Nova Riva nepodporuje Ati AGP. Je ale mozne si rucne upravit .cfg, aby to chodilo.


It is not supported by 2.07, but you can add it yourself by adding your card PCI DeviceID (as far as I remember 9515h) to RV670 line of RivaTuner.cfg.

zdroj guru3d.com

P.S. brzy prijde RivaTuner 2.08, kde uz ma byt podpora Radeonu HD3850

[Spajdr]

RivaTuner v2.08
http://downloads.guru3d.com/RivaTune...nload-163.html

Minor bugfixes:

- 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.

What's new:

- 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.

[homberg]

Tak o/c na HD3850 AGP uz sice funguje, ale nerozlisuje 2D/3D, takze me to hned v 2D vali na plnej vykon, coz zrovna nepotrebuju

[Martin]

Ahoj, stavim PC, kde je 8800GT od Saphiru (GigaByte GeForce 8800GT GV-NX88T512HP 512MB, PCI-E), na ktery je snad Zalman chladic. Pokousel jsem se regulovat otacky vetraku pomoci ntune, ale nejde to. Zkusil jsem Rivatuner podle zde uvedenoho navodu, ale kdyz mam upravit plugin CORE TEMP, nezobrazi se mi polozka Treshold settings. Jinama metodama na bazi pokus-omyl jsem taky nedonutil vetrak tocit se pomalejs. Jde to u tyhle karty? Zbytek PC je dost tichej a byla by skoda to zabit timhle kravalem. Majitel PC nechce investovat do napr. Accelero S1 + nejakej vetrak.
Dik za odpovedi.

[erik_1]

Viem ze tu uz boli pastnute viacere linky na navod k RT ,ale skuskte este
tento...snad niekomu pomoze...ja ho pouzivam a je fajn.

http://www.vaguesoft.com/index.php?pageid=rt207

[meteor]

Viem ze tu uz boli pastnute viacere linky na navod k RT ,ale skuskte este
tento...snad niekomu pomoze...ja ho pouzivam a je fajn.

Uff, celkem dlouhý návod. Já to říkám pořád, zlatý ATi Tray Tools klik klik a je to. Nechápu, že je problém to udělat i v RT (stupnice teplot a k nim se přiřazují procentuální otáčky ventilátoru na GPU). Nebo to prostě nejde udělat z principu?

[Martin]

Viem ze tu uz boli pastnute viacere linky na navod k RT ,ale skuskte este
tento...snad niekomu pomoze...ja ho pouzivam a je fajn.

http://www.vaguesoft.com/index.php?pageid=rt207

Nepomohlo, fakt uz nevim, co s tim. Na CZC foru k tomuhe vyrobku psali, ze vetrak nejde regulovat softwarove. Fakt divny. Nikdo nema zkusenosti?

[Masster]

RivaTuner 2.09

Download

Minor bugfixes:

• The server no longer erroneously swaps RGB components and no longer causes On-Screen Display to be rendered in unexpected color under Direct3D10 when non-default OSD color is being used.

What's new:

• Added ForceWare 175.xx drivers family support.
• Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 174.40, 174.51, 174.53, 174.60, 174.70, 174.74, 174.82, 174.85, 174.88, 174.93 and 175.12.
• Added Catalyst 8.4 drivers detection. Please take a note that ATI continues "old good" tradition of using the same build version of different driver versions, so both Catalyst 8.3 and 8.4 will be detected as Catalyst 8.3 or newer.
• Updated Catalyst 8.4 certified SoftR9x00 patch script (for Windows 2000/XP drivers only).
• Updated PCI DeviceID database for AMD graphics processors. Added PCI DeviceIDs for RADEON X1650 AGP and RADEON 3850 X2.
• Update driver files database for 64-bit NVIDIA ForceWare drivers.
• Unlocked previously available experimental AMD RV620 graphics processors family support.
• Added experimental NVIDIA G96 graphics processors family support.
• Added experimental NVIDIA G100 (aka GT200) graphics processors family support.
• Added experimental driver-level multi-GPU fan control support for Quad-SLI systems. Thanks to Jacob Freeman @ EVGA for testing driver-level fan control with2x NVIDIA 9800GX2 system.
• Now RivaTuner is able to detect driver version and display driver files info for drivers using multiple driver files and active non-primary driver file.
• Added experimental clock frequency stress-testing for NVAPI overclocking interfaces. Please take a note that NVAPI's own stress testing is not ideal yet and it is not available for some GPU families (e.g. G80) or may work improperly for others. Due to this reason NVAPI clock frequency stress-testing feature is disabled by default, however power users may enable it using NVAPIClockTest registry entry.
• Added set of technologies aimed to improve RivaTuner startup and usage safety in conjunction with other hardware monitoring and diagnostics related tools:
  
  • Added low-level PCI controller access synchronization protocol. The protocol serves for preventing possible PCI controller access collisions when multiple tools are being started and scanning PCI buses simultaneously (e.g. detecting supported hardware during OS startup). Please take a note that to take full effect the protocol must be supported by other tools used simultaneously with RivaTuner, so please ensure that you're using this version of RivaTuner with the latest versions of other monitoring or diagnostics related software products (e.g. Everest).
  • Previously used low-level I2C synchronization protocol is now also applied to driver-level thermal monitoring function calls to prevent possible conflicts between low-level I2C transactions and internal driver-level I2C transactions.Please take a note that to take full effect the protocol must be supported by other tools used simultaneously with RivaTuner, so please ensure that you're using this version of RivaTuner with the latest versions of other monitoring or diagnostics related software products (e.g. Everest).
  • Added hardware scanning synchronization protocol, aimed to optimize startup process and reduce startup time when multiple tools are intensively scanning hardware.
  • Now startup daemon routine displays warning message in case of driver load failure (e.g. when the driver is blocked by antivirus tool).
  • Startup daemon self-deinstallation technology is disabled by default now. The daemon no longer uninstalls itself from Windows startup when it fails to apply any startup settings (e.g. due to driver load blocked by antivirus tool). If needed, the technology can be re-enabled by setting DontUninstallStartupDaemon registry entry to 0.
• Updated bundled RivaTunerStatisticsServer v2.6.0 utility:
  
  • Now OSD rendering routines are compatible with WPF based applications.
  • Now the server's manifest file specifies full administrative privileges requirement. If you're using Windows Vista with UAC enabled, it is recommended to create scheduled task launching the server simultaneously with RivaTuner to minimize amount of displayed UAC evaluation dialogs.
  • Changed sever's own OSD rendering behavior, now the server doesn't display 3D API usage information in the OSD when framerate display is not requested by a client application.
  • Updated pseudo-3D applications list.
• Updated bundled D3DOverrider v1.6.0 utility:
  
  • Now the D3DOverrider's manifest file specifies full administrative privileges requirement. If you're using Windows Vista with UAC enabled, it is recommended to create scheduled task launching the utility simultaneously with RivaTuner to minimize amount of displayed UAC evaluation dialogs.
• Improved launcher module:
  
  • Added 'Show item in tray menu' option to regular launch item editor. By disabling this option you may prevent some regular launch items from being displayed in RivaTuner's tray menu. This option is helpful if you're intensively use scheduled tasks and define many helper launch items, required only for scheduled tasks.
  • Now you may select 'All files' as file type when browsing for application associated with a launch item and this way start and non-executable file type (e.g. WAV or MIDI) registered in the OS. Please take a note that 'Restore settings after terminating application' option will not affect non-executable file types.
  • Now RivaTuner stores application specific event markers in the event history panel of hardware monitoring window, allowing you to analyze all item launch events and reasons (e.g. item launch due to pressed hotkey, due to scheduled task etc). This feature simplifies debugging complex dynamic hardware control algorithms programmed via scheduler module etc.
• Improved scheduler module:
  
  • Now you may specify custom scheduled tasks names in the task editor window to improve scheduled tasks list readability.
  • Added 'Wait for application termination' option for 'Launch application' tasks, allowing you to program sequentional tasks execution if needed.
  • Now you may select 'All files' as file type when browsing for application associated with 'Launch application' task and this way start and non-executable file type (e.g. WAV or MIDI) registered in the OS. Please take a note that 'Wait for application termination' option will not affect non-executable file types.
  • Now RivaTuner stores application specific event markers in the event history panel of hardware monitoring window, allowing you to analyze all shceduled tasks events and reasons (e.g. scheduled task launch due to core temperature change from 50°C to 51°C). This feature simplifies debugging complex dynamic hardware control algorithms programmed via scheduler module etc.
• Improved hardware monitoring module:
  
  • Now you may use 'Override group name' option in each data source's properties to define custom on-screen display group for it and override default OSD grouping rule if needed,
  • Now RivaTuner is able to detect PLL shutdown and swicth to bus clock on G8x and newer GPU families to provide dynamic memory clock frequency monitoring on upcoming G96 graphics processors family.
  • Now RivaTuner uses BIOS PLL information tables on G9x and newer GPU families to detect reference clock frequencies for core and memory PLLs if unknown GPU is detected. If needed, reference clocks can be redefined via [CrystalClock] section of RivaTuner.cfg file.
  • Improved SMART.dll hardware monitoring plugin. Now the plugin supports SMART temperature reading for up to 8 hard drives instead of 4 hard drives in the previous version.
• Improved low-level diagnostic report module:
  
  • Now RivaTuner displays PLL table contents containing per-PLL reference clock frequencies for G8x and newer display adapter families in 'NVIDIA VGA BIOS information' diagnostic report category.
• Unlocked undocumented SSAA and combined MSAA / SSAA antialiasing modes for G8x and newer display adapters.
• Now you may change external I2C fan controller detection retry counter using ExternalFanControllerDetectRetry registry entry or completely disable external I2C fan controller detection by setting this registry to 0.
• Minor UI changes and improvements.