RivaTuner FAQ

***Toto téma bylo založeno z důvodu častých otázek okolo nastavení RivaTuneru a problémů s ním. Takže aby se nám to zbytečně netříštilo v celé sekci nvidia, směřujte další dotazy nejlépe sem, bude to přehlednější jak pro ty co přispívají, tak i pro ty co hledají odpovědi***THX
------------------------------------------------------------------------------------------------------

FAQ pro začátečníky s RivaTunerem (EN)
Taktovaní jádra a pamětí
Nastavení otáček chladiče grafické karty
http://www.electraforge.com/brooke/m...iva_tuner.html
http://www.vaguetech.com/index.php?pageid=rt207#fan
Přetaktovaní shaderů na 8800
další... http://www.guru3d.com/article/rivatu...erclock-guide/

OK, takze sem nieco pridam, co uz som tu pisal uz skorej:

Ako doplnit podporu GeForce 6800GS AGP do RT2.0RC 15.8

Ako doplnit podporu GeForce 7800GS AGP do RT2.0RC 15.8

RivaTuner 2.0 RC 16 , který podporuje i NV 7900

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

Jelikoz mam neblahou zkusenost s prehranim grafiky. Chtel jsem nastavit v RivaTuneru Threshold setting na urcitou hodnotu. Presne podle tohoto clanku: http://www.svethardware.cz/art_doc-9...60069FDF2.html
To znamena zadal jsem prikaz "C:\Windows\System32\Shutdown.exe -s -t 0 -f" A nastavil teplotu pri ktere se ma vykonat+ dobu v ms po kterou ma teplota setrvat nez se provede prikaz. Nastavil jsem pro test teplotu nizsi nez je teplota jadra abych jsem mohl vyzkouset funkcnost, Ale nic se jaksi nedeje. Nevite co muze byt spatne. Diky za odpovedi.

me pro zmenu nefunguje ve verzi 20 RC16, snizeni otracek vetraku na GPU.
delal jsem to step by step, presne podle manualu. frekvence jsou v poradku jak si nastavim, dokonce nastavim i ty otacky na 50%/50%/100%. ulozim, RT si to pamatuje ale pece na to. karta jede porad 100% otackama :o(

Mam pocit ze by to mohlo byt tim, ze moje karta 6800GS AGP Neni plne verzi 15.8 podporovana, i kdyz teplotu meri dobre? Proto se chci zeptat jak optimalne updatovat RivaTuner preinstalace a nebo odinstalace a nesledna instalace nove verze? Diky

Citace:

---

Původně odeslal Guide-Bot

me pro zmenu nefunguje ve verzi 20 RC16, snizeni otracek vetraku na GPU.
delal jsem to step by step, presne podle manualu. frekvence jsou v poradku jak si nastavim, dokonce nastavim i ty otacky na 50%/50%/100%. ulozim, RT si to pamatuje ale pece na to. karta jede porad 100% otackama :o(

---

Podle me to musi karta zaroven umoznovat SpeedFanem taky nejdou regulovat vsechny desky a k nim pripojeny vetracky.

Potřeboal bych nějaké základy s overclockingem v Riva turner česky a čeho se mám držet,zatim mam starou graf.kartu GF FX5200 128 MB tak bych se to na ní rád naučil než tam šoupnu novou,děkuji za odpovědi....Matrixx

http://www.oclab.cz/index.php?option...d=42&Itemid=51

http://www.svethardware.cz/art_doc-5...60069791C.html

Citace:

---

Původně odeslal Martin Šrámek

Podle me to musi karta zaroven umoznovat SpeedFanem taky nejdou regulovat vsechny desky a k nim pripojeny vetracky.

---

pockat jak k desce ??? me jde o to regulovat vetracek na karte.

Citace:

---

Původně odeslal Guide-Bot

pockat jak k desce ??? me jde o to regulovat vetracek na karte.

---

Chci tim jenom rict ze nektery grafarny nejdou regulovat RivaTunerem, stejne jako vetracky na boardu SpeedFanem (je na regulaci vetracku na deskach stejne jako RivaTunerna grafikach).Protoze bud nemaj hw. obvody pro regulaci a nebo je ten program nepodporuje. Coz i Tvuj pripad mas totiz Leadtek 7600 a u ty jsem to cetl v recenzi. Jde to jenom nejakou utilitou co je ke kartam Leadtek a je to nekde hluboku v nastaveni ale jde to. :-)

Citace:

---

Původně odeslal Guide-Bot

pockat jak k desce ??? me jde o to regulovat vetracek na karte.

---

zkus EXPERTool http://www.stahuj.cz/utility_a_ostat...sty/expertool/


zde návod na tweak EXPERTool pro zvětšení rozsahu nastavení otáček ventilátoru od 0%-100% (def. 50%-100%)
http://hem.passagen.se/fholmen/

Citace:

---

Původně odeslal Martin Šrámek

Chci tim jenom rict ze nektery grafarny nejdou regulovat RivaTunerem, stejne jako vetracky na boardu SpeedFanem (je na regulaci vetracku na deskach stejne jako RivaTunerna grafikach).Protoze bud nemaj hw. obvody pro regulaci a nebo je ten program nepodporuje. Coz i Tvuj pripad mas totiz Leadtek 7600 a u ty jsem to cetl v recenzi. Jde to jenom nejakou utilitou co je ke kartam Leadtek a je to nekde hluboku v nastaveni ale jde to. :-)

