Article View: alt.games.quake2
Article #516Re: 3d
From: Matt
Date: Mon, 29 Sep 1997 00:00
Date: Mon, 29 Sep 1997 00:00
37 lines
1842 bytes
1842 bytes
Barry <barry....@btinternet.com> wrote in article <60ik58$i...@neon.btinternet.com>... > Hi, > Can anyone take a guess as to what will be needed to play Quake 2 hardware > wise? I have a P200-MMX, 32MB EDO a Righteous 3d and a 4MB MB Mystique 220. > Can anyone predict the frame rate with that setup? (I've guessed <15). > > Thanks > -- > Barry > barry....@btinternet.com > > > Hey, you're be up in the high 20's at least!! Figure it out - Mystique won't be used, the Righteous will handle most of the graphics itself. Also, it will do all the effects for you (transparency and such) in hardware (excluding the other extras - mip mapping, filtering etc. - which will be hardware specific), as opposed to software. 32 mb will suffice (16 will be the minimum, but 32 will be greatly better - less disk access). MMX not important (it won't be used, or if it is I'll be shocked - I mean, 50 clock cycles to go from floating point - which Q2 will use - to MMX integers, it's just too slow; unless you have a P2 - 1 cycle to change!!). So, with a 200 handling the AI, physics, and other stuff, with the 3DFX concentrating on the graphics, you'll get 23-28 fps in 640x480 EASILY. What do you get in GLQ? Probably 40 + (with it optimized), so 30 fps seems a realistic figure. Pity the fools who have to do it all in software (640x480 = 5fps, est.). Matt
Technical Details
Message-ID:
<01bccd26$d7096620$LocalHost@mwba01863>Path:
mbox-mo1.pugleaf.net!unknown!not-for-mailReferences:
<60ik58$i7t@neon.btinternet.com>Show Full Headers
Complete Article Headers
From: "Matt" <chai...@cableinet.co.uk> Subject: Re: 3d Date: 1997/09/29 Message-ID: <01bccd26$d7096620$LocalHost@mwba01863> X-Deja-AN: 276628332 X-NNTP-Posting-Host: usr9-bas.cableinet.co.uk References: <60ik58$i7t@neon.btinternet.com> Organization: "Cable Internet (post doesn't reflect views of Cable Internet)" Newsgroups: alt.games.quake2 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit