RivaTuner

[Jelc]

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

Version 2.04:

Minor bugfixes:
Fixed overclocking algorithms for ATI R3xx/R4xx GPU families, broken due to MMIO protection introduced in the previous version.
Fixed gamma correct antialiasing option for G7x GPU families, broken due to G8x related gamma correct antialiasing related changes in the previous version.
Fixed bug in the installer script, preventing automatic update installation system from installing the updates from a folder containing spaces in the path.
RivaTuner no longer stops working with access violation error when I/O driver is not loaded.
Minor UI and localization fixes.

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

Plug-ins:
Core 2 Duo Temp
http://downloads.guru3d.com/download.php?det=1545

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

[d0X]

jesu malo pojačali podržanost ati grafulja? jer su starije verzije bile više za nvidiu. i koliko se isplati grafu softmodat u firegl? vjerojatno se dobije malo bolje performanse u ogl-u ali jel se išta gubi u d3d-u?

[Jelc]

Autor d0X

jesu malo pojačali podržanost ati grafulja? jer su starije verzije bile više za nvidiu. i koliko se isplati grafu softmodat u firegl? vjerojatno se dobije malo bolje performanse u ogl-u ali jel se išta gubi u d3d-u?

Pa, ne sjećam se da ATI grafe nisu bile dobro podržane.
FireGL ti u stvari treba samo za posao.
Najbolje je napraviti dual-boot i na jednom OS-u imati igre, net i slično a na drugom posao.
Cijela 19xx serija daje jako dobre perfomanse kad se moda, 2600 PRO i XT isto tako.

[Razer]

Čeka se (najavljena) mogućnost mijenjanja taktova shadera u Rivi

Inače mislim da su ATi grafe u Rivi dosta dobro podržane, pa i sam clockam iz Rive kad ATT truje sa memorijom.

[Jelc]

Autor Razer

kad ATT truje sa memorijom.

Zbunj???

[Razer]

Pa da, dignem za jedan MHz memoriju bilo u ATiToolu, bilo u ATI Tray Toolsima, samo baci crni ekran i nema druge nego restart i meni je također

[Jelc]

Autor Razer

Pa da, dignem za jedan MHz memoriju bilo u ATiToolu, bilo u ATI Tray Toolsima, samo baci crni ekran i nema druge nego restart i meni je također

Meni je sa X1800 XL i XT, X1900XTX i sa mojom AIW radio ATT normalno.
2600XT-nije još podržan overclock.

Nisam probao X1950 GT.

[Razer]

Nemam pojma, ja probao na tri komada, dvije od 256MB, i jednu od 512MB...uvijek ista stvar. Na ATT-u smeđi ekran (low-level OC) a u AT-u crni ekran.

No dobro, nije bitno...nebih išao u offtopic, zato dobra stara Riva radi kako treba

[d0X]

pa ako vi tako kažete onda ću se vratit na rivu

[Razer]

Malo sam kopao po ATT-u i ATiToolu, za X1950 serije se čini da treba ugasiti Low level overclocking, tj clockati na Driver levelu. A pošto sam ja upravo suprotno radio na oba programa, dešavale su se gore navedene pogreške. Sad se radi kako treba. Sry na OT-u, samo sam htio pojasniti da ljudi nebi prebjegli na RT

[Jelc]

Ah, takozvana next, next, next instalacija ATT-a

[Router]

Dobra je ova verzija , koristim je za klokanje x1650 i ide dobro , cak i bolje nego sa zadnjim attom koji mi uporna skida frekvu memorije , ova riva zato sve štimac .

[nathan]

izasao je novi riva tuner 2.06, mozete ga skinuti s guru3d-a, no ono sto me iznenadilo je da je ekipa s techPowerUp-a platila Microsoftu "signed drivers" tako da korisnici x64 viste mogu korisiti riva tuner bez limitacija:

http://www.techpowerup.com/downloads...d_Drivers.html

popis svih noviteta i dodataka pogledajte ovdje:
version 2.06:

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 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 [COLOR=#000080 ! important][COLOR=#000080 ! important]ATI[/COLOR][/COLOR] 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 [COLOR=#000080 ! important][COLOR=#000080 ! important]graphics [COLOR=#000080 ! important]processors[/COLOR][/COLOR][/COLOR] 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 [COLOR=#000080 ! important][COLOR=#000080 ! important]NVIDIA[/COLOR][/COLOR] 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 [COLOR=#000080 ! important][COLOR=#000080 ! important]Vista[/COLOR][/COLOR] 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).
- 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 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).
- 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.
- 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.

[Wolverine]

evo stigla nova Riva

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


Version 2.06:

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.

[LorD ClockaN]

Ja imam posljednju betu, pa mi se neda ovaj final niti stavljat jer mi sve radi kak spada sa novim xg 167.26

[nathan]

[quote=Wolverine;858188]evo stigla nova Riva



stavio ja vec jucer: http://forum.pcekspert.com/showthread.php?t=85871

[Razer]

Izašla je i nova verzija popularnog Riva Tunera, verzije 2.07.

Službene stranice - Link

Download - Link

FAQ/Info - Link

Change log:

Version 2.07:
Minor bugfixes:

* Fixed default values for Direct3D Intellisample slider and "Clamp negative mipmap LOD bias" option.
* State of global OSD visibility setting is no longer lost when any other option is being changed immediately after changing the global OSD visibility setting in the properties of bundled RivaTunerStatisticsServer application.
* Minor UI and localization fixes.