---

no je to takovej kruh, porad dokola. jde to udajne jen winfoxem, jenze na CD je neaktualni verze, ta se da stahnout pres live update, jenze ja na tom kompu nemam net :o)

gr gr gr

Citace:

---

Původně odeslal Guide-Bot

no je to takovej kruh, porad dokola. jde to udajne jen winfoxem, jenze na CD je neaktualni verze, ta se da stahnout pres live update, jenze ja na tom kompu nemam net :o)

gr gr gr

---

Pokud vis presne, jake otacky ventilatoru chces pro jednotlive rezimy nastavit, tak je natvrdo nastav v biosu karty, ne?

Tady mas navod na NiBiTor: http://www.oclab.cz/index.php?option...d=36&Itemid=51

Pokud si na to netroufas, tak mi ten bios posli a ja ho upravim, ale myslim, ze konkretne zmena otacek ventilatoru je velmi jednoducha uprava... ;)

Je lepsi preinstalovat a nebo odinstalovat a nainstalovat novou verzi?

Citace:

---

Původně odeslal Guide-Bot

me pro zmenu nefunguje ve verzi 20 RC16, snizeni otracek vetraku na GPU.
delal jsem to step by step, presne podle manualu. frekvence jsou v poradku jak si nastavim, dokonce nastavim i ty otacky na 50%/50%/100%. ulozim, RT si to pamatuje ale pece na to. karta jede porad 100% otackama :o(

---

No tak ja som RT rozbehal na mojej karte LEADTEK..myslim ze taku presne mas aj ty...no ale ako docielim to aby sa mi ukazovalo medzi grafmi aj otacky ventilatora...pocujem ze klesaju a narastaju ale v tray vidim len teplotu jadra....a nikde neviem nastavit aby tam boli aj otacky ventilatora...
Ak niekto vie pomoct tak vopred dakujem

Mam problem s nastavenim frekvence pameti pro 2D/Perform3D. Jakmile se prepnu do 3D, zafunguje to dobre, zvedne se frekvence jadra i pameti, ale po navratu do windows se snizi jen frekvence jadra, pameti zustanou pretaktovany.
Co s tim, help.

Pak mam stejny problem jako Erik_1, monitoring otacek vetraku, taky slysim zmenu otacek, ale nemuzu vybrat graf pro zobrazeni.

doplnění k riva tuneru - doplnění podpory pro 7600GS/GT AGP

je nutno otevřít RivaTuner.cfg a doplnit údaje
[GPU_10DE]
NV4B = 390h-39Fh
položku výše změnit na
NV4B = 390h-39Fh,2E0h-2E2h

budou takto podporované všechny známé 76xx pro AGP

RivaTuner 2.0 RC 16.1
http://www.svethardware.cz/support-d...1005583CD.html

RivaTuner 2.0 RC 16.2
http://www.guru3d.com/index.php?page=rivatuner&menu=8
(hodně věcí přidáno pro G80 karty)

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

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 :)

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

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

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

