VOGONS


First post, by Bohemond1099

User metadata
Rank Newbie
Rank
Newbie

So I got my Voodoo 5 5500 PCI installed on my PIII 1Ghz/384MB RAM W98SE machine and it seems to run ok; but when I run 3dmark 2000 two tests fail and the first one is the CPU portion; 3d Mark2000 shows a red "benchmark cannot be run" message and moves on to the next portion of the benchmark. Anyone one have any idea what could be causing this? I tried setting the 3dFX control panel to DirectX and Glide alternatively, but that did not help.

Reply 1 of 7, by Bohemond1099

User metadata
Rank Newbie
Rank
Newbie

Update with what I find to be some interesting results; some reeaaly sluggish performance out of the Voodoo 5 55oo PCI; so thought I'd pop in my Voodoo 3 3000 AGP and see how the smoothness compared. It's night and day; even with lower average FPS the Voodoo 3 3000 is a smooth experience vs the stop motion the V5 5500 PCI gets in Unreal/Delta Force/Quake 3 (though interestingly Quake II and Dark Forces 2: Jedi Knight run great on the Voodoo 5 PCI). The constant slow downs I got in Delta Force, Quake III, and Unreal are gone. Thought I would post the results as well to see if anyone 99knows if this is the card or something else going on.

Attachments

  • V5 vs V3 Q3 TD2.JPG
    Filename
    V5 vs V3 Q3 TD2.JPG
    File size
    75.48 KiB
    Views
    673 views
    File comment
    Quake III TD2
    File license
    Fair use/fair dealing exception
  • V5 vs V3 Q3 TD1.JPG
    Filename
    V5 vs V3 Q3 TD1.JPG
    File size
    83.27 KiB
    Views
    673 views
    File comment
    Quake III TD1
    File license
    Fair use/fair dealing exception
  • V5 vs V3 3DMK99.JPG
    Filename
    V5 vs V3 3DMK99.JPG
    File size
    61.87 KiB
    Views
    673 views
    File comment
    3DMark 99
    File license
    Fair use/fair dealing exception
  • V5 vs V3 3DMK00.JPG
    Filename
    V5 vs V3 3DMK00.JPG
    File size
    68.63 KiB
    Views
    673 views
    File comment
    3DMark 2000
    File license
    Fair use/fair dealing exception

Reply 2 of 7, by Shagittarius

User metadata
Rank Oldbie
Rank
Oldbie

Doesn't help with the PCI question except for maybe comparison, I get 5526 3dMarks in 3DMark2000 @ 1024x768x16 with a 5500AGP.

At 1024x768x32 I got 3989.

I just realized you are running a P3-1ghz. That could be your limiting factor right there.

Reply 3 of 7, by leonardo

User metadata
Rank Member
Rank
Member
Bohemond1099 wrote on 2022-02-28, 08:31:

So I got my Voodoo 5 5500 PCI installed on my PIII 1Ghz/384MB RAM W98SE machine and it seems to run ok; but when I run 3dmark 2000 two tests fail and the first one is the CPU portion; 3d Mark2000 shows a red "benchmark cannot be run" message and moves on to the next portion of the benchmark. Anyone one have any idea what could be causing this? I tried setting the 3dFX control panel to DirectX and Glide alternatively, but that did not help.

A lot depends on the absent details. Which version of DirectX are you using and which Voodoo drivers?

The PCI bus is constrained compared to AGP in certain ways - and you can wreak havoc on the bus with your BIOS settings as well as other devices. What chipset does your motherboard utilise? ViA and ALi were in many cases known to be finicky with a variety of different cards. In the early PIII days everyone preferred Intel's i440BX, even over the later i820-series in many cases...

So many open questions!

[Install Win95 like you were born in 1985!] on systems like this or this.

Reply 4 of 7, by Bohemond1099

User metadata
Rank Newbie
Rank
Newbie
leonardo wrote on 2022-03-10, 23:09:
A lot depends on the absent details. Which version of DirectX are you using and which Voodoo drivers? […]
Show full quote
Bohemond1099 wrote on 2022-02-28, 08:31:

So I got my Voodoo 5 5500 PCI installed on my PIII 1Ghz/384MB RAM W98SE machine and it seems to run ok; but when I run 3dmark 2000 two tests fail and the first one is the CPU portion; 3d Mark2000 shows a red "benchmark cannot be run" message and moves on to the next portion of the benchmark. Anyone one have any idea what could be causing this? I tried setting the 3dFX control panel to DirectX and Glide alternatively, but that did not help.

A lot depends on the absent details. Which version of DirectX are you using and which Voodoo drivers?

The PCI bus is constrained compared to AGP in certain ways - and you can wreak havoc on the bus with your BIOS settings as well as other devices. What chipset does your motherboard utilise? ViA and ALi were in many cases known to be finicky with a variety of different cards. In the early PIII days everyone preferred Intel's i440BX, even over the later i820-series in many cases...

So many open questions!

Just using the latest driver posted on Phils Computer lab for each card (V3 and V5); I tried those third party drivers and they never worked for me at all. Ok, will have a look at the Bios, thanks.

Reply 5 of 7, by Bohemond1099

User metadata
Rank Newbie
Rank
Newbie

Ok got an update; I FINALLY got the Voodoo 5 to work with Amigamerlin drivers on my QX6700 system with Windows XP 32bit; could not get the Vcontrol utility to install though; exe just pops up real fast and then disappears without installing anything.

QX6700 demo1 32bit.JPG
Filename
QX6700 demo1 32bit.JPG
File size
78.83 KiB
Views
623 views
File license
CC-BY-4.0
QX6700 demo1 16bit.JPG
Filename
QX6700 demo1 16bit.JPG
File size
92.53 KiB
Views
623 views
File license
CC-BY-4.0
QX6700 demo 2 32bit.JPG
Filename
QX6700 demo 2 32bit.JPG
File size
83.82 KiB
Views
619 views
File license
CC-BY-4.0
QX6700 demo 2 16bit.JPG
Filename
QX6700 demo 2 16bit.JPG
File size
90.62 KiB
Views
619 views
File license
CC-BY-4.0
1. Quake III combined average.JPG
Filename
1. Quake III combined average.JPG
File size
111.92 KiB
Views
616 views
File license
CC-BY-4.0

Reply 6 of 7, by Bohemond1099

User metadata
Rank Newbie
Rank
Newbie

Really too bad those AmigaMerlin drivers (3.1) only worked with Idtech games; would not run any DX8 games at all. Attempted the SFFT or whatever drivers; big mistake as usual; the previous Amiga was an unuseable mess that either crashed instantly or shot out polygons everywhere...so bad.