What's new:

* Added ForceWare 171.xx, 173.xx and 174.xx drivers families support.
* Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 169.09, 169.13, 169.17, 169.21, 169.25, 169.28, 169.32, 169.38, 169.39, 171.16, 171.17, 171.23, 173.65, 173.80, 174.12, 174.13, 174.16, 174.23 and 174.31.
* Added Catalyst 7.11, 7.12, 8.1 and 8.2 drivers detection. Please take a note that both Catalyst 8.1 and 8.2 share the same binary file versions, so both Catalyst 8.1 and 8.2 will be detected as Catalyst 8.1 or newer.
* Updated Catalyst 7.11, 7.12, 8.1 and 8.2 certified SoftR9x00 patch script (for Windows 2000/XP drivers only).
* Updated PCI DeviceID database for both ATI and NVIDIA graphics processors. Added PCI DeviceIDs for RADEON 2600XT AGP, RADEON 2900GT, RADEON HD 3870 X2 and GeForce 8800GTS 512 SKUs. Please take a note that RivaTuner doesn't provide official Crossfire support, so RADEON HD 3870 X2 support can be limited to single GPU functionality under certain conditions.
* Unlocked previously available experimental RV635 graphics processors support. Thanks to Andrey Vorobiev for testing RivaTuner with ATI RADEON HD3650.
* Added experimental G94 graphics processors support. Thanks to Andrey Vorobiev and Hilbert Hagedoorn for testing RivaTuner with NVIDIA GeForce 9600GT.
* Added powerful built-in task scheduler module. Task scheduler has been designed as more flexible and more programmable replacement for the previously available programmable monitoring thresholds technology, providing you the following functionality:
o 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).
o Standard safety measures, allowing you to skip scheduled tasks if necessary (e.g. if you have programmed loading a profile with too agressive overclocking at Windows startup or if you have programmed RivaTuner to close itself at startup). You can hold key after logging in Windows to skip RivaTuner's tasks scheduled to be started with Windows or you can hold key during RivaTuner startup to skip RivaTuner's tasks scheduled to be started with it.
o 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:
o 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:
o 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.
o 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.
o 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:
o 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.
o 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:
o 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.
o 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.
o 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.
o 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:
o 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.
o 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.
o Added Direct3D10 (for non-multisampled frame buffers only) screen capture support.
o 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.
o Now the server is able to capture multiple screenshots at once if multiple 3D applications are running simultaneously.
o 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.
o 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.
o 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.
o Updated list of pseudo 3D applications.
* Improved hardware monitoring module:
o Now "Framerate" graph shows framerate from the focused application if there are multiple 3D applications running simultaneously.
o Added SEH for clock calculation routines for better protection against incorrect hardware emulation.
o Changed default Core/Memory clock graph ranges from 1.5GHz to 2GHz.
o 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:
o 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.

Download - Link

[karlito]

sad idem kupit novi komp, dosta mi je više patnje na starom, izlaze nove verzije programa, igre, svašta, a ja sam nemočan to isprobati na ovoj kanti, Agp, socket 478, DDR1, fuck of tooo....

[Mihael]

Autor karlito

sad idem kupit novi komp, dosta mi je više patnje na starom, izlaze nove verzije programa, igre, svašta, a ja sam nemočan to isprobati na ovoj kanti, Agp, socket 478, DDR1, fuck of tooo....

Kupi i meni nešto

[karlito]

Autor Mihael

Kupi i meni nešto

ja težim tak nečemu kak ti trenutno imaš, no dobro, malo bolje.....
....nebudemo sad pokretali spam, vratimo se na temu, kak vam se čini nova verzija Rive, koje korisne novosti donosi ???

[McG]

Autor karlito

koje korisne novosti donosi?

Piše ti u prvom postu odma nakon What's New. Ili hoćeš možda da ti neko prevede, eventulano sproba doma kod sebe, pa napiše mali vodič za sve novosti?

[karlito]

znam čitati, thx...netrebam prijevod....samo me zanimaju vaša mišljenja o novoj verziji, dal ima kakvih korisnih poboljšanja, jer ja ne koristim Rivu iz razloga kojeg sam naveo (stari komp)....

[nino]

....RADEON HD 3870 X2....

Dalje nisan citao Meni dosta.

[°¤•ßŁăĐ€•¤°]

Weeee! Radi sa SLI-em (isprobano), tako da sada mozete spaliti ne jednu, nego dvije kartice, lol.

[Mihael]

Meni se driver resetira stalno ako stavim gpu na 700, na 650 radi ok...
Ne kužim foru...

Help?

[mislav_os]

Autor °¤•ßŁăĐ€•¤°

Weeee! Radi sa SLI-em (isprobano), tako da sada mozete spaliti ne jednu, nego dvije kartice, lol.

I da,fora je sto podrzava HD3870 X2,sada ce biti testova s OC-anim 3870X2,auuuu

[Tekla]

odlicno podrzava mi 9600GT

[Daddy]

Tebi uopce ne treba SW za OC VGA.

[Tekla]

Autor Daddy

Tebi uopce ne treba SW za OC VGA.

??? nekuzim

[elvis again]

207 nema ovog crveno zaokruzenog plusica (threshold settings) i zato nisam mogel namjestat automatsku regulaciju venta
http://www.guru3d.com/admin/imageview.php?image=10671
dal postoji na 207 neki drugi nacin za to naparviti?