Rivatuner 2.03 released

Download

Citace:

---

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:

Citace:

---

Původně odeslal Unwinder

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.

---

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.

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.

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

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.

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

Sakra, to abych to dal rychle pryc :mweheh:

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.

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.

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

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

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

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

Citace:

---

Původně odeslal Doktor-Prase

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

---

...že by první post?

Citace:

---

Původně odeslal Over

...že by první post?

---

Mae culpa...

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:D

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.

Nefunkcni se Sapphire AGP HD3850...

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

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.

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 :(

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.

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

Citace:

---

Původně odeslal 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.

---

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?

Citace:

---

Původně odeslal 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

---

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

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.

RivaTuner 2.10

Download


Minor bugfixes:

• Fixed core clock gating detection code for G8x and newer display adapters. RivaTuner no longer erroneously detects core clock generator switching to PCI-E bus clock and no longer monitors wrong 100MHz core / shader clock under certain conditions (e.g. wrong shader clock on GeForce GTX 260 / 280 series in idle mode).
• Driver-level fan control is no longer forcibly switching to direct fan control mode when driver-level system tweaks dialog is being closed and "Fan" tab is not in focus.

What's new:

• Added ForceWare 177.xx drivers family support.
• Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 175.16, 175.19, 177.26, 177.35, 177.39, 177.41, 177.66, 177.70, 177.72, 177.73, 177.79, 177.83, 177.89 and 177.92.
• Added Catalyst 8.5, 8.6, 8.7 and 8.8 drivers detection.
• Updated Catalyst 8.5, 8.6, 8.7 and 8.8 certified SoftR9x00 patch script (for Windows 2000/XP drivers only).
• Improved NVIDIA GT200 graphics processors family support. Thanks to Jacob Freeman @ EVGA for providing NVIDIA GeForce GTX 260 display adapter sample for testing.
• Added AMD RV770 graphics processors family support. Now almost all RivaTuner's features including overclocking, low-level fan control and hardware monitoring are fully available on AMD RADEON HD 48x0 series display adapters. Thanks to Hilbert Hagedoorn @ The Guru of 3D for providing AMD RADEON HD 4850 display adapter sample for testing. Please take a note that currently RivaTuner doesn't support direct access to generic I2C bus and flashrom on RV770 GPUs, so generic I2C bus access based features (e.g. RADEON HD 4870 X2 fan control and monitoring) and VGA BIOS image dumping features are currently not available.
• Improved set of technologies aimed to improve RivaTuner startup and usage safety in conjunction with other hardware monitoring and diagnostics related tools:
  
  • Previously used low-level I2C synchronization protocol is now also applied to driver-level fan control 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 or EVGA Precision).
• Updated bundled RivaTunerStatisticsServer v2.8.0 utility:
  
  • New server uses improved hook notification system and more aggressive hooks unload routines aimed to minimize the situations which require system reboot during server uninstallation.
  • Added new OSD rendering mode. Optional configurable OSD background improves OSD text readability in some applications and prevents it from merging with solid color screen. Please take a note that new mode doubles performance hit caused by OSD rendering so it is recommended to use in only when needed via the server's application profiles.
  • Updated pseudo-3D applications list.
