Rivatuner 15.8 coming features

[Ubermann]

Scheduled on 30.11.2005

From Guru3D forum: (its a long list with changes)

Minor bugfixes:

- Fixed *.RTP / *.RTR / *.RTS files shell integration under Windows XP x64 edition.
- Fake DDR detection algorithm is no longer forced by default on GeForce 7800 series.

What's new:

- Added ForceWare 81.xx and 82.xx driver families support.
- Updated databases for Detonator and ForceWare driver families. Added databases for ForceWare 81.26, 81.33, 81.82, 81.84, 81.87, 81.94 and 82.10 drivers.
- Added Catalyst 5.10 and 5.11 drivers detection.
- Updated Catalyst 5.10 and 5.11 certified SoftR9x00 patch script (32-bit versions only).
- Added support for mainboards with more than 8 physically addressable PCI-compatible slots (e.g. ASUS P5WD2)
- Revised registry access layer code:
- HKEY_CURRENT_USER registry root can be accessed via IO driver now.
- The list of keys with driver restricted access is no longer hardcoded to HKEY_LOCAL_MACHINE\Software\Unwinder\RivaTuner and can be redefined via the configuration file.
- Improved low-level refresh overrider module. Added injection based refresh override mode. Opposing to the previously available refresh override modes performing refresh override after actual display mode change, new refresh override mode allows RivaTuner to intercept any attempts of display mode change and override target refresh rate without allowing OS to set requested refresh. This results in improving compatibility with some display mode change sensitive applications.
- Added X1800 / X1600 / X1300 series support. Now all RivaTuner's low-level features including overclocking, low-level diagnostics, monitoring and gamma correction are available on newest ATI graphics processors. Thanks to Peter Yeung @ HIS for providing X1800XL sample for testing. Please refer to 'Known issues' section to get more details on RADEON X1000 family support.
- Improved GeForce 7800 series support. This versions introduces a lot of new GeForce 7800GT/TX specific features, including new low-level tuning options, driver-level Direct3D/OpenGL tuning options, improved low-level hardware diagnostics and monitoring improvements. Thanks to Andrew Worobiew and AIC willing to remain anonymous for providing GeForce 7800GTX sample.
- Improved low-level fan control module:
- Low-level fan control tab is no longer exclusively available on LM63 capable display adapters. Now low-level fan control is also available on display adapters equipped with F76363S (some HIS RADEON X800 series), LM64 (RADEON X1800 series) and ADT7473 (GeForce 7800GTX series).
- It is no longer assumed that automatic fan speed control mode is enabled by defaults. Now fan control module saves state of fan controller during enabling fan control.
- Added low-level fan profiles. Combining with RivaTuner's flexible monitoring thresholds programming technique, low-level fan profiles allow you to implement many useful dynamic fan control techniques (e.g. independent 2D/3D fan speeds).
- Improved driver-level fan control module:
- Added driver-level fan profiles. Combining with RivaTuner's flexible monitoring thresholds programming technique, driver-level fan profiles allow you to implement many useful dynamic fan control techniques (e.g. temperature controlled fan speeds, even if your display adapter is not equipped with temperature based fan speed controller).
- Added "Defaults" button for resetting driver-level 2D / LowPower3D / 3D fan speeds to defaults defined in VGA BIOS.
Improved driver-level overclocking module:
- Added driver-level overclocking profiles. Combining with RivaTuner's flexible monitoring thresholds programming technique, driver-level overclocking profiles allow you to alter ForceWare's 2D/3D clock frequency profiling system and implement alternate overclocking techniques (e.g. implement 2D/3D memory clock frequency separation, temperature based overclocking etc).
- Improved Direct3D / OpenGL tuning options for ForceWare drivers:
- Direct3D Quality / Performance texture filtering preferences have been moved from Direct3D tab to new separated Direct3D Intellisample tab.
- Added Direct3D negative LOD bias clamping option.
- Added options for controlling anisotropic / trilinear filtering optimizations to both Direct3D and OpenGL Intellisample tabs.
- Added transparent antialiasing controls for GeForce 7800 series.
Improved profile manager for the ForceWare's own application profiling engine:
- Added ability of editing profiles containing more than 32 characters.
- Added ability of associating color scheme with a profile.
- Regular launcher item editor UI has been changed slightly to accommodate newly introduced fan / overclocking profiles association. Now you may associate low-level / driver-level fan profile or driver-level overclocking profile with a launcher item and apply desired settings during application runtime only, as well as create items for quick activating desired profile.
- Improved built-in registry editor. Added an ability of viewing / editing variable size binary values.
- Improved hardware monitoring plugins engine:
- Added hardware monitoring plugin activation wizard. Now each plugin contains configuration file with a database of display adapters, which can retrieve useful information via this plugin. During the first hardware monitoring module activation, the wizard will check the list of currently active plugins and automatically prompt you to enable all inactive the plugins, which can provide useful information specific to your hardware configuration.
- All the sources provided by a plugin are automatically enabled now after activating the plugin module.
- Drastically reduced CPU overhead during plugin API functions calls due to global precached hardware access layer object usage instead of dynamically created hardware access layer objects in the previous version.
- Improved hardware monitoring plugins API.
- Added functions for R/O access to display adapter's VGA BIOS.
Improved hotkey manager. Added optional hotkey handler emulation via low-level keyboard hooks.
- Added /M command line switch for setting marker at the current position on hardware monitoring graphs. This feature allows you to mark some critical moments in the log (e.g. the moment of rendering artifacts appearance for subsequent thermal statistics analysis).
- Updated IO driver. Added timeouts for I2C transaction completion wait loops to IOCTLs for ATI I2C access.
- Undated NVStrap driver v1.10:
- Added NV42 GPU support.
- Updated RivaTunerStatisticsServer v1.5.0 bundled utility:
- The server's properties window is created in inactive state now to prevent the server from stealing input focus from certain 3D applications during the server's startup. This feature is useful when the server's launch is bound to a hotkey and it ensures that the server's runtime load will not cause 3D application minimization due to loss of input focus.
- Now the server is automatically injected in foreground application during startup.
- Added option for OSD coordinate space selection. By default the server uses 3D application's rendering viewport coordinate space. However certain applications (e.g. Codename Panzers: Phase II) can use multiple viewports during frame rendering. In this case OSD coordinate space origin will be located in the top-left corner f the last viewport, defined during frame rendering, which may not match with top-left corner of screen. In this case you may use new option to force different OSD coordinate space usage.
- Added benchmark statistics recording ability. Now the server allows client applications to initiate framerate statistics recording either via command line or via shared memory and to stop statistics and flush it to file per client's request at desired moment of time. The statistics can be optionally displayed in the server's OSD, and it includes:
- Total benchmarking time and total amount of rendered frames.
Global average framerate (total amount of rendered frames divided by total benchmarking time).
- Minimum instantaneous framerate (instantaneous framerate is measured once per second, minimum value is recorded)
- Average instantaneous framerate (instantaneous framerate is measured once per second, then all the measurements are averaged)
- Maximum instantaneous framerate (instantaneous framerate is measured once per second, minimum value is recorded)
- Improved low-level hardware monitoring module:
- Improved hardware monitoring threshold engine:
- Added ability of associating launcher items with threshold upward / downward crossing events. This feature allows you to associate desired event (e.g. critical temperature threshold crossing in upward direction) with any combination of profiles available in RivaTuner (e.g. boost fan speed to maximum with fan profile and downclock display adapter via overclocking profile).
- Added ability of defining color of each threshold on the graph.
- Added multiple tray icons mode for monitoring data sources displayed in tray icon. Now the sources' 'Show .. in tray icon' options are no longer mutually exclusive and multiple data sources may be simultaneously displayed in tray icons. Take a note that you may also activate previously available single tray icon mode using DisableMultipleTrayIconMode registry entry.
- Now you can click a source's tray icon to get quick access to the corresponding monitoring data source's properties. Please take a note that this feature is available only in multiple tray icons mode.
- Tray icon text color customization option is no longer power user oriented and is now available in the source's propertied dialog.
- Updated ADT7473.dll plugin
- Added 'Fan duty cycle' data source, allowing you to see target temperature controlled fan speed, programmed by fan controller.
- Added fan stop case detection for 'Fan speed' data source.
- Updated VidMem.dll plugin:
- Added 'Non-local videomemory usage' data source.
- Added 'Videomemory usage' data source.
- Updated W83L785R.dll plugin:
- Added F75373S-styled user extendable voltage calibration database.
- Added 'Fan speed' data source.
- Added LM63.dll plugin, supporting LM63 and clone devices (F75363S and LM64). The plugin provides 'Core temperature', 'Ambient temperature', 'Fan duty cycle' and 'Fan speed' data sources. Please take a note that 'Fan speed' data source is only available if the fan's tachometer output is physically connected to the sensor's tachometer input (e.g. RADEON X1800 series).
- Added VT1103.dll plugin for reading diagnostic information from Volterra VT1103 voltage (used on ATI RADEON X1800 series). The plugin provides 'Voltage regulator output' (target output voltage defined by voltage regulator's VID pins), 'Voltage regulator temperature' and 'Voltage regulator current' data sources. Please take a note that there are no public VT1103 datasheets available, and VT1103 VID table used by ATI's own voltage control tools is simply plain wrong (viva ATI software development team again ), that is why the plugin gives you an ability of redefining VID -> voltage mappings. The plugin's database contains ATI's own erroneous voltage mapping table and corrected voltage table created using real Vcore measurements for each VID.
- Added NVThermalDiode plugin. This plugin provides 'Core temperature' data source on the systems with on-die thermal diode capable GPUs (NV43, NV44 and NV47). Now GeForce 6600 owners no longer need to patch VGA BIOS for thermal monitoring unlocking, the plugin is able to retrieve temperature from on-die thermal diode even on locked VGA BIOS.
- Improved graphics subsystem diagnostic report module:
- Revised diagnostic report text format. Please take due to these changes you cannot directly compare this version's diagnostic reports with reports captured using the previous versions of RivaTuner.
- Added "Core VID" graph for NV41 and NV47 GPUs.
- Added NV47 specific VID interpretators to the database.
- Added thermal table dumping ability for BIT based VGA BIOSes. Now RivaTuner is able to display thermal compensation (sensor specific delta between temperature reported by sensor and approximated core temperature), on-die thermal diode calibration parameters (thermal diode offset and thermal diode gain) and core / ambient thermal thresholds.
- Added ability of defining GPU family specific register dumps. This feature was added special for ATI R5xxx family dianostics, and it allows using different registers sets or different naming schemes of the same registers depending on GPU family. Please take a note that currently the names of R5xxx specific registers are encoded in RivaTuner's diagnostic reports to prevent info stealing by some third party developers. I also warn some unethical guys behind ATI oriented tweaking/overclocking tools, that all R5xxx related hardware access code is watermarked with dummy GPU registers reads/write. So please use your own minds instead of cloning, my eyes are on you
- Updated SDK:
- Added LM63.dll plugin source code.
- Added VT1103.dll plugin source code. This plugin demonstrates access to VT1103 voltage regulator.
- Added NVThermalDiode.dll plugin source code. This plugin demonstrates access to on-die thermal diode of the latest NVIDIA GPUs. Additionally, the plugin demonstrates usage of newly introduced VGA BIOS and GPU registers access functions.
- FAQ updated.
- Minor UI changes and improvements.

http://forums.guru3d.com/showthread.php?threadid=160442

[spajdr]

so no voltage change for X1800 cards?

[bazx]

so no voltage change for X1800 cards?

hehe you must have eagle eyes :)

