Article View: alt.games.duke3d
Article #317Re: 486 frame rates
From: loxx... CHUE C LO
Date: Mon, 08 Apr 1996 00:00
Date: Mon, 08 Apr 1996 00:00
23 lines
1660 bytes
1660 bytes
ato...@pe.net (David Moore) writes: >In article <4k4ql7$e...@jaxnet.jaxnet.com>, > sha...@jax.jaxnet.com (Shawn) wrote: >>: I have a 486DX2-66, with an 1 Meg video card, and I see no >>: slowdowns anywhere... Runs faster than doom or doom2 did/does >>: on the same system. >> >>Try running it with 800 X 600 screen pitch & watch it crawl. >> >Why? What's the point, really? Anything more than 640X480 is pointless, >anyway, at this point the game is already beautiful and anything higher is >just gobbling up proccesor power. I suppose if you wasted money on an >obsolete-in-a-second pentium you might feel a little better knowing you could >run Duke at 800X600, but other than that who gives a crap? The game is great, >even in 320X200. It's the GAME that makes the game great, not the graphics. I believe he was responding to the prior post in regard to the speed and power of the DX2-66 with the 1 mb videocard. I personally don't know how he could get a better framerate in Duke3d versus Doom2. Doom2 runs almost too fast for my system, whereas duke3d only gets around 30 framerate in vga, and less in svga modes.
Technical Details
Message-ID:
<4ka75n$rdi@epx.cis.umn.edu>Path:
mbox-mo1.pugleaf.net!unknown!not-for-mailReferences:
<4iqio9$pbk@ccnet2.ccnet.com> <4ja9lf$n7a@news.wco.com> <4jbg1f$17oi@mercury.cc.uottawa.ca> <4jpfp3$9do@news.tamu.edu> <4k4ql7$emo@jaxnet.jaxnet.com> <4k51t9$7em@nfs1.pe.net>Show Full Headers
Complete Article Headers
From: loxx...@itlabs.umn.edu (CHUE C LO) Subject: Re: 486 frame rates Date: 1996/04/08 Message-ID: <4ka75n$rdi@epx.cis.umn.edu> X-Deja-AN: 146379671 references: <4iqio9$pbk@ccnet2.ccnet.com> <4ja9lf$n7a@news.wco.com> <4jbg1f$17oi@mercury.cc.uottawa.ca> <4jpfp3$9do@news.tamu.edu> <4k4ql7$emo@jaxnet.jaxnet.com> <4k51t9$7em@nfs1.pe.net> organization: University of Minnesota newsgroups: alt.games.duke3d MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit