3dmark 2000 score

[morphious]

hi, i just downloaded 3dmark 2000 and ran it in 800x600 (that the max my crappy monitor can do) and i got a score of 3506 on a
duron 800
256mb pc133
voodoo5
asus A7V
i was just wondeirng if this is a good score for my computer with everything set to default speeds. i am gonna try and overclock my vid card and see if that helps inprove it, also does anyone know which drivers i should use and can anyone help me configure 3dfx tools to give me the best preformince?

[morphious]

ok i just ran the test again with same settings in 800x600 16-bit with my voodoo overclocked 10mhz faster and i got a score of 3471, i'm gonna take it up another 10mhz. also when i was running the test it just exited for no reason. is that a bug or is it because my vid card is over clocked? i have never really experimented with overclocking before but i am gonna try and overclock it 20mhz faster then it is at factory with factory heatsinc and fan, is this a bad idea?

[morphious]

umm how come my score went down when i increased my vid card speed? i was watching most of the benchmark and i didn't notice any tearing or empty pixels during the test

[This message has been edited by morphious (edited 08-30-2001).]

[morphious]

ok i guess 186mhz is too much because my comp locked up half way threw the test so i have it at 172mhz wich is just 6mhz faster then default so i guess this will be fine. but can some one please tell me why my score went down when it was clocked 10mhz faster then default. it was runing fine, there was no tearing or missing pixels during 3dmark 2000. i think that my score isnt thast good because i have herd of people getting 5400 and up a while ago. this is 3dmark 2000 not 2001

[Todd a]

I actually got higher scores on my Voodoo3 2000 @166Mhz and a Duron 600 @900Mhz (just over 4000), but the Voodoo3 does not do true 32bit color. As for the dumping out. I had a K6-2 system that did that untill I upped the voltage from 2.2 to 2.4. As for the low scores when overclocking, it is likely getting timing errors of some sort that are not quite bad enough to crash it, but enough to cause slowdowns.

Man did 3DFX really screw up the Voodoo4/5. They should have stuck with the Voodoo3 core and added to it. Adding the 32bit and larger textures would have been fine. Switching to .18 micron instead of their crappy .25 micron metal proccess would have helped a lot. Left the 2 textures per pipeline and doubled the number of pipeline. Switched to DDR memory to handle the extra memory requirements and supported 32MB or memory. It would have pounded the GeForce256 DDR pretty bad. It would have had a fill rate around 1G-texel compared to the GeForces 480M-pixel. Screw anti-alasing (does anybody ever use this feature?) and all the wonderful Cinimatic effects that new go used.

They should have concentrated on the HSR. They say it was a CPU hog, but that just means that if you upgraded your CPU, your graphics card could offload some of the load back to the CPU to give you a nice performance boost instead of wasting CPU cycles, because your graphics card is holding you back.

------------------
The COMPUTER is your FRIEND!
Happiness is manditory.