• Updated exceptions list for bundled D3DOverrider utility.
• Improved hardware monitoring module:
  
  • Now hardware monitoring plugin activation wizard module enables ADT7473 plugin by default on GeForce GTX 260 / 280 series display adapters.
  • Improved memory clock gating detection for GeForce GTX 260 / 280 series display adapters.
  • Improved VT1103.dll plugin:
    
    • Added support for voltage regulator output and average current monitoring on NVIDIA GeForce GTX 260 / 280 series. Please take a note that Volterra voltage regulators are rather sensitive to frequent polling and may return false data under heavy load, so it is not recommended to use VRM monitoring in daily monitoring sessions.
    • Added support for serial VID encoding mode for VT1165 voltage regulators to provide proper voltage regulator output monitoring on AMD RADEON HD 4870 and GeForce GTX 260 / 280 series display adapters.
    • The plugin no longer uses hardware database to detect used VID encoding mode. Now the plugin directly reads hardwired VID encoding mode defined by configuration resistors.
    • Optimized average current monitoring implementation for VT1105/VT1165 voltage regulators. Now the plugin pre-calculates and pre-caches maximum output current instead of calculating it on each average current read request.
• Updated license agreement. New license agreement explicitly restricts publishing any links to RivaTuner on www.nvnews.net homepage or in www.nvnews.net discussion forums.
• Minor UI changes and improvements.

RivaTuner 2.11

Download

Minor bugfixes:

• Low-level hardware access interfaces are now re-initialized properly before restarting the plugins when changing display adapter selection in the main tab

.

What's new:

• Updated databases for Detonator and ForceWare drivers. Added database for ForceWare 177.98.
• Added experimental AMD RV710 and RV730 graphics processors families support. Thanks to Andrey Vorobiev for testing RivaTuner with AMD RADEON HD 4670.
• Display adapter enumeration routine has been modified to provide proper fan control on AMD RADEON HD 4870 X2 series. New enumeration routine also gives additional advantages to the rest systems:
• Now RivaTuner is able to detect physical display adapters attached to logical Windows display devices as well as unattached physical display adapters. Low-level access to unattached display adapters gives you the following abilities:
• Ability to use RivaTuner for low-level diagnostics, hardware monitoring and fan control even when Windows is booted in VGA mode (e.g. in safe mode or with no display driver installed).
• Ability to use RivaTuner for low-level diagnostics, hardware monitoring and fan control for slave display devices in SLI / Crossfire mode invisible for OS.
• Attached display adapters detection time has been reduced due to optimized PCI bus scanning routine. Furthermore, both attached and unattached display devices detection are optional and can be forcibly disabled via DetectAttachedDevices and DetectUnattachedDevices registry entries for startup time optimization.
• Improved secondary display adapter heads enumeration. Now RivaTuner mirrors primary head specific settings (e.g. overclocking and fan control) into the secondaty head UI.
• Optimized startup time due to improved object dynamic/static casting in hardware abstraction layer.
• Added experimental overclocking support for the secondary display adapters in Crossfire systems (only for Windows Vista).
• Added experimental low-level fan control and overclocking settings cloning modes. When cloning mode is enabled RivaTuner clones and automatically applies the same low-level fan control or overclocking settings to all identical devices (i.e. the same display adapter models, different brands are allowed) installed in the system. Please take a note that currently these modes are available to power users only and can be enabled via EnableFanControlCloning and EnableClockControlCloning registry entries.
• Updated exceptions list for bundled D3DOverrider utility.
• Improved hardware monitoring module:
• Improved ADT7473.dll plugin:
• Added Vcc and Vccp voltages monitoring support. Now The the plugin can monitor state of +3.3V supply voltage of ADT7473 chip (Vcc) and additinal optional voltage input (Vccp), which can be used to monitor different display adapter related voltages depending on the PCB design (e.g. memory voltage on RADEON HD 4870 X2 series display adapters).
• Improved fan speed monitoring for fans with non-standard pulses per revolution count on tachometer output. Now the plugin no longer uses hardcoded calculations for standard fans with 2 pulses per revolution and can provide correct RPM monitoring for such systems (e.g. fans with 4 pulses per revolution on NVIDIA GeForce GTX 260 / 280 series).
• Improved VT1103.dll plugin:
• Now the plugin is able to monitor independent temperatures of VT1105/VT1165 voltage regulator phases (slave chips).
• Improved temperature monitoring for RV710 / RV730 / RV770 graphics processors family. Now RivaTuner is able to monitor independent temperatures of display controller, memory controller and shader core on RV7xx graphics processors. Please take a note that unlike many other diagnostic tools reading these temperatures via GPU's internal sensor switching and calibration logic, RivaTuner reads these temperatures via direct access to thermal sensor's ADC outputs and calibrates ADC readings at software level. Such approach drastically reduces CPU load and doesn't have side effects like fan speed fluctuations caused by frequent sensor switching, however it is in experimental stage yet so please contact me if additional core temperatures reported by RivaTuner and other software like GPU-Z or Everest seriously differ on your system. Please take a note that traditional sensor switching based access to these temperature sensors can be also enabled for debugging and performance comparision via ATIThermalSensorAccessModeR7xx registry entry.
• Optimized GPU usage monitoring for RV710 / RV730 / RV770 graphics processors family. Now RivaTuner is no longer waiting for response from on-die PowerPlay microcontroller if GPU usage is not sampled yet and returns the previous cached value instead.
• Now hardware monitoring plugin activation wizard module enables ADT7473 plugin by default on AMD READEON HD 4870 X2 series display adapters.
• Improved /SD and /SELECTDEVICE command line switches handler. RivaTuner's GUI is no longer activated and displayed when current display device selection is changed via these command line switches. This improvement allows you to switch target display device in multimonitor or multi-GPU SLI/Crossfire systems via hotkeys without leaving 3D application.
• Added I2C bus disconnection feature for ATI RV6xx/RV7xx I2C controllers. Now RivaTuner is able to mark I2C bus as unused and exclude it from further detection when I2C controller is not responding to the transactions through this bus during specified timeout. Bus disconnection feature drastically reduces I2C devices scanning time on some systems with missing I2C buses (e.g. on the secondary chip of AMD RADEON HD 4870 X2 having no physical connection to I2C bus). Please take a not that I2C bus disconnection can be disabled via AllowI2CBusDisconnection registry entry if necessary.
• Default timeout for ATI I2C transactions has been reduced from 2 seconds to 0.5 second. Now power users may adjust the timeout using ATII2CTimeout registry entry.
• Improved duty cycle generation accuracy for all types of on-die and external fan controllers due to floating point calculation usage.

