PDA

View Full Version : RivaTuner Version 2.0 Final Release


Pages : [1] 2 3

weeds
12-25-06, 05:03 PM
RivaTuner Version 2.0 Final Release

http://downloads.guru3d.com/download.php?det=163
http://forums.guru3d.com/showthread.php?t=208457

Version 2.0 Final Release:

Minor bugfixes:

- Removed obsolete warning message, offering user to enable alternate startup daemon mode when applying custom LowPower 3D clock frequencies at Windows startup. New alternate daemon usage approach is no longer compatible with switching alternate startup mode on the fly, so now LowPower 3D clock controls are simply blocked when alternate startup daemon mode is disabled.
- Minor UI and localization fixes.

What's new:

- Added ForceWare 97.28 and 97.44 drivers support.
- Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 93.28 and 97.44 drivers.
- Added ForceWare 97.44 compatible gamma corrected antialiasing control.
- Added Catalyst 6.12 drivers detection.
- Updated Catalyst 6.12 certified SoftR9x00 patch scripts.
- Updated PCI DeviceID database for NVIDIA graphics processors.
- Added workaround for G80 memory clock frequency generation bug of the ForceWare 97.28 and newer drivers. Unfortunately a lot of gamers with GeForce 8800 graphics adapters seem to be unable to understand the principles of multiple hardware clocking and aggressively react on any attempts to explain it. Due to that reason now by default RivaTuner displays memory clock of the only memory clock frequency generator programmed by all versions of the ForceWare drivers. The clocks of the rest two generators, which are erroneously left by the driver in BIOS default 400MHz state, are now hidden from eyes of beginners. The power users still can monitor independent clocks of all 3 memory clock frequency generators on G80 via GPUProbe.dll plugin. And the gamers unable to get technical details may relax and continue "fellas, my new 8800 is so cool" related discussions in the forums.
- Previously available experimental driver-level overclocking workaround is now enabled by default on RV560 and RV570 based display adapters. Power users may disable it with EnableDriverLevelClockControl registry entry.
- Hardware monitoring module's screenshot watermark image is now stored into .\Graphics\Watermark instead of .\Watermark folder.
- Updated RivaTunerStatisticsServer v2.2.0 bundled utility:
- Added new pseudo 3D applications to the profiles list.
- Added RivaTuner styled startup links checking, aimed to prevent conflicts between multiple simultaneously installed versions of the server. Now the server checks the startup registry link and offers you to correct it, it if is referring to other folder.
- Added workaround for 3D applications, wasting CPU time into erroneous page flip calls (e.g. Company of Heroes during movies rendering). Now the server checks flip call status and throws failed page flip calls from the statistics to avoid registering abnormally high framerate in such applications.
Improved hardware monitoring plugin API. Now the plugins can directly access NVIDIA driver resource manager's internal configuration and extended configuration data.
- Improved hardware monitoring module:
- The list of active hardware monitoring plugins is stored in the registry instead of the configuration file. This allows avoiding reenabling the plugins when reinstalling RivaTuner while keeping the previous version's settings.
- Previously available experimental OSD and tray tooltip values grouping modes are now enabled by default. Power users may disable these modes with EnableOSDGroups and EnableTooltipGroups registry entries.
- The font used to display hardware monitoring statistics in system tray icon is no longer fixed and can be customized by user. By default RivaTuner uses intelligent font size selection algorithm and automatically chooses the best font for currently selected display mode (large 7x9 pixels raster font for 1600x... and greater display modes, medium 7x7 pixels raster font for 1280x... and greater display modes and previously used small 5x7 pixels raster font for display modes below 1280x...). However, power users may redefine this behavior and select desired font manually by editing TrayFont registry entry. Furthermore, all the fonts are stored in .\Graphics\Tray folder as bitmap files so you can easily create your own font if necessary and force RivaTuner to use it with TrayFont registry entry.
- Improved tray icon text fitting algorithm. Now RivaTuner is able to display negative values in tray icon and uses more accurate algorithm when trying to fit too large values in the icon and displays as many significant digits as possible.
- Added barchart mode for values displayed it system tray icon. Now RivaTuner may optionally display either text values or barcharts in tray icon. Barchart mode is useful for the graphs, reflecting CPU usage, memory usage, etc.
- Now "Show ... in tray icon tooltip" option affects both primary and data source icon's tooltips. Displaying text value in the data source icon's tooltip is useful in conjunction with newly introduced barchart mode.
- Improved hardware monitoring plugins:
- Improved GPUProbe.dll plugin. Now besides GPIO pin reading for NV1X - NV4X GPU families the plugin also provides MPLL0 - MPLL2 clock reading for G80 GPU family. Power users may use it for monitoring clocks of all G80 memory clock domains.
- Added NVHwAccel.dll plugin. The plugin demonstrates developers usage of newly introduces functions for accessing NVIDIA driver resource manager's configuration and extended configuration data. The plugin accesses NV_CFGEX_PERF_MODE extended configuration data and provides hardware monitoring module "Hardware acceleration" graph, showing if any application using NVIDIA driver's hardware acceleration is currently running. Power users may define the thresholds on this graph for simple 3D application events start / stop detection, e.g. when defining a threshold for separating 2D/3D fan speeds on the cards with temperature based fan controller.
- Improved low-level graphics subsystem diagnostics module:
- Added boot core clocks and memory clock for G80 VGA BIOS images to "NVIDIA VGA BIOS Information" diagnostic report category.
- Improved multilanguage engine debugging features for third party localization pack creators:
- Added localization pack comparison mode. Now third party localization pack creators can use RivaTuner's /CL or /COMPARELOCALIZATION command line switches to generate LocalizationDifferences.log, containing the list of differences between currently selected localization pack and specified one. The list of differences allows you to see which localized files or translation database entries have to be added to or removed from your localization pack when updating it for new version of RivaTuner. Please refer to "Updating localization pack" chapter of RivaTuner SDK documentation to get more detailed information.
- Special New Year present for all RivaTuner users. Direct3D triple buffering forcing feature, one of the most deeply hidden and most wanted Easter Eggs, is now unlocked and available for everybody! Deepest respect and personal thanks goes to Demirug, the developer of DXTweaker project and author of original Direct3D triple buffering concepts, for allowing it to happen. Now RivaTuner's distributive includes bundled DXTweaker concepts based D3DOverrider v1.3 tool, providing the following feature set:
- Simple, effective and beginner friendly user interface. Just start the utility and it will automatically force Direct3D triple buffering in all subsequently started applications. The utility is not limited to any OS or any graphics hardware, so it can be used for forcing triple buffering on the NVIDIA as well as on ATI graphics cards.
- RivaTunerStatisticsServer styled global and application specific profiles. You may globally enable or disable triple buffering forcing as well as do it for desired executable files only.
- Sound indication feature. D3DOverrider uses standard OS defined success and failure beeps on each back buffer count override event, allowing you to control triple buffering forcing status really easy.
- Triple buffering forcing support for fullscreen DirectDraw and DirectDraw derived Direct3D applications (DirectX7 and older).
- Triple buffering forcing support for windowed and fullscreen Direct3D8 applications.
- Triple buffering forcing support for windowed and fullscreen Direct3D9 applications.

