Voodoo2 + GLQuake image corruption \ VOGONS

Voodoo2 + GLQuake image corruption

Topic actions

First post, by feipoa

Posted on 2015-10-09, 07:01

feipoa Offline

Rank l33t++

Rank: l33t++
Posts: 10298
Joined: 2011-03-07, 13:54
Location: Canada

After about 40 minutes of running GLQuake in autoplay mode (that is, enter the game and don't press any keys, the game plays by itself), I start to see some lack of detail in the background images. I am inclined to refer to this as image corruption, however this phenomenum might have a more appropriate term. Refer to the attached images.

I believe my Voodoo2 is the STB variety. It has 12 MB of RAM and 100 MHz memory chips. Does anyone know what is causing this and if there is any means to correct for it? The image corruption only happens with Win95c. When I boot into NT4, I tested GLQuake in autoplay mode for 75 minutes without any evidence of this image corruption, which makes be beleive the issue may be a Win95c instability w.r.t. hardware temperature. Can the Voodoo2 run too hot? Has anyone witness this before, if so, how did you correct it? Are there some Glide settings I should adjust?

For Win95c, I am using driver v3.03.00. MiniGL version is 1.46.
For WinNT4, I am using driver v3.02.02. MiniGL version is 1.46.

The attachment Voodoo2_GLQuake_Corruption_2.jpg is no longer available

The attachment Voodoo2_GLQuake_Corruption_1.jpg is no longer available

EDIT: There is one newer 3dfx driver version for Win95, however it requires DirectX 7, which I do not want to install.

Plan your life wisely, you'll be dead before you know it.

Reply 1 of 1, by idspispopd

Posted on 2015-10-15, 11:57

idspispopd Offline

Rank Oldbie

Rank: Oldbie
Posts: 1213
Joined: 2012-02-15, 21:08
Location: Hamburg / Germany

I see dropped textures (only the models seem to be textured, but that's hard to see), but I think there also other errors like the checkerboard pattern.
Voodoo2 can very well overheat when used with a faster CPU.
You could enhance the cooling (use a fan or slap on heat sinks). It might also help to use VSync (if the frame rates are above 60fps that is), maybe that is already active in NT so you don't see the problem there.
I don't think it's a driver issue.

Go to top of page Go to top of page

Back to General Old Hardware