🚀 go-pugleaf

On Tue, 1 May 2001 22:24:48 +0100, Mjx2001 <mjx2001@lineone.net> wrote:
> "Charles Fultz" <fultz@cs.purdue.edu> wrote in message
> news:wmelu9xkf9.fsf@phoenix.cs.purdue.edu...
>> I'm having a bit of trouble getting Quake3Arena to play at an
>> acceptable speed.  My setup is as follows: CPU: dual PII-overdrives
>> 333MHz
> 
> Quake 3 Arena does not use dual CPU  systems, so  the second CPU is
> useless...  Also, a P2 333 overdrive is prehistoric and nowhere near
> minimum requirements.

I ran Quake 3 on a p200 mmx for a while, and it ran.  Not terribly well,
but at 800x600 it was playable.  Unless a P2 333 is much worse than
that, he should not have too much of a problem.  And, yeh, we all can
upgrade, but there isn't any sense in throwing out what (we) already
have.

>> RAM: 384MB Video: 3Dfx Voodoo3 3000 PCI
> 
> I do use Linux, but I stopped using a voodoo3 years ago. My Athlon 950
> MHz / Geforce 2 can manage 80 fps @ 1024 x 768 x 32 full detail... Get
> yourself a new video card, preferably, one with a little more power.

I have, and currently use a 3dfx v3 2000 pci.  It runs, and it runs
well.  Again, this should not be too much of a problem.

>> Disk: 18GB IBM SCSI (40MB/sec) 7200RPM Kernel: 2.4.3 X: XFree86-4.0.3
>> w/ tdfx driver and DRI and GLX modules
>>
>> The game looks fine, but the response is horrible.  I get anywhere
>> from 2-10 secs/frame.  That's right secs/frame, not frames/sec.  I
>> get the same results playing as a user or root.  Can anyone help me
>> out here?  I know I should be getting like anywhere from 30-50
>> frames/sec.
> 
> 50 fps with a p2 333 and voodoo3 - you are dreaming.

Well, at 640x480 or lower, with options lowered, he should at least be
in the 20fps range.

As to Charles: I had the same problem as you on my system.  I fixed it
by installing a glide dri package designed for 3dfx cards, which came in
the contrib directory of Slackware.  The main file of concern was
usr/lib/libglide3.so.3.10.0.  After I installed this, everything ran as
it should.

Good luck.  If this doesn't work for you, then maybe there's something
else awry.  Also, it is probably worth running the app glxinfo; this
might give you some incite as to where to go next.