Please take a note that D3DOverider is also included in encrypted format in the previous versions of RivaTuner, so if you're not willing to upgrade RivaTuner to a final release due to some reason, you can extract D3DOverrider from the previous versions by adding the following key to the registry then typing "RivaTuner.exe /E D3DOverrider" in the command line:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Unwinder\RivaTuner\Eas terEggs]
"86547637"=dword:72395256

Greatest thanks and the best wishes goes to all RivaTuner users, privately testing and using D3DOverrider tool during the last few years and honestly keeping their promises on not leaking it or not disclosing a key for unlocking it. I really appreciate it and deeply thank you for that.

- Added new Easter Eggs.
- FAQ updated.
- Minor UI changes and improvements.



Thanks for all your good work Unwinder! (xmasgrin) (xmassign)

.

Roadhog
12-25-06, 07:16 PM
:O Thanks for this. :D

EDIT: It seems as the memory clock is fixed... So I guess I was right all along?

Quick420
12-25-06, 07:26 PM
Thnx for the excellent work.Rivatuner has always worked well for me(cheers)

stevemedes
12-25-06, 08:06 PM
mmmmm...
i love rivatuner

(cheers)

Shocky
12-25-06, 08:09 PM
:O Thanks for this. :D

EDIT: It seems as the memory clock is fixed... So I guess I was right all along?

