
Weakest PC Specs Able To Play Duke 3D
#1 Posted 29 June 2014 - 08:45 AM
This post has been edited by t800: 29 June 2014 - 09:58 AM
#2 Posted 29 June 2014 - 09:10 AM
Might take a couple of days, but I'm kinda curious myself so I think I'll give it a shot with an Intel 25MHz SX and possibly an older 386 box which uses a Cyrix 486DLC-40 but I have an AM386DX-40, can run either at 33MHz too on the Shuttle board I have. That has an ISA ET4000 in it, but I am unclear if I can get the game to start in it's puny 4MB of RAM, I really need to upgrade that.
I'd be willing to bet that the Am286-6MHz with it's Everex Viewpoint (EGA/VGA combo card) and 640K RAM isn't going to run it though...
This post has been edited by High Treason: 29 June 2014 - 09:14 AM
#3 Posted 29 June 2014 - 09:15 AM
Strangely enough, Quake would, but at literally 1FPS.
This post has been edited by Tea Monster: 29 June 2014 - 09:16 AM
#4 Posted 29 June 2014 - 09:22 AM
Can't resist... It's not here yet, but I wonder if this will run it;
Almost an entire 486 on a single chip at 66MHz, made by SGS Thomson (ST) - wonder if it's the same as the Cyrix 486 just like the regular SGS ones were of if they tweaked anything by the time they did this circa 1999.
#5 Posted 29 June 2014 - 09:29 AM
I'm pretty sure you'd need a pentium 100 with at least 20mb of ram to run it smoothly at 640*480 at high video settings; which is the minimum for comfortable gameplay.
This post has been edited by MetHy: 29 June 2014 - 09:29 AM
#6 Posted 29 June 2014 - 09:49 AM
This post has been edited by MusicallyInspired: 29 June 2014 - 09:50 AM
#7 Posted 29 June 2014 - 10:06 AM

We ran multiplayer in my office on 486s with a good video card, I forgot the name for them. At home, Build ran best on this VESA mode, again on a 486 but with straight DOS 6.2/Windows 3.11, not much luck with Windows 95/98.
Thus I say, in DOS/Win3.1 with a 486, Duke ran half decent on 600x480, as soon you switched to Windows 95 and up, you needed the better computers, or frankly, a better port.
This post has been edited by Hank: 29 June 2014 - 10:51 AM
#8 Posted 29 June 2014 - 10:51 AM
It is not really playable, I can capture video from it if you want (direct from VGA just like that video I linked, no cameras pointed at screens) though I want to first try with a VESA 2.0 driver (SDD 7) and a few other adjustments such as disabling the audio and whatnot.
I don't think it's worth trying the 386 chip in this machine as the 486DLC is a 386 upgrade - essentially a 486 in a 386 socket so generally faster.
#9 Posted 29 June 2014 - 10:52 AM
I think there was a way in properties to tell the game to automatically do that, but It's been a while.
#10 Posted 29 June 2014 - 11:04 AM
High Treason, on 29 June 2014 - 09:22 AM, said:
The original BUILD source is completely integer-based.
#11 Posted 29 June 2014 - 12:05 PM
This post has been edited by The Angry Kiwi: 29 June 2014 - 12:10 PM
#12 Posted 29 June 2014 - 01:00 PM
Hendricks266, on 29 June 2014 - 11:04 AM, said:
#13 Posted 30 June 2014 - 02:08 PM
With an Intel 486 SX 25 and S3 Trio the frame rate ran at an average of 3-5 on full screen with all settings set to low, and at it's peak it rendered about 18 frames. (Hollywood Holocaust)
At the minimum size of the screen I got an average of 3-7 and a max of 22 frames. note that the max values had the camera pointed straight in to a wall.
Moving sectors (like exploding walls) and mirrors broke the fps though. To be honest, at least the first level is playable
Just for the heck of it I tried to boot up life's a beach and I think I got about 1 frame every 3 second in some places

