Article View: alt.games.duke3d
Article #16Re: Duke Nukem is a WIMP
From: ITH... Christopher Arrowsmith
Date: Mon, 19 Feb 1996 00:00
Date: Mon, 19 Feb 1996 00:00
64 lines
3654 bytes
3654 bytes
In article <4g9gnq$j...@mozo.cc.purdue.edu>, bra...@ecn.purdue.edu (Branden Robinson) wrote: >an52...@anon.penet.fi wrote: > >: Someone said: >: My Opinion:DN3D is cool,but I think he looks stupid.His voice >: is dumb as hell too,they should have had a voice that sounded like >: Arny's,or maybe that guy on the Simpsons that sounds like Arny. >: Anyways a goofy voice would of made the game better. > >: And I AGREE ! I think Duke must be homosexual. He sure looks like a >: faggot, fresh from admiring himself after bodybuilding ! I find it >: hard to believe someone that looks as clean as that can be a hero. >: I Think 3drealms should give him a higher voice, something like >: 'ooh I'm so pretty, lick my love pump, big boy'... > >Why don't you bitch about something substantive, like: > 1) The music/sound setup can't autodetect DMA channels for shit > 2) The saved game thumbnails are corrupted 1/3 to 1/2 the time > 3) Game restores occasionally bomb right out of the program > 4) It likes to wegde machines HARD. As in locking up the keyboard beyond >all hope of a three-finger salute. Once I even crashed into some debug >code that blew my monitor into some half-assed 40x25 CGA text mode, rang >the speaker bell like it was a fire alarm, and dumped the processor >state to LPT1:, complete with the register contents. > >I guess these guys were so busy talking to their lawyers about how >"creating your own levels or reverse engineering the software" (i.e., >writing your own level editors, sound/graphics extraction and replacement >utilites, etc.) is "a violation of the vendor's rights" that they couldn't >be bothered to debug their software. Bullshit. Id let the kids run >hog wild with DOOM and they made a buttload of money. > >Mayhaps that's why Id and Apogee went their separate ways... > >Looks like a beta test to me. Once they work the bugs out, it should be >tolerable, though. > >One last word: DON'T TRY to run this game on a 486DX2/66. It must drop 75% >of the frames. You'll need a Pentium or one of those hopped-up >clock-ntupled AMD 486 chips to get any performance out of this thing. > >Followups trimmed to combat the 13-year old mindset. Not like it'll do any >good. > Sorry but IMHO you are talking CRAP. ND3D runs fine on a dx2 66 ,the graphics engine to do this must be bloody good but it is I even ran it in win95 and its fine. I get an average frame rate of about 15 on my dx2 this is fine and frames have only ever 'dropped' when the hard disk is used (this has happened to me twice so far). I've had no problem with with duke 3d sure theres the odd minor bug ( like when you blow up the cinema screen you get a glass breaking sound ) but as long as you save a game properly ie remembering to press return when saving over an existing game and when the new save screen comes up press return again. I've not had it crash on me at all yet but the cga mode thing you are talking about is quite standard when a game crashes I know that Bullfrog games always return you to this type of mode when they crash out and other games such as micro machines do the same.
Technical Details
Message-ID:
<4ga5fr$70g_001@salford.ac.uk>Path:
mbox-mo1.pugleaf.net!unknown!not-for-mailReferences:
<235335Z18021996@anon.penet.fi> <4g9gnq$jr7@mozo.cc.purdue.edu>Show Full Headers
Complete Article Headers
From: ITH...@news.salford.ac.uk (Christopher Arrowsmith) Subject: Re: Duke Nukem is a WIMP Date: 1996/02/19 Message-ID: <4ga5fr$70g_001@salford.ac.uk> X-Deja-AN: 140049069 references: <235335Z18021996@anon.penet.fi> <4g9gnq$jr7@mozo.cc.purdue.edu> organization: University of Salford newsgroups: alt.games.duke3d,alt.games.apogee,comp.sys.ibm.pc.games.action MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit