VOGONS


Duke Nukem 3D 3DFX Voodoo 3 Patch (2026)

Topic actions

Reply 20 of 24, by NeoG_

User metadata
Rank Oldbie
Rank
Oldbie

I am kind of curious how the glide API fits in with column based renderers, because clearly the world still has the 2.5D representation on the CPU side with vertical shearing effects. Does it treat each column as a pair of triangles and convert the texture co-ordinates?

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 21 of 24, by BitWrangler

User metadata
Rank l33t++
Rank
l33t++
jh80 wrote on Today, 05:26:
BitWrangler wrote on Yesterday, 14:25:

I don't get why anyone would put a V3 in anything slow enough to not run Duke at 800x600 well on a 2D card. It only takes a P166 or so and VBE 2.0 card.

While I get the point you're making... I don't think this statement is accurate at all. Can you confirm? Even on a P200 MMX I probably only get 20-30 fps at 800x600 on Duke3d. If you want to play at anything like 60 fps you need a much faster CPU. So, it is possible that someone may have a period-accurate Voodoo 3 in a system that otherwise could not run Duke3d at 60 fps in 800x600.

I am sorry I didn't specify that it didn't meet the arbitrary post year 2000 FPS standard. 1990-1999 if it did 15+ FPS it was playing well.

Anyway, wouldn't be having silly arguments if it was clearly stated what things actually achieve when you release them instead of us having to apply the subtext "Here's a piece of random AI generated crap I am not even sure what it does" because that's what it sounds like when details are withheld.

Edit:Hmmm do code box edits show as edit? because I swear there's more details now in first post than there was.

Unicorn herding operations are proceeding, but all the totes of hens teeth and barrels of rocking horse poop give them plenty of hiding spots.

Reply 22 of 24, by feipoa

User metadata
Rank l33t++
Rank
l33t++
BitWrangler wrote on Today, 12:51:

1990-1999 if it did 15+ FPS it was playing well.

Are you guys aiming for 60 fps on vintage DOS games? On my hyper 486's, I get average 17 fps in Duke Nukem 3D with sound enabled (640x480). It feels good enough for me. My kids can't stop playing it and never said anything about it feeling slow. Neither myself, nor my children, have any experience with modern day action games, so we aren't expecting life-like movement.

My software mode Duke Nukem 3D benchmark results are here, Re: The Ultimate 486 Benchmark Comparison
Anyone know if this Duke3D benchmark will work with the Voodoo3 patch?

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

Reply 23 of 24, by BaronSFel001

User metadata
Rank Member
Rank
Member
TgamesFR wrote on Yesterday, 09:33:

For others games i will concentrate maintly on Voodoo 1 exclusives games.
My goal is to make the Voodoo 3 the 100% compatibility card over every 3DFX patches.
And also support few "high-spec" games who need the power of the Voodoo 3 to run correctly (like Duke Nukem 3D and Screamer).

Very interesting, as this happens to be while I still contemplate the merits of whether to keep my Voodoo3 or Voodoo2 SLI.

If you can make EF2000 work on Voodoo3 that will pretty much settle it: I get one more precious PCI slot, and the SLI setup will sell for more anyway.

System 20: PIII 600, LAPC-I, MK1869 Xtreme, Voodoo3, SQ2500, R200, 3.0-Me
System 21: G2030 3.0, X-fi Fatal1ty, GTX 560, XP-Vista
Retro gaming (among other subjects): https://baronsfel001.wixsite.com/my-site

Reply 24 of 24, by jh80

User metadata
Rank Member
Rank
Member
feipoa wrote on Today, 17:16:

Are you guys aiming for 60 fps on vintage DOS games? On my hyper 486's, I get average 17 fps in Duke Nukem 3D with sound enabled (640x480). It feels good enough for me. My kids can't stop playing it and never said anything about it feeling slow. Neither myself, nor my children, have any experience with modern day action games, so we aren't expecting life-like movement.

My software mode Duke Nukem 3D benchmark results are here, Re: The Ultimate 486 Benchmark Comparison
Anyone know if this Duke3D benchmark will work with the Voodoo3 patch?

As someone who played Duke3d quite a lot on a 486 when it came out, 17 fps is rather unbearable. Did you have your kids compare with 320x200?

Of course people tolerated low fps back in the day. Go back to 1989 and play Mechwarrior and you'll be satisfied with 5 fps.

Once games like Quake and Descent came out, and with online play, there was certainly more discussion about sufficient frame rate. You can read all of this discussion from 1996 still on Usenet. For Duke3d, I see a lot of Usenet comments suggesting 25-3o fps minimum is ideal.

Once 3D hardware started taking off in 1997 and gaming benchmarks started becoming more common alongside sites like Anandtech, then the push for 60 fps really entered the industry consciousness.

But I think you'd be hard-pressed to find a serious Duke3d player from 1996 who preferred 17 fps 640x480 vs. 60 fps 320x200. The game is simply much harder to play at low fps.