Other than the cpu and video card, I really haven't looked up the specs on the stuff I'm using, but almost all the stuff I have came from discarded OEM computers, so I'm guessing it not top notch stuff.
In fact, probably garbage.
I have a Deskpro 386/20e, but at the moment I have no means to install Duke on that, not enough space and no CD drive, I don't want to crack it open to use other means.
The plastic front on that thing is disintegrating by itself, I have no idea if the previous owner threw something on it, but I've never seen that before, not at that extreme at least.
I'm just gonna leave it alone, or maybe I'll try and install Duke Shareware some other day.
#14 Posted 30 June 2014 - 02:17 PM
I mean, the minimum specs requirements that would be able to do that.
Is Blood the most demanding?
This post has been edited by MetHy: 30 June 2014 - 02:19 PM
#15 Posted 30 June 2014 - 04:40 PM
My Athlon 1500+ with a GeForce 4 MX440 still gets the odd lag spike at 1024x768 in Blood. I also think it's a bit quick for the ISA BUS as by that point the audio doesn't always work when you start the game - that machine is running an AWE 64 Gold. The others are running a Yamaha YM724 (P2) and probably a Vibra 16 (K6) but I am unsure on the last one as the K6 didn't like any card I tried to use with it and can't be bothered to look at it. I suspect the Pentium III might be a slightly faster platform for DOS games with the correct chipset, regardless of it's Windows performance.
All of these machines seem to run pretty much all Build games very well overall, of course, the K7 takes it. You would be able to upgrade that to an obscure revision of the 2600 on a slower BUS than most 2600+ chips had, but the chances of getting it working are slim and the chances of upgrading further are almost nil as you'd have to set up a newer motherboard lacking ISA, an bridge/adapter could be used but PCI lacks several functions relied on by the SoundBlaster and code that ran it... Some P3 boards still had an SB Link by that time which you could use with something like the Yamaha 724 though, but they would probably be hard to find. I have never seen an AMD board with that feature but they may have existed at some point.
SuperMicro made a Pentium 4 board with ISA slots, probably just on a bridge, but I do wonder how that would fare as a DOS rig. By that time CPUs weren't well optimized but the brute force of the chip might pull it through.
#16 Posted 30 June 2014 - 04:53 PM
#17 Posted 01 July 2014 - 03:23 AM
High Treason, on 30 June 2014 - 04:40 PM, said:
Ahcruna, on 30 June 2014 - 04:53 PM, said:
Ah, so one shouldn't go too retro to make an ultimate Build machine!
I remember I had a 500mhz computer (don't remember what exactly at all) which ran Duke3D smoothly at 800*600 so I thought something like that would be enough!
Anyway if I stumble upon something like on a flea market I might have a try, hoping the thing works. I'd a bit sick of having to use dosbox for Redneck Rampage Rides Again, Blood and Powerslave.
This post has been edited by MetHy: 01 July 2014 - 03:24 AM
#18 Posted 01 July 2014 - 01:42 PM
#19 Posted 01 July 2014 - 02:02 PM
Like it's been said before, you can run the games on stuff like DX4, 5x86's and up depending on the resolution.
I'm not sure how well my PIII run's the games at 1600 x 1200 because I have no screen that supports that resolution, but below that it all runs smooth.
Redneck Rampage can get some flickering at random moment ( I have no idea what causes it) but there is no slowdown when that happens.
Duke Nukem 3D, Blood and Shadow Warrior all run perfect through and through.
#20 Posted 06 July 2014 - 10:09 AM
Using an Athlon is like killing a fly with an atomic bomb.
#21 Posted 06 July 2014 - 12:51 PM
#22 Posted 08 July 2014 - 08:11 PM
The 386 looked pretty old so I doubt it had one.
#23 Posted 08 July 2014 - 08:49 PM
Corvin, on 08 July 2014 - 08:11 PM, said:
What kind of coprocessor? Certainly not floating-point.
#24 Posted 09 July 2014 - 10:31 AM
The thing is, these old machines got replaced at some point with then-modern PCs (Pentiums I suppose), which had Windows NT (maybe Windows 2000), but we would still often boot into DOS mode to do the stuff we were learning (the basics of C++ etc.). So maybe I'm confusing things and Doom and Duke3D were played already on the new machines (there's this comparison video, and as I remember Doom certainly ran a lot faster than what is shown for 386DX).
#25 Posted 09 July 2014 - 03:59 PM
#26 Posted 09 July 2014 - 04:36 PM
By the time Duke Nukem 3D was out, I had my Home LAN and faster machines, so we didn't play at work anymore. Ahh... the LAN Party years.

MrBlackCat
This post has been edited by MrBlackCat: 09 July 2014 - 04:38 PM
#27 Posted 10 July 2014 - 02:29 AM
But am I not mistaken here that I am beginning to think that using smallest screen view and low details have very negligible effect on overall performance or is just so that nobody had nerves back then to try it at such low graphical details?
#28 Posted 10 July 2014 - 03:19 AM
t800, on 10 July 2014 - 02:29 AM, said:
Oh no it made a huge difference. I could only play the game at details set to 'low'.
Then I remember some usermap that was laggy even then; and reducing the size of the screen helped a lot.
Man I must have really liked the game to play in such shitty conditions. Guess I must still really like it since I'm still here. One of the first things I did when we upgraded to a newer computer was to finally play Duke3D with good video settings.
#29 Posted 10 July 2014 - 06:11 AM
MrFlibble, on 09 July 2014 - 10:31 AM, said:
That sounds odd, yet very interesting. I've never seen any 386 play Duke Nukem 3D at a playable rate.
Like I mentioned before, I do have a 386 but it's slower than the 486SX 25mhz I tried Duke3D on. Not sure if it's even playable on that thing, but I could try to load up the shareware today.
Not getting my hopes up on it actually being playable though, hehe
[EDIT]
If it does run I can do a cellphone recording of it (oh, I don't have any sort of video capturing card).
This post has been edited by Ahcruna: 10 July 2014 - 06:17 AM
#30 Posted 10 July 2014 - 07:09 AM
Looked a lot like this, I couldn't find a pic to match the model I had.

This post has been edited by Drek: 10 July 2014 - 07:21 AM