Soo, did this ever actually affect performance or just a cosmetic bug?

jAkUp
12-26-06, 12:04 AM
Hmmm... according to the dev, the memory clock misreport was actually a bug in the drivers...

Roadhog
12-26-06, 12:06 AM
Hmmm... according to the dev, the memory clock misreport was actually a bug in the drivers...

If its a bug in the drivers, then why did it get fixed in this release? Maybe its reading the higher clocked memory thing, since he said that 2 out of the 3 are running at 400mhz.

Unwinder
12-26-06, 02:13 AM
If its a bug in the drivers, then why did it get fixed in this release? Maybe its reading the higher clocked memory thing, since he said that 2 out of the 3 are running at 400mhz.

Guys, is it so hard to read the posting you're commenting? Changes list from posting #1 clearly says the following:


Added workaround for G80 memory clock frequency generation bug of the ForceWare 97.28 and newer drivers. Unfortunately a lot of gamers with GeForce 8800 graphics adapters seem to be unable to understand the principles of multiple hardware clocking and aggressively react on any attempts to explain it. Due to that reason now by default RivaTuner displays memory clock of the only memory clock frequency generator programmed by all versions of the ForceWare drivers. The clocks of the rest two generators, which are erroneously left by the driver in BIOS default 400MHz state, are now hidden from eyes of beginners. The power users still can monitor independent clocks of all 3 memory clock frequency generators on G80 via GPUProbe.dll plugin. And the gamers unable to get technical details may relax and continue "fellas, my new 8800 is so cool" related discussions in the forums.

Grestorn
12-26-06, 04:43 AM
Guys, is it so hard to read the posting you're commenting? Changes list from posting #1 clearly says the following:


Added workaround for G80 memory clock frequency generation bug of the ForceWare 97.28 and newer drivers. Unfortunately a lot of gamers with GeForce 8800 graphics adapters seem to be unable to understand the principles of multiple hardware clocking and aggressively react on any attempts to explain it. Due to that reason now by default RivaTuner displays memory clock of the only memory clock frequency generator programmed by all versions of the ForceWare drivers. The clocks of the rest two generators, which are erroneously left by the driver in BIOS default 400MHz state, are now hidden from eyes of beginners. The power users still can monitor independent clocks of all 3 memory clock frequency generators on G80 via GPUProbe.dll plugin. And the gamers unable to get technical details may relax and continue "fellas, my new 8800 is so cool" related discussions in the forums.


I understood you all along, Unwinder, which kept me from using a later driver than 97.02. Anyway, isn't there any way to let RT program the memory clock generator, thereby actually fixing the problem?

Damn, they changed the gamma correction flags AGAIN? Didn't know that. Now I have to fix nHancer again :(

Anyway: Thanks for your great work!

Unwinder
12-26-06, 05:47 AM
Anyway, isn't there any way to let RT program the memory clock generator, thereby actually fixing the problem?

You cannot do it easily, because clocks frequency generators are programmed by the driver rather than by an overclocking tool. However, there is a way to access any part of hardware (including PLLs) directly: one of RT's Easter Eggs is undocumented command line interface for direct access to GPU's registers.

WR (Write Register) command line switch can be used to program the chip's PLLs.
Syntax is: RivaTuner.exe /WR<HEX_REG>,<HEX_DATA>

Addresses of all 3 MPLLs (each PLL is controlled by 2 registers) can be grabbed from GPUProbe.cfg. And RR (Read Register) command line switch can be used to read data from MPLL0.

Warning! It may be not enough to rewrite PLLs only, some memory controllers require restart sequence after programming.


Damn, they changed the gamma correction flags AGAIN? Didn't know that. Now I have to fix nHancer again :(!

Yep, the bit has been changed again in 97.44.

Shocky
12-26-06, 07:29 AM
I'd still like to see benchmarks showing this actually affecting performance.. Not that I care, im still using 96.89.. (xmastong) (xmassign)

DSC
12-26-06, 10:15 AM
Can someone with contacts at Nvidia please get them to fix the memory clock generator bug once and for all? I remember the old 2D Image Sharpening bug with the Forceware drivers and that took a LONG time to get fixed. Don't let this take a long time to be fixed like that bug.

