VOGONS


First post, by sepooq

User metadata
Rank Newbie
Rank
Newbie

Hello! I'm currently corresponding with a seller that has Voodoo2 12MB to offer. Card seems to be working without issues on Quake, NFSII:SE, 3dMark99 and 3dMark2000. I asked to perform one last test running donut demo from fastvoodoo package and while the donut itself seems to be free of visible issues, the first scene - 'donut' writing is putting out some weird artifacts. They seem to be appearing suddenly for a couple of seconds.
I'm not sure if this might be a driver or hardware issue.

Drivers: v2-w9x-3.02.02 + FastVoodoo2 4.6 (on Windows98)
PC Spec: ABit SA6, 384MB RAM, Pentium III 1GHz (133MHz)

Anyone able to help diagnose?

Donut video (artifacts 0:02 - 0:09, 0:34 - 0:42, 0:44 - 0:48): https://youtu.be/xQTmvFTNb8U
6030 video (no artifacts): https://youtu.be/J5u5C7qqyyw

Reply 1 of 5, by sepooq

User metadata
Rank Newbie
Rank
Newbie

I think this test was performed on FastVoodoo2. Not sure if the same is happening on reference drivers. Will try to confirm.

Reply 2 of 5, by Shagittarius

User metadata
Rank Oldbie
Rank
Oldbie

FastVoodoo is garbage. It really only works error free on the most popular titles and benchmarks. Everything else it will barf all over. Just use the final official release.

Reply 3 of 5, by Postman5

User metadata
Rank Member
Rank
Member

The donut is covered in artifacts. This clearly indicates problems with the TMU's connections to the memory.

Reply 4 of 5, by Lostdotfish

User metadata
Rank Member
Rank
Member
Shagittarius wrote on 2025-03-20, 17:44:

FastVoodoo is garbage. It really only works error free on the most popular titles and benchmarks. Everything else it will barf all over. Just use the final official release.

this - test with the stock driver and report back

Reply 5 of 5, by sepooq

User metadata
Rank Newbie
Rank
Newbie

We tried reference drivers and did more detailed inspection of what's going on. Turns out that, in fact, switching between TMUs causes artifacts to show up and go away. Unreal (as a game that utilizes both TMUs) also shows issues.
So now it seems to be about identifying potential cause for TMU-memory issue.
The photos I currently have may be too blurry upon zooming in. I'll ask if it's possible to get something better. In the meantime I'll investigate these and also post them here hoping that someone's eye might catch some hint.

I've never done the "mojo.exe" thing but I will also look up the instructions as I'm guessing this might provide a helpful insight.