RivaTuner 2.20

Download

http://i33.tinypic.com/fz89a8.jpg

RivaTuner v2.21
http://downloads.guru3d.com/download...4e3c6522abe9b7


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.

RivaTuner v2.22

http://downloads.guru3d.com/download...2463589da1b0c5

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.
  
  

Včera jsem se trápil s novou verzí RivaTuneru. Abych docílil přetaktování pro 3D, podtaktování pro 2D a start profilu 2D se startem windows. Takže jak na to

1. Ve skupině "Driver settings" -> customize -> system tweaks mastavit frekvence pro 3D a uložit třeba jako Profil-3D. Neutíkat z tohoto nastavení, ani nepřepínat mezi profily (zde nefunkční) posunout frekvence pro 2D a uložit třeba jako Profil-2D
2. Ve skupině "Target adapter" spustit Hardware monitoring -> setup a postupně zaškrtnout
- Hardware acceleration
- Hardware acceleration \OGL
- Hardware acceleration \DD
- Hardware acceleration \D3D8 ... D3D10
- kliknutím pravým tlačítkem myši na některou z částí grafu je možné tento vybraný parametr přes nabídku "setup" sledovat v liště windows, buď jako hodnotu, nebo jako barchart - s podmínkou, že zapnete červený "čudlík" "Enable background monitoring"
3. Spustíte Riva tuner server kliknutím na obrázek-ikonku "Riva tuner" se zelenou šipkou v grafu "Hardware acceleration"
4. Pokud vám Riva tuner server spadne do lišty, obnovte jej a zaškrtněte v nastavení "Start with windows" na "ON"
5. Najedete na tabelátor "Launcher" a vytvoříte profil typu "Regular menu item"
- název třeba "Launch-3D" a v nastavení zaškrtnete "Asociated overclocking profile" a přiřadíte mu dříve připravený Profil-3D
6. Zůstanete v tabelátoru "Launcher" a vytvoříte profil typu "Regular menu item"
- název třeba "Launch-2D" a v nastavení zaškrtnete "Asociated overclocking profile" a přiřadíte mu dříve připravený Profil-2D
7. Pokud jste dodrželi postup, klikáním na jednotlivé profily můžete nyní přepínat připravené 2D/3D profily manuálně.
8. Nejdůležitější nastavení, aby Riva tuner měnil profily automaticky při přechodech mezi 2D/3D a také se nastavil při startu windows profil 2D. Najeďte si na záložku "Scheduler", kde postupně vytvoříte 3 položky
- Název třeba "Schedule-3D", typ položky "Item", name vyberete z nabídky "Launch-3D", run task nastavte na "on hardware monitoring treshold event", Data source vyberte "Hardware acceleration", Treshold nastavte na "0.5", Direction na "upward"
- Název třeba "Schedule-2D", typ položky "Item", name vyberete z nabídky "Launch-2D", run task nastavte na "on hardware monitoring treshold event", Data source vyberte "Hardware acceleration", Treshold nastavte na "0.5", Direction na "downward"
- Název třeba "Startup", typ položky "Item", name vyberete z nabídky "Launch-2D", run task nastavte na "at Windows startup".
9. Otestovat správnou funkci můžete skvělým prográmkem "RthDribl", který spouští 3D akceleraci v okně. A to je vše, snad to pomůže někomu, kdo tápe v angličtině nebo nastavení tak mimořádně kvalitního prográmku, kterým RivaTuner bezpochyby je.