Roadhog
12-26-06, 06:05 PM
Guys, is it so hard to read the posting you're commenting? Changes list from posting #1 clearly says the following:


Added workaround for G80 memory clock frequency generation bug of the ForceWare 97.28 and newer drivers. Unfortunately a lot of gamers with GeForce 8800 graphics adapters seem to be unable to understand the principles of multiple hardware clocking and aggressively react on any attempts to explain it. Due to that reason now by default RivaTuner displays memory clock of the only memory clock frequency generator programmed by all versions of the ForceWare drivers. The clocks of the rest two generators, which are erroneously left by the driver in BIOS default 400MHz state, are now hidden from eyes of beginners. The power users still can monitor independent clocks of all 3 memory clock frequency generators on G80 via GPUProbe.dll plugin. And the gamers unable to get technical details may relax and continue "fellas, my new 8800 is so cool" related discussions in the forums.



Ahaha, I missed that part.. my bad. I still love the program and great work. :D

So this basically has no affect on performance unless the program uses over 256MB of Vram?

GitDat
01-01-07, 11:19 AM
Is there a way for RivaTuner to go to 100% fan utilization on the GPU ONLY when games are launched? I want the GPU fan to run at 80% when idle and 100% while gaming.

I see I can save different profiles for each but I don't see a way to bounce between the profiles "automatically" :bleh:

SLippe
01-01-07, 12:06 PM
Is there a way for RivaTuner to go to 100% fan utilization on the GPU ONLY when games are launched? I want the GPU fan to run at 80% when idle and 100% while gaming.

I see I can save different profiles for each but I don't see a way to bounce between the profiles "automatically" :bleh:
Are you looking at where you set the 3 different fan speeds? You can set it to 100% in the 3D mode(s), so when you start a game it will speed up to 100% and then when you exit, it will go back down to whatever you have it set at for 2D mode, like 80% if that is what you have it set at.

GitDat
01-01-07, 12:29 PM
Are you looking at where you set the 3 different fan speeds? You can set it to 100% in the 3D mode(s), so when you start a game it will speed up to 100% and then when you exit, it will go back down to whatever you have it set at for 2D mode, like 80% if that is what you have it set at.

I tried messing with those but they don't seem to change the GPU fan at all. Are those for case fans or something? The only one that changed the fan speed for me was under the low-level fan control setting.

GitDat
01-01-07, 02:14 PM
Are you looking at where you set the 3 different fan speeds? You can set it to 100% in the 3D mode(s), so when you start a game it will speed up to 100% and then when you exit, it will go back down to whatever you have it set at for 2D mode, like 80% if that is what you have it set at.

http://i11.photobucket.com/albums/a154/gitdat/Miscellaneous/Riva.jpg

I've tried changing all these settings and nothing at all changes the GPU fan speed. Has anyone else gotten this section to work right?

rewt
01-01-07, 02:45 PM
Has anyone else gotten this section to work right?

Yes. Works great here. I set mine to 90/90/100%. Even works with SLI, adjusting fan speeds on both of my cards.

Perhaps your graphics cards are not reference design, but custom?

GitDat
01-01-07, 02:47 PM
I think it doesn't work on the 8800 series cards :( Ugh, figures.

Darkoz
01-01-07, 09:01 PM
http://i11.photobucket.com/albums/a154/gitdat/Miscellaneous/Riva.jpg

I've tried changing all these settings and nothing at all changes the GPU fan speed. Has anyone else gotten this section to work right?

For the 8800 series cards (and 7800/7900) you have to use Low Level Fan Control to adjust the fan speed.

Is there a way for RivaTuner to go to 100% fan utilization on the GPU ONLY when games are launched? I want the GPU fan to run at 80% when idle and 100% while gaming.

There are a few different ways you can set RivaTuner to automatically adjust the fan speed for the 8800 cards.
Remember that the 8800 cards do not have seperate 2D/3D core clocks by default so you'll have to be a bit creative and find different ways of doing it.
One way is to create your fan profile linked to the card's core temperature so when you start up a game and the card's temp increases the fan will automatically increase accordingly, which is how I set mine up and it works very well.

