RivaTuner 2.06 veröffentlicht

jetztaber

PCGHX-HWbot-Member (m/w)
RivaTuner 2.06 veröffentlicht

Heute wurde der RivaTuner 2.06 online gestellt. Er steht hier zum Download:

http://downloads.guru3d.com/

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 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 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.
 
AW: RivaTuner 2.06 veröffentlicht

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


toll....
 
AW: RivaTuner 2.06 veröffentlicht


Das ist überhaupt nicht schlimm, da die drei Betriebsmodi in einem Profil jeweils einem Takt zugeordnet werden. Das bedeutet, dass ich z.B. einem Coretakt von 630 alle drei Betriebsmodi, nämlich Standard 2D, Low Power 3D und Performance 3D zuordne und als Profil benenne und speichere. Ich wechsle Profile und gut ist es. und wenn ich noch ein anderes habe, z.B. mit einem Coretakt von 290, kann ich zwischen diesen manuell wechseln oder über RT bei 3D-Spielen sogar automatisch.
 
Zurück