0.25 Beta 10

[Flashnc]

hey w1zzard....im getting pretty much the same as others...still using manual settings to oc.....but....


the DPI issue is fixed.........good work so far.


dont have a clue how you created this program, but you are one awsume dude at what you do for us in the OC community..

"may you walk in sunshine-
and be blessed,
to never have holes in your underware"...

flash

[ugp]

Any clocks get me black screen when I go to benchmark... Using OverClocker with the same clocks on the core I do fine...

I have a x1800XT at 702/800 so far... and going... Stock Cooler

[KrisMCool]

Good news is that beta 10 installs and runs fine on WinXP 64 now. Thanks. Bad news is that reference divider and minimum step are all jacked up. Divider shows 2, 4 or 12, depending on its mood. Min step shows -21474836.48 MHz. I'm using a clock-modified BIOS, if it makes a difference, but these numbers were always correct before. Is there a way to manually input these numbers?

[ITPaladin]

I couldn't find a feature request section so I thought I would ask to add in an always on top and a sound choice feature.
I sometimes hear the default Windows "boop" that you hear when you click on the system tray sound icon and then click on the volume slider that pops up.
If that sound is supposed to be an artifact notice, then it is confusing.
I would like the option to have a file of my choice to play or some better sound and a preview button before applying it.

[Super XP]

With my X800XL & my Windows XP Pro x64 OS, the beta 10 is now wroking great. I can restart with no problems. I can also turn off ATI Tool & restart it with no prob's.

Great work Wizzard

Wizzard, I think ATI will hire you in an instant. I mean, if you can fix there CCC drivers, which I am sure you can, can you imagine

[M Diddy]

Just curious, what Amps are you guys running when OC'ed??? I'm at 16.4 on my OC profile... Is that a little high???

[M Diddy]

Also, what kind of FPS do you guys score in 3dM05????

[Super XP]

All are on Default Setting. w/ Cat 5.11b drivers.

3D Mark 2001 = 28,732
3D Mark 2003 = 13,152
3D Mark 2005 = 6,016

Aquamark 3 = 82,365
GFX = 12,006
CPU = 13,110

Everest Home Edition (DDR Tests):
Memory Read : 7767 MB/s
Memory Write : 3024 MB/s
Memory Latency : 34.1 ns

[M Diddy]

Well this was wierd... My GPU is clocked to 625 and here's what happens with various RAM speeds in 3DM05:

650 MHZ = 7860 3dmark
660 MHZ = 7729 3dmark
670 MHZ = 7716 3dmark

What the hell gives??? Why would they get lower as RAM speed increases????

[mR Yellow]

Originally Posted by M Diddy

Well this was wierd... My GPU is clocked to 625 and here's what happens with various RAM speeds in 3DM05:

650 MHZ = 7860 3dmark
660 MHZ = 7729 3dmark
670 MHZ = 7716 3dmark

What the hell gives??? Why would they get lower as RAM speed increases????

M Diddy, u score seems a bit low for a 1800XL. I get 9200 @ 650/650.

[Super XP]

Originally Posted by M Diddy

Well this was wierd... My GPU is clocked to 625 and here's what happens with various RAM speeds in 3DM05:

650 MHZ = 7860 3dmark
660 MHZ = 7729 3dmark
670 MHZ = 7716 3dmark

What the hell gives??? Why would they get lower as RAM speed increases????

The only thing I see is that your RAM is getting hot, so try placing a FAN in front of your DDR Ram.

[NT78stonewobble]

Now running 0.25 beta 10

Still crashes on too high oc. But as said x800's do that...

Now I've read through all of the beta posts and got a little confused.

With this beta what artifact scanning method am I sposed to use for the x800xt?

Haven't checked if the boot problem is still there (It was mysteriously absent this morning when I started my pc with the beta 9's, first time it worked normally with those installed ).

Will report back in if I see any problems resuming or booting.

[mR Yellow]

Originally Posted by NT78stonewobble

Now running 0.25 beta 10