Nedavno jsem postupoval podle nasledujiciho navodu.

Create Video Card Profiles To Save Power And Reduce Noise
http://www.ghacks.net/2008/11/05/cre...-reduce-noise/

Jenom jeste dodam ze jsem na Gigabyte 8800 GT 512MB
docilil snizeni jen o 10W v idle, podtaktovani 180MHz jadro; 441MHz Shader; 300MHz memory.
Na Leadteku 8800GT 512MB byla uspora jeste mensi.

Zkratka na 8800GT se to IMHO temer nevyplati.

Citace:

---

Původně odeslal Halen

Včera jsem se trápil s novou verzí RivaTuneru.

---

Dobrý, ale imho ses trápil zbytečně.... SpeedyGT už to kdysi udělal ;)

Btw. taky sem před pár měsíci hledal :)

RealTemp plugin for RivaTuner

It works only with Intel CPU's which has a digital thermal sensor (DTS).

Works with Nehalem, Quad's, Core2Duo's and it's a big step forward from "old" Core2Duo plugin.

Unzip and copy the attached files into your RivaTuner/PlugIns/Monitoring directory and the rest should be easy. This plug-in includes Distance to TJMax for each core for those that like to keep an eye on that number.

download

Rivatuner take pouzivam a myslim ze je to dost dobry program.... Jen tak dal.

VoltageFactory v1.00. Umoznuje v spolupraci s RivaTuner-om zmenu voltaze na niektorych grafickych kartach.

Aktualne podporovane graficke karty:

• GTX260 65nm

• GTX280

• GTX295

• HD4850

• HD4870

• Graficke karty s chipom Volterra VT11xx

Download

RivaTuner v2.23

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

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.

Oprava chybného zobrazení frekvence paměti a otáček ventilátoru ne kartách nVidia - prozatím vím, že to dělá ne G92,G94
- Vytvořit soubor s názvem třeba MemoryPatch.rts, obsah souboru:
[Common]
SrcFile = RivaTuner.exe
DstFile = RivaTuner.new
BakFile = RivaTuner.old
MakeCRC = 1

Src0 = 3D A0 00 00 00 72 0B 6A 02
Dst0 = 3D 90 00 00 00 72 0B 6A 02

Spustit, soubor RivaTuner.new přejmenovat zpět na RivaTuner.exe a funguje to. Soubor i přikládám.

RivaTuner v2.24
http://downloads.guru3d.com/download...432a3976bff55a

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.