VOGONS


First post, by Tek

User metadata
Rank Newbie
Rank
Newbie

Link to the video: https://www.youtube.com/watch?v=cLFad5qiB3o

Hi guys, another post about my excellent retro PC. This machine was built over six months ago, with a heavy amount of help from this forum. You can see my original thread here if you're inclined. This time around I set about the tricky task of benchmarking the cards and CPU!

I think my Voodoo 2 cards are coming up as 4mb cards though - anyone have any thoughts about that? I'm certain they're 12mb cards. VOGONS helped me to find a huuuge list of programs but I didn't recognise all of them. To me, the obvious go-tos were the ones I recognised from back in my day. Anyway, I hope you enjoy the video guys.

Resources:
VOGONS Benchmark archive?
http://www.benchmarkhq.ru/be_video.html
http://www.roylongbottom.org.uk/oldones.htm
https://dosbenchmark.wordpress.com/
http://www.futuremark.com/benchmarks

We'll karaoke all night long, macarena 'til the break of dawn.

Reply 3 of 5, by obobskivich

User metadata
Rank l33t
Rank
l33t
2fort5r wrote:

I think 3D Mark ignores the Voodoo and just tests the 3D card it's connected to?

It depends on which version of 3DMark, and how you configure it (you will have to select the Voodoo), and what drivers the Voodoo2 is using (if they support DirectX or not). In Windows 9x, the V2 drivers support DirectX, and the card will run 3DMark99 and 3DMark00 reasonably well for its age; it can run most of 3DMark01 at lower resolutions, but its pretty awful (especially if you're paired up with an a "era appropriate" CPU, like the P2 here, as 3DMark01 is very CPU dependent)). In Windows 2000 the official drivers don't support DirectX, so only Glide and OpenGL applications can be run - 3DMark requires DirectX. I've never personally had good luck with the mod-drivers that try to implement DX support in 2000+ (usually built-up from the 3dfx beta drivers) for Voodoo2, but they're out there, and ostensibly someone has gotten them to work.

Voodoo2 doesn't require a 3D card to be connected either - it can be the system's sole 3D acceleration, as long as there's a 2D card for non-3D tasks. The system here, however, has 3D available through both the Riva and the Voodoo2 SLI configuration.

Some points on the linked videos:

- Voodoo2 are not AGP.
- Voodoo2, even in SLI, will not achieve "full HD" (1920x1080) - they're limited to 1024x768. The 1280x960 (which is not "full HD") is almost certainly running on the Riva as you've selected the default OpenGL driver (e.g. thru the nVidia). The Half-Life menu actually tells you what you need to do to enable the Voodoo2 configuration.
- Hardware bump-mapping is indeed not supported on Voodoo2.

Finally, what makes you (Tek) say they're only being recognized as 4MB cards?

Reply 4 of 5, by Tek

User metadata
Rank Newbie
Rank
Newbie
obobskivich wrote:

Finally, what makes you (Tek) say they're only being recognized as 4MB cards?

In the menu in 3DMark, it seemed to say I had 8mb of VRAM, where I would have assumed I'd see 24mb?

We'll karaoke all night long, macarena 'til the break of dawn.

Reply 5 of 5, by havli

User metadata
Rank Oldbie
Rank
Oldbie

8 MB is correct for V2 12MB SLI. 3Dmark only recognizes the framebuffer memory which is 4MB for each V2, so 8 MB total.
Single Voodoo2 12MB has 4MB framebuffer + 8 MB texture memory - split to 2x 4MB (each TMU has its own dedicated RAM).
SLI only add up the framebuffer, texture RAM contains duplicate data... in total there is 8MB FB + 4MB TEX effective VRAM.

HW museum.cz - my collection of PC hardware