In Low Level System Settings choose the Fan tab, place a tick next to Enable low level fan Control and below that choose fixed, then set up a fan profile. For instance, I've simply named mine 2D 65% and 3D 80%, where I've set the 2D Fan @ 65% and the 3D Fan @ 80%.

Then in the Launcher tab set your 2D/3D fan profile as the associated fan profiles.
Then in low Level Hardware Monitoring right click on the Core Temperature graph, go to setup and create your 2D and 3D temperature thresholds.
For instance, you could set both the 2D/3D upward and downward threshold at 60C so when the card's temp goes over 60C the fan will increase to 80% and when the card's temp drops again to below 60C the fan will decrease to 65%, (of course you can set your fan profile and temp threshold to whatever you prefer.)
(also remember that you need to have RivaTuner running in the background for it to work)

That's just a brief overview of one way of doing it and I find for me it works well.

badboy64
01-02-07, 05:05 AM
For the 8800 series cards (and 7800/7900) you have to use Low Level Fan Control to adjust the fan speed.



There are a few different ways you can set RivaTuner to automatically adjust the fan speed for the 8800 cards.
Remember that the 8800 cards do not have seperate 2D/3D core clocks by default so you'll have to be a bit creative and find different ways of doing it.
One way is to create your fan profile linked to the card's core temperature so when you start up a game and the card's temp increases the fan will automatically increase accordingly, which is how I set mine up and it works very well.

In Low Level Fan Control you set up a fan profile, for instance I've simply named mine 2D 65% and 3D 80%, where I've set the 2D Fan @ 65% and the 3D Fan @ 80%.

Then in the Launcher tab set your 2D/3D fan profile as the associated fan profiles.
Then in low Level Hardware Monitoring right click on the Core Temperature graph, go to setup and create your 2D and 3D temperature thresholds.
For instance, you could set both the 2D/3D upward and downward threshold at 60C so when the card's temp goes over 60C the fan will increase to 80% and when the card's temp drops again to below 60C the fan will decrease to 65%, (of course you can set your fan profile and temp threshold to whatever you prefer.)
(also remember that you need to have RivaTuner running in the background for it to work)

That's just a brief overview of one way of doing it and I find for me it works well.
Thanks for the guide. That worked great for me. :) Can you shown a screenshot of the fan settings seup?

Darkoz
01-02-07, 08:38 PM
Thanks for the guide. That worked great for me. :) Can you shown a screenshot of the fan settings seup?


Do you mean this one?.......

http://img148.imageshack.us/img148/559/fanprofiletf6.th.jpg (http://img148.imageshack.us/my.php?image=fanprofiletf6.jpg)

badboy64
01-02-07, 09:52 PM
Do you mean this one?.......

http://img148.imageshack.us/img148/559/fanprofiletf6.th.jpg (http://img148.imageshack.us/my.php?image=fanprofiletf6.jpg)
I got that already. I want to see how you set the threshold settings with the hardware monitor. I tried setting but it isn't doing nothing at all. The settings on the right.
http://img406.imageshack.us/img406/4228/rivatunerlk0.th.jpg (http://img406.imageshack.us/my.php?image=rivatunerlk0.jpg)

GitDat
01-02-07, 10:08 PM
http://i11.photobucket.com/albums/a154/gitdat/Miscellaneous/riva1.jpg
http://i11.photobucket.com/albums/a154/gitdat/Miscellaneous/riva2.jpg

That's how I have mine setup. I used this guide and was able to get it going---> http://home.comcast.net/~msl2/RivaTuner.htm

Darkoz
01-03-07, 12:31 AM
I got that already. I want to see how you set the threshold settings with the hardware monitor. I tried setting but it isn't doing nothing at all. The settings on the right.
http://img406.imageshack.us/img406/4228/rivatunerlk0.th.jpg (http://img406.imageshack.us/my.php?image=rivatunerlk0.jpg)

On the right side window in your screenshot for Core Temperature Threshold Setup and half way down there's a Launch drop down box you need to choose Item (not application as you have it) for both the upward and downward threshold crossing.
Once you change it to Item you then select your 3D fan profile for the upward threshold and then select your 2D fan profile for the downward threshold.


http://img352.imageshack.us/img352/5903/fanprofilemy6.th.jpg (http://img352.imageshack.us/my.php?image=fanprofilemy6.jpg)