[`SippY]

i was just gonna say that

[G H Z]

It will be interesting to see how this new version handles X1800 series overclocking compared to Overclocker & ATI Tool which are very different..

[Hicks]

Ive been told this won't work with X1800 cards because of the 2d 3d clock speeds.

[G H Z]

The developer stated he added support for X1800 cards. I doubt he would release anything that does not work ;)

[Kunaak]

Ive been told this won't work with X1800 cards because of the 2d 3d clock speeds.

if that were true, then it wouldnt work on old cards like TI 4200's and such too. which it does, always has, always will...
2D and 3D have nothing to do, with the overall make of Rivatuner, it's just a feature it supports.

[Hicks]

Thought so.....

Roll on 5 days. i don't like ATi Tool at all, never have done. Can you overclock the XT with the Overdive tab in the mean time.

[Hicks]

So whats the word?

[spajdr]

Unwinder: My apologies, I'm currently doing some urgent changes in other commercial project, so 15.8 launch date will be probably shifted on Monday 5th.

[ugp]

Overdrive is what I have been use for my 24.7 clocks. It maxes out at 690/800 though. I look forward to any overclocking utilities that work well for my x1800XT.

[[XC]Atomicpineapple]

I emailed Unwinder about 15.8 beta testing last week and recieved this in reply.

What type of X1800XT do you have? Latest XT BIOSes are Overdrive3 capable, such cards use different 2D/3D clocks and voltages. Due to these specifics none of third party overclocking tools (including RivaTuner) will work on them (the driver will override third party clock changes due 2D/3D mode switch).

[saaya]

I emailed Unwinder about 15.8 beta testing last week and recieved this in reply.

What type of X1800XT do you have? Latest XT BIOSes are Overdrive3 capable, such cards use different 2D/3D clocks and voltages. Due to these specifics none of third party overclocking tools (including RivaTuner) will work on them (the driver will override third party clock changes due 2D/3D mode switch).

wow thats lame...so no ocing on the new ati cards? wth??

[Ubermann]

Hope bios flash solves that one..

[Hicks]

I emailed Unwinder about 15.8 beta testing last week and recieved this in reply.

What type of X1800XT do you have? Latest XT BIOSes are Overdrive3 capable, such cards use different 2D/3D clocks and voltages. Due to these specifics none of third party overclocking tools (including RivaTuner) will work on them (the driver will override third party clock changes due 2D/3D mode switch).

If thats true, that is truely wank.

What's it gonna take for use to be able to clock out X1800's properly?

[deathman20]

I emailed Unwinder about 15.8 beta testing last week and recieved this in reply.

What type of X1800XT do you have? Latest XT BIOSes are Overdrive3 capable, such cards use different 2D/3D clocks and voltages. Due to these specifics none of third party overclocking tools (including RivaTuner) will work on them (the driver will override third party clock changes due 2D/3D mode switch).


Hmmm if thats true, why does ATITool work switching clocks and voltages between the 2 modes as long as you set them up?

Was looking foward to using this program, since everyones talking so much about it. Guess might have to wait a little longer then I exepected.

[Nunyabiz]

Hmmm if thats true, why does ATITool work switching clocks and voltages between the 2 modes as long as you set them up?

Was looking foward to using this program, since everyones talking so much about it. Guess might have to wait a little longer then I exepected.


I have yet to see ATI tool working with an XT. I would like to know how to do it. When I set clocks with ATI Tool, it only sets 2d clocks according to overclocker. So what am I doing wrong? How do i set the modes in ATI tool?

[Hicks]

I have yet to see ATI tool working with an XT. I would like to know how to do it. When I set clocks with ATI Tool, it only sets 2d clocks according to overclocker. So what am I doing wrong? How do i set the modes in ATI tool?

Use ATi-Tool to change volts, and use the other OC tool, to change your clocks. Check your clocks ith ATi-tool, as they are accurate.

[deathman20]

I have yet to see ATI tool working with an XT. I would like to know how to do it. When I set clocks with ATI Tool, it only sets 2d clocks according to overclocker. So what am I doing wrong? How do i set the modes in ATI tool?

Don't know the XL doesn't seem to have a 2D/3D mode at all. Unless you make 2 seperate profiles in ATITool for it which I've always done with my past 2 cards (9800Pro and X800Pro). The clocks it boots with is what it is. So mines 499/495, and those are the actual clocks in 3D also.

But as we know, the XT is a different beast.

[deathman20]

Use ATi-Tool to change volts, and use the other OC tool, to change your clocks. Check your clocks ith ATi-tool, as they are accurate.

You can use OC to change volts its acurrate, just need to compensate the differences between the 2 programs. But I don't like that I get degraded preformance with OC compared to ATITool with when I OC my ram.

But is this different to the XT?

[Nunyabiz]

But as we know, the XT is a different beast.


Lol, I thought you new something I didnt. :)

Use ATi-Tool to change volts, and use the other OC tool, to change your clocks. Check your clocks ith ATi-tool, as they are accurate.

Yeah, I understand that, just want to use ATI tool so I dont have to do it each time I boot.

[Nunyabiz]

You can use OC to change volts its acurrate, just need to compensate the differences between the 2 programs. But I don't like that I get degraded preformance with OC compared to ATITool with when I OC my ram.

But is this different to the XT?

The problem is you cant yet use ATI tool to change clocks with the XT. AFAIK

[deathman20]

The problem is you cant yet use ATI tool to change clocks with the XT. AFAIK

Hmmm what speed CPU you got? Curious if you could run a test I could care less what voltage your running, but what 05 scores you get with 625/650?

[Nunyabiz]

Hmmm what speed CPU you got? Curious if you could run a test I could care less what voltage your running, but what 05 scores you get with 625/650?


I have an x24400 at 2.5 ghz. Not sure if I can underclock the memory, but I will try when I get home.

[deathman20]

I have an x24400 at 2.5 ghz. Not sure if I can underclock the memory, but I will try when I get home.

Cool thx.

Well at least with ATITool I with 625/650 @ 2.5Ghz 9010
OC I havn't tried at those exact clocks/voltages as my above one, I'd get around 8610.

Just curios if it loosened the settings up even if the ram can do well more then that with the correct voltage.

[Nunyabiz]

Cool thx.

Well at least with ATITool I with 625/650 @ 2.5Ghz 9010
OC I havn't tried at those exact clocks/voltages as my above one, I'd get around 8610.

Just curios if it loosened the settings up even if the ram can do well more then that with the correct voltage.


at 625/750 I get 9099

at 625/650 9038

[deathman20]

at 625/750 I get 9099

at 625/650 9038

Is one using OC tool and the other using ATI tool? Or both using OC tool?

Get nearly identical results as mine at the same speed.

[Nunyabiz]

Is one using OC tool and the other using ATI tool? Or both using OC tool?

Get nearly identical results as mine at the same speed.


at 625/750 with cat 511 i get 9109. That is stock settings for the XT, so i am not using any overclocking. ATI tool does not work with the XT (as i have said) so I have just set CCC to 690/800 which is the max of CCC, and saved settings.

at 690/800 9747 with cat 5.11

I had an 1800XL and I could not get it to xt speeds, so you have a really nice card.

[deathman20]

at 625/750 with cat 511 i get 9109. That is stock settings for the XT, so i am not using any overclocking. ATI tool does not work with the XT (as i have said) so I have just set CCC to 690/800 which is the max of CCC, and saved settings.

at 690/800 9747 with cat 5.11

I had an 1800XL and I could not get it to xt speeds, so you have a really nice card.

Wasn't sure if ATI tool would work with a downward clock. But thats intresting, at 625/650 I got a higher score then you did with 625/750 (not much but slight talking 9 points hehe). Wonder if that means stock settings it doesn't actually have the memory as tight as it could be?

But of course you can definatly clock higher then I can, still trying to figure out my card as we speak hehe.

[Nunyabiz]

Wasn't sure if ATI tool would work with a downward clock. But thats intresting, at 625/650 I got a higher score then you did with 625/750 (not much but slight talking 9 points hehe). Wonder if that means stock settings it doesn't actually have the memory as tight as it could be?

But of course you can definatly clock higher then I can, still trying to figure out my card as we speak hehe.


First off I did not use ATI tool, it does not work with the XT.

...........your score __________ my score

625/650 9010 _______________ 9038
625/750 ___________________ 9109

So I dont see how you scored higher than me, are you using cat 5.11?

[deathman20]

625/650 scored 9114-9118 with 2.6Ghz. Overall seems pretty much inline, just something in the background seems to be eating up cycles since they preform almost identical at the same speed at least with you using OC. Makes me wonder if it changes the timings on the fly then, seems really odd going from 650-750 yielded barely no score difference.

Using 5.11 (not the b version)

But its odd I'm getting so close to your scores with my CPU at the same speed, I'd of figured it would of been higher.

I mean having it at 625/750 should raise your score quiet a bit.

Was doing some tests.... Gained nearly 800 points going from 500Mhz mem to 600Mhz. Guessing you'd see similar findings with your card, just seems very odd only getting another 70 points out of her for such a large clock difference, expecially since its stock speed also.

[Nunyabiz]

625/650 scored 9114-9118 with 2.6Ghz. Overall seems pretty much inline, just something in the background seems to be eating up cycles since they preform almost identical at the same speed at least with you using OC. Makes me wonder if it changes the timings on the fly then, seems really odd going from 650-750 yielded barely no score difference.


yes,Its probably because overclock tool lowers the mem timings even when I underclock the memory. It will be interesting when ATI tool is working with the XT.

Was doing some tests.... Gained nearly 800 points going from 500Mhz mem to 600Mhz. Guessing you'd see similar findings with your card, just seems very odd only getting another 70 points out of her for such a large clock difference, expecially since its stock speed also.

Must be something to do with the bandwidth limit affecting 3dmark. What score increase do you see going 600-650 on the mem? (400 points or less?)

[deathman20]

Must be something to do with the bandwidth limit affecting 3dmark. What score increase do you see going 600-650 on the mem? (400 points or less?)

I'll have to double check my results with that one, think it was only 300points but im not sure if I upped my core as well when I did that. All my paperwork is at home so gotta wait til then.

[nachthymnen]

When it's ready for downloading?
The date was not 30th of November?

[Diverge]

seems really odd going from 650-750 yielded barely no score difference.

I mean having it at 625/750 should raise your score quiet a bit.

Was doing some tests.... Gained nearly 800 points going from 500Mhz mem to 600Mhz. Guessing you'd see similar findings with your card, just seems very odd only getting another 70 points out of her for such a large clock difference, expecially since its stock speed also.

Yeah, i agree, it does seem odd that going from 650-750 yielded so little points.

Here some of my data if you guys want to compare:

->Asrock MB<-
omega (5/10a) - 7033 (stock gpu/mem)(cpu2.2ghz - opty 146)
ati(5/11) - 7048 (stock gpu/mem)(cpu2.2ghz - opty 146)
ati(5/11) - 7314 (546.75/mem)(cpu2.2ghz - opty 146)
ati(5/11) - 7221 (546.75/549)(cpu2.2ghz - opty 146)

->DFI nF4 eXpert MB<-
ati(5/11) - 7326 (stock gpu/mem)(cpu2.7ghz - opty 146)
ati(5/11) - 7369 (stock gpu/mem)(cpu2.7ghz - opty 170)
ati(5/11) - 7599 (546.75/549)(cpu2.7ghz - opty 170)
ati(5/11) - 7866 (573.75/576)(cpu2.7ghz - opty 170)
ati(5/11) - 7652 (547/648)(cpu2.0ghz / ram 200mhz - opty 170)
ati(5/11) - 8119 (573.75/648)(cpu2.7ghz / ram 180mhz - opty 170)
ati(5/11) - 8104 (560.25/558.00)(1.100V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9
ati(5/11) - 8177 (560.25/571.50)(1.100V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 64.9°C
ati(5/11) - 8219 (560.25/580.50)(1.100V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 67.1°C
ati(5/11) - 8257 (560.25/589.50)(1.100V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 66.6°C
ati(5/11) - 8297 (560.25/598.50)(1.100V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 65.8°C
ati(5/11) - 8363 (560.25/612.00)(1.100V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 64.8°C
ati(5/11) - 8384 (560.25/621.00)(1.100V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 67.8°C

->DFI nF4 eXpert MB<- w/cover off + 120mm blowing down on copper core HS - tightend core HS backplate screws, 2 loose

ati(5/11) - 8405 (560.25/621.00)(1.100V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 50°C/63.1°C
ati(5/11) - 8443 (560.25/630.00)(1.100V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 50°C/63.3°C
ati(5/11) - 8489 (569.70/630.00)(1.100V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 50°C/63.0°C
ati(5/11) - 8646 (580.50/630.00)(1.100V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 50°C/63.3°C
ati(5/11) - 8656 (589.50/630.00)(1.100V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 50°C/63.3°C
ati(5/11) - 8810 (600.75/630.00)(1.125V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 50°C/64.9°C
ati(5/11) - 8791 (610.20/630.00)(1.125V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 50°C/64.8°C
ati(5/11) - 8895 (621.00/630.00)(1.150V,1.905V,1.905V)(cpu2.5ghz / ram 250mhz - opty 170) - AtiTool0.25B9 - 50°C/64.4°C
ati(5/11) - 8848 (621.00/630.00)(1.150V,1.905V,1.905V)(cpu2.7ghz / ram 180mhz - opty 170) - AtiTool0.25B9 - 50°C/68.3°C (no fan ctrl)
ati(5/11) - 8981 (621.00/630.00)(1.150V,1.905V,1.905V)(cpu2.7ghz / ram 193mhz - opty 170) - AtiTool0.25B9 - 50°C/66.5°C
ati(5/11) - 8935 (621.00/643.50)(1.150V,1.916V,1.916V)(cpu2.7ghz / ram 193mhz - opty 170) - AtiTool0.25B9 - 50°C/66.0°C (fan 100%)
ati(5/11) - 8983 (621.00/630.00)(1.150V,1.905V,1.905V)(cpu2.7ghz / ram 193mhz - opty 170) - AtiTool0.25B9 - 50°C/66.3°C
ati(5/11) - 9027 (630.00/630.00)(1.200V,1.905V,1.905V)(cpu2.7ghz / ram 193mhz - opty 170) - AtiTool0.25B9 - 52°C/70.9°C
ati(5/11) - 9143 (641.25/630.00)(1.200V,1.905V,1.905V)(cpu2.7ghz / ram 193mhz - opty 170) - AtiTool0.25B9 - 52°C/71.5°C
ati(5/11) - 9193 (641.25/643.50)(1.200V,1.922V,1.922V)(cpu2.7ghz / ram 193mhz - opty 170) - AtiTool0.25B9 - 52°C/71.5°C
ati(5/11) - 9219 (643.50/643.50)(1.200V,1.922V,1.922V)(cpu2.7ghz / ram 193mhz - opty 170) - AtiTool0.25B9 - 52°C/69.6°C
ati(5/11) - 9243 (643.50/643.50)(1.200V,1.922V,1.922V)(cpu2.7ghz / ram 193mhz - opty 170) - AtiTool0.25B9 - 52°C/72.1°C

[Nunyabiz]

When it's ready for downloading?
The date was not 30th of November?

Last I heard, due to other commitments, it has been delayed until DEC 5.

[nachthymnen]

Last I heard, due to other commitments, it has been delayed until DEC 5.

Azz :(
Ok...just a couple of days to wait :)
TKS

[Nunyabiz]

Azz :(
Ok...just a couple of days to wait :)
TKS


Just released a release candidate lol.
get it HERE (http://www.guru3d.com/index.php?page=rivatuner&menu=8)

[spajdr]

useless program for us ati guys, no?

[deathman20]

Wondering myself whos tried it? I got it downloaded but of course gotta wait til I get home.

[spajdr]

Wondering myself whos tried it? I got it downloaded but of course gotta wait til I get home.

Well .. but why? you can overclock, but you cant change voltage.
It have nothing interesting compared to ati tool..

[Hicks]

Hhaahaha, doesn't work. So we still haven't got a overclocking program. ATI need to release one. :rolleyes:

[deathman20]

Well .. but why? you can overclock, but you cant change voltage.
It have nothing interesting compared to ati tool..

Well its always cool to try out other programs but of course, gave up looking at it for a while wonder what the hell half the settings where lol. Then quickly uninstalled it, deleted it, like it was never there.

[Hicks]

Will X1800's be fixed with an update? I mean them not working, is a bit lame.