Still crashes on too high oc. But as said x800's do that...

Now I've read through all of the beta posts and got a little confused.

With this beta what artifact scanning method am I sposed to use for the x800xt?

Haven't checked if the boot problem is still there (It was mysteriously absent this morning when I started my pc with the beta 9's, first time it worked normally with those installed ).

Will report back in if I see any problems resuming or booting.

The artifact error is only with the new x1800 series.

[W1zzard]

Originally Posted by ITPaladin

I couldn't find a feature request section so I thought I would ask to add in an always on top and a sound choice feature.
I sometimes hear the default Windows "boop" that you hear when you click on the system tray sound icon and then click on the volume slider that pops up.
If that sound is supposed to be an artifact notice, then it is confusing.
I would like the option to have a file of my choice to play or some better sound and a preview button before applying it.

there is a setting "play sound when artifact detected"

[W1zzard]

Originally Posted by KrisMCool

Good news is that beta 10 installs and runs fine on WinXP 64 now. Thanks. Bad news is that reference divider and minimum step are all jacked up. Divider shows 2, 4 or 12, depending on its mood. Min step shows -21474836.48 MHz. I'm using a clock-modified BIOS, if it makes a difference, but these numbers were always correct before. Is there a way to manually input these numbers?

argh .. forgot to fix this for the x1000 series
the setting does not apply there

[W1zzard]

it is unknown to which voltage the amperage number is related to .. if it's vgpu, 40 amps isnt that much .. watts = ampere * volts

the 2d/3d clocks thing on the x1800xt is not fixed yet.. still digging for info

[W1zzard]

"use old scanning method" is best left at off for maximum heat generation, but if you are having some strange problems, try the old one too and see if it works better. the heat generated there might be a little less

anybody else can confirm old scanning method works good on x1800?

[mR Yellow]

Originally Posted by W1zzard

"use old scanning method" is best left at off for maximum heat generation, but if you are having some strange problems, try the old one too and see if it works better. the heat generated there might be a little less

anybody else can confirm old scanning method works good on x1800?

Well, the old method doesn't show yellow artifacts in 3dview...if that helps.
I just downloaded ATiTool (im at work) so i'll only give feedback tomorrow.

[OBR]

Bad news: i have the same problem like in 25.9beta, if i set frequency for GPU and MEM in Atitool (example: 700,800) atitool automatically set 2D default frequency and card is not overclocked, why i cant set 2D a 3D frequencies separately?

[W1zzard]

Originally Posted by OBR

Bad news: i have the same problem like in 25.9beta, if i set frequency for GPU and MEM in Atitool (example: 700,800) atitool automatically set 2D default frequency and card is not overclocked, why i cant set 2D a 3D frequencies separately?

because the programmer hasnt figured out yet how to do so

[mR Yellow]

Originally Posted by W1zzard

because the programmer hasnt figured out yet how to do so

lol

[Spider]

So the programmer also hasn't figured out how to disable 2d mode from find max core in nvidia cards? I've asked for that several times .

[atomicpineapple]

OBR, disable ATISmart and ATIHotkey Poller services, that stops clocks being taken back ot default when a 3d app is run.

[W1zzard]

Originally Posted by atomicpineapple

OBR, disable ATISmart and ATIHotkey Poller services, that stops clocks being taken back ot default when a 3d app is run.

thats some great info .. could you check if both have to disabled or one will be enough? will everything still work if the services are permanently disabled? or do you have to enable/disable them each session?

[atomicpineapple]

Both have to be disabled from the looks of things, this causes overdrive facilities to be lost, but i found that with both disabled it stops the card entering 3d mode (checked that by changing 3d clocks in the OC tool, no increase in 3d mark score or fps, changed 2d clocks and scores increased). Everything looks like it'll work with them permanently disabled, ie system wont crash. But that still leaves the problem of ATITool setting the clocks very low on exit from (and possibly during) a 3d application, somethingwhich doesnt happen with the OC tool with those 2 services disabled.