🚀 go-pugleaf

I know im not on Linux but for ref I get fairly stable 60fps in 800*600 with
most of the candy on using

v3-3000 AGP
Athlon750
256Mb
Win2K

So you should be able to get 30-50 without issues.

Have you tried turning SMP off in Q3 as I doubt the 3dfx drivers support it.
Might be the problem. Just look for smp in your config and make sure its set
to 0.

HTH

Crap Name [AGQx]
--
...
"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
> RAM: 384MB
> Video: 3Dfx Voodoo3 3000 PCI
> 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.
>
> Please send responses to my e-mail address: fultz@purdue.edu
>
> Thanks,
> Charles Fultz
> fultz

I had that problem in linux when my nvidia graphics acceleration was turned
off. You might also make sure it is set to full using xconf or something
similar.

"Crap Name [AGQx]" <warren@NOSPAM.leggatt.demon.co.uk> wrote in message
news:988725184.20478.0.nnrp-14.c1ed5d97@news.demon.co.uk...
> I know im not on Linux but for ref I get fairly stable 60fps in 800*600
with
> most of the candy on using
>
> v3-3000 AGP
> Athlon750
> 256Mb
> Win2K
>
> So you should be able to get 30-50 without issues.
>
> Have you tried turning SMP off in Q3 as I doubt the 3dfx drivers support
it.
> Might be the problem. Just look for smp in your config and make sure its
set
> to 0.
>
> HTH
>
> Crap Name [AGQx]
> --
> ...
> "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
> > RAM: 384MB
> > Video: 3Dfx Voodoo3 3000 PCI
> > 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.
> >
> > Please send responses to my e-mail address: fultz@purdue.edu
> >
> > Thanks,
> > Charles Fultz
> > fultz
>
>

Today, Charles Fultz wrote:

>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
>RAM:		384MB
>Video:		3Dfx Voodoo3 3000 PCI
>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.

enter \com_hunkmegs 192

also send us the output of glxinfo and lsmod

Regards,

Philip Willoughby

--
echo bzidd@nfo.ho.co.se | tr "bizndfohces" "pwgd9ociaku"

"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.

> 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.

> 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.

>
> Please send responses to my e-mail address: fultz@purdue.edu
>
> Thanks,
> Charles Fultz
> fultz

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.

> > 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.
>

Quake 3 DOES use dual processors if they are available and the SMP option is
enabled. Your graphics card drivers have to be coded to handle it though or
it will cause issues.

You gain about 10% performance from the second CPU and it helps the load in
big firefights. I have seen plenty of benchmarks on the web that describe
the difference between single and dual setups.

Philip Willoughby <pgw99@doc.ic.ac.uk> writes:

> Today, Charles Fultz wrote:
> 
> >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
> >RAM:		384MB
> >Video:		3Dfx Voodoo3 3000 PCI
> >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.
> 
> enter \com_hunkmegs 192
> 
> also send us the output of glxinfo and lsmod

Here is the output of glxinfo:
display: :0.0  screen:0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
client glx vendor string: SGI
client glx version string: 1.2
client glx extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, 
    GLX_ARB_get_proc_address
GLX extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
OpenGL vendor string: VA Linux Systems, Inc.
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 Mesa 3.4
OpenGL extensions:
    GL_ARB_multitexture, GL_ARB_texture_cube_map, GL_ARB_tranpose_matrix, 
    GL_EXT_abgr, GL_EXT_blend_color, GL_EXT_blend_func_separate, 
    GL_EXT_blend_logic_op, GL_EXT_blend_minmax, GL_EXT_blend_subtract, 
    GL_EXT_clip_volume_hint, GL_EXT_compiled_vertex_array, GL_EXT_histogram, 
    GL_EXT_packed_pixels, GL_EXT_paletted_texture, GL_EXT_point_parameters, 
    GL_EXT_polygon_offset, GL_EXT_rescale_normal, 
    GL_EXT_shared_texture_palette, GL_EXT_stencil_wrap, GL_EXT_texture3D, 
    GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_object, 
    GL_EXT_texture_lod_bias, GL_EXT_vertex_array, GL_HP_occlusion_test, 
    GL_INGR_blend_func_separate, GL_MESA_window_pos, GL_MESA_resize_buffers, 
    GL_NV_texgen_reflection, GL_PGI_misc_hints, GL_SGI_color_matrix, 
    GL_SGI_color_table, GL_SGIS_pixel_texture, GL_SGIS_texture_edge_clamp, 
    GL_SGIX_pixel_texture

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
0x23 16 tc  0 16  0 r  .  .  5  6  5  0  0  0  0  0  0  0  0  0 0 None
0x24 16 tc  0 16  0 r  .  .  5  6  5  0  0  0  8  0  0  0  0  0 0 Slow
0x25 16 tc  0 16  0 r  .  .  5  6  5  0  0  0  0 16 16 16  0  0 0 Slow
0x26 16 tc  0 16  0 r  .  .  5  6  5  0  0  0  8 16 16 16  0  0 0 Slow
0x27 16 tc  0 16  0 r  .  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x28 16 tc  0 16  0 r  .  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x29 16 tc  0 16  0 r  .  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x2a 16 tc  0 16  0 r  .  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x2b 16 tc  0 16  0 r  y  .  5  6  5  0  0  0  0  0  0  0  0  0 0 None
0x2c 16 tc  0 16  0 r  y  .  5  6  5  0  0  0  8  0  0  0  0  0 0 Slow
0x2d 16 tc  0 16  0 r  y  .  5  6  5  0  0  0  0 16 16 16  0  0 0 Slow
0x2e 16 tc  0 16  0 r  y  .  5  6  5  0  0  0  8 16 16 16  0  0 0 Slow
0x2f 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x30 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x31 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x32 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x33 16 dc  0 16  0 r  .  .  5  6  5  0  0  0  0  0  0  0  0  0 0 None
0x34 16 dc  0 16  0 r  .  .  5  6  5  0  0  0  8  0  0  0  0  0 0 Slow
0x35 16 dc  0 16  0 r  .  .  5  6  5  0  0  0  0 16 16 16  0  0 0 Slow
0x36 16 dc  0 16  0 r  .  .  5  6  5  0  0  0  8 16 16 16  0  0 0 Slow
0x37 16 dc  0 16  0 r  .  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x38 16 dc  0 16  0 r  .  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x39 16 dc  0 16  0 r  .  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x3a 16 dc  0 16  0 r  .  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x3b 16 dc  0 16  0 r  y  .  5  6  5  0  0  0  0  0  0  0  0  0 0 None
0x3c 16 dc  0 16  0 r  y  .  5  6  5  0  0  0  8  0  0  0  0  0 0 Slow
0x3d 16 dc  0 16  0 r  y  .  5  6  5  0  0  0  0 16 16 16  0  0 0 Slow
0x3e 16 dc  0 16  0 r  y  .  5  6  5  0  0  0  8 16 16 16  0  0 0 Slow
0x3f 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x40 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x41 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x42 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow

Charles Fultz
fultz

"Mjx2001" <mjx2001@lineone.net> writes:

> "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.

Mjx2001, are you on crack!?  First of all, YES, Q3A DOES support dual
procs.  Check out this DOCUMENTED command-line option:
Flag   Description
----   ------------
r_smp  Setting this to "1" enables dual CPU support for the Quake3
       rendering/graphics engine. Note that your graphics card
       drivers and operating system must support smp.

Also, do a search for 'quake3 dual' or 'quake3 smp' on Deja.com.

Secondly, here are the MINIMUM system requirements for Q3A, as
published on lokigames.com:
                      Pentium 233 MHZ with 8 MB video card*, or
Processor/Video       Pentium II 266 MHz with 4 MB video card*, or
                      AMD K6-350 MHZ with 4 MB video card*

Okay, lets see, I have two PII 333MHz and a 16MB Voodoo3 3000.
I MORE than meet the minimum system requirements.
You best be doing some research before spreading FALSE information.

> > 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 don't have a GeForce and don't want one, therefore your comments are
of absolutely no value to this conversation.

> > 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.

No, but you've been hitting the crack pipe a little too hard.
Hehe, man you're lame.

Charles Fultz
fultz

Today, Charles Fultz wrote:

>The following message is a courtesy copy of an article
>that has been posted to alt.os.linux.slackware,3dfx.glide.linux,alt.games.quake3,comp.os.linux.misc as well.
>
>Philip Willoughby <pgw99@doc.ic.ac.uk> writes:
>
>> Today, Charles Fultz wrote:
>>
>> >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
>> >RAM:		384MB
>> >Video:		3Dfx Voodoo3 3000 PCI
>> >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.
>>
>> enter \com_hunkmegs 192
>>
>> also send us the output of glxinfo and lsmod
>
>Here is the output of glxinfo:
>display: :0.0  screen:0
>direct rendering: No

                   ^^
that means it is using software GL... Chack the kernel module is loaded and
that DRI is enabled in your XF86Config, and that you have read and write
access in the DRI mode command.

Regards,

Philip Willoughby

--
echo bzidd@nfo.ho.co.se | tr "bizndfohces" "pwgd9ociaku"

Today, Charles Fultz wrote:

>"Mjx2001" <mjx2001@lineone.net> writes:
>
>> "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.
>
>Mjx2001, are you on crack!?  First of all, YES, Q3A DOES support dual
>procs.  Check out this DOCUMENTED command-line option:
>Flag   Description
>----   ------------
>r_smp  Setting this to "1" enables dual CPU support for the Quake3
>       rendering/graphics engine. Note that your graphics card
>       drivers and operating system must support smp.

Last time I tried this, it failed.  They may have fixed it in newer
drivers/point release.  That was on dual-celeron 400s with voodoo3s.

Regards,

Philip Willoughby

--
echo bzidd@nfo.ho.co.se | tr "bizndfohces" "pwgd9ociaku"

The prob is caused by the 3dfx driver not supporting SMP.



--
...
"Philip Willoughby" <pgw99@doc.ic.ac.uk> wrote in message
news:Pine.LNX.4.32.0105021611080.30654-100000@pub.doc.ic.ac.uk...
> Today, Charles Fultz wrote:
>
> >"Mjx2001" <mjx2001@lineone.net> writes:
> >
> >> "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.
> >
> >Mjx2001, are you on crack!?  First of all, YES, Q3A DOES support dual
> >procs.  Check out this DOCUMENTED command-line option:
> >Flag   Description
> >----   ------------
> >r_smp  Setting this to "1" enables dual CPU support for the Quake3
> >       rendering/graphics engine. Note that your graphics card
> >       drivers and operating system must support smp.
>
> Last time I tried this, it failed.  They may have fixed it in newer
> drivers/point release.  That was on dual-celeron 400s with voodoo3s.
>
> Regards,
>
> Philip Willoughby
>
> --
> echo bzidd@nfo.ho.co.se | tr "bizndfohces" "pwgd9ociaku"
>

"Charles Fultz" <fultz@cs.purdue.edu> wrote in message
news:wmoftbx57l.fsf@phoenix.cs.purdue.edu...
> "Mjx2001" <mjx2001@lineone.net> writes:
>
> > "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.
>
> Mjx2001, are you on crack!?  First of all, YES, Q3A DOES support dual
> procs.  Check out this DOCUMENTED command-line option:
> Flag   Description
> ----   ------------
> r_smp  Setting this to "1" enables dual CPU support for the Quake3
>        rendering/graphics engine. Note that your graphics card
>        drivers and operating system must support smp.
>
> Also, do a search for 'quake3 dual' or 'quake3 smp' on Deja.com.
>
> Secondly, here are the MINIMUM system requirements for Q3A, as
> published on lokigames.com:
>                       Pentium 233 MHZ with 8 MB video card*, or
> Processor/Video       Pentium II 266 MHz with 4 MB video card*, or
>                       AMD K6-350 MHZ with 4 MB video card*
>
> Okay, lets see, I have two PII 333MHz and a 16MB Voodoo3 3000.
> I MORE than meet the minimum system requirements.
> You best be doing some research before spreading FALSE information.

Games Minimum System Requirements, as printed on game boxes are a joke.
What they mean to say is, "minimum system required to run game at 320 x 200
x 16 bit colour mode with 10 fps." or some other equally obscore resolution.
Anyone serious about playing Quake should have at least a 17" monitor, and
on a monitor that size, you'd be an idiot to play the game in anything less
than 1024 x 768 x 32... I'd shudder at the thought of playing Q3A on a
K6-2/250 with 4mb AGP card. If we are to believe minimum specs' on
software - Windows 95 only needs 8 MB of memory you know.





se 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 don't have a GeForce and don't want one, therefore your comments are
> of absolutely no value to this conversation.
>
> > > 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.
>
> No, but you've been hitting the crack pipe a little too hard.
> Hehe, man you're lame.
>
> Charles Fultz
> fultz

I used to run a p2-300 + v3 without much issues. It was in vertex mode and
at 800*600 but I still managed to get 40-50 fps. The person with his Dual p2
setup should have NO problems running Q3.

I still have my V3 in my new Athlon tbrid 750 on a 21" screen and still run
it at 800*600. Yes the display would be better at a higher resolution but I
prefer to keep stable at 60fps at all times instead of having the variations
I get when I run at the higher resolutions.
--
...
"Mjx2001" <mjx2001@lineone.net> wrote in message
news:tf0kp29ena7u47@corp.supernews.co.uk...
>
> "Charles Fultz" <fultz@cs.purdue.edu> wrote in message
> news:wmoftbx57l.fsf@phoenix.cs.purdue.edu...
> > "Mjx2001" <mjx2001@lineone.net> writes:
> >
> > > "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.
> >
> > Mjx2001, are you on crack!?  First of all, YES, Q3A DOES support dual
> > procs.  Check out this DOCUMENTED command-line option:
> > Flag   Description
> > ----   ------------
> > r_smp  Setting this to "1" enables dual CPU support for the Quake3
> >        rendering/graphics engine. Note that your graphics card
> >        drivers and operating system must support smp.
> >
> > Also, do a search for 'quake3 dual' or 'quake3 smp' on Deja.com.
> >
> > Secondly, here are the MINIMUM system requirements for Q3A, as
> > published on lokigames.com:
> >                       Pentium 233 MHZ with 8 MB video card*, or
> > Processor/Video       Pentium II 266 MHz with 4 MB video card*, or
> >                       AMD K6-350 MHZ with 4 MB video card*
> >
> > Okay, lets see, I have two PII 333MHz and a 16MB Voodoo3 3000.
> > I MORE than meet the minimum system requirements.
> > You best be doing some research before spreading FALSE information.
>
> Games Minimum System Requirements, as printed on game boxes are a joke.
> What they mean to say is, "minimum system required to run game at 320 x
200
> x 16 bit colour mode with 10 fps." or some other equally obscore
resolution.
> Anyone serious about playing Quake should have at least a 17" monitor, and
> on a monitor that size, you'd be an idiot to play the game in anything
less
> than 1024 x 768 x 32... I'd shudder at the thought of playing Q3A on a
> K6-2/250 with 4mb AGP card. If we are to believe minimum specs' on
> software - Windows 95 only needs 8 MB of memory you know.
>
>
>
>
>
> se 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 don't have a GeForce and don't want one, therefore your comments are
> > of absolutely no value to this conversation.
> >
> > > > 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.
> >
> > No, but you've been hitting the crack pipe a little too hard.
> > Hehe, man you're lame.
> >
> > Charles Fultz
> > fultz
>
>

Philip Willoughby <pgw99@doc.ic.ac.uk> writes:

> Today, Charles Fultz wrote:

> >Here is the output of glxinfo:
> >display: :0.0  screen:0
> >direct rendering: No
> 
>                    ^^
> that means it is using software GL... Chack the kernel module is loaded and
> that DRI is enabled in your XF86Config, and that you have read and write
> access in the DRI mode command.

Here is the output from dmesg concering DRM:
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 322M
agpgart: no supported devices found.
[drm] Initialized tdfx 1.0.0 20000928 on minor 63

I don't have any AGP cards, so the complaint from agpgart should be
fine.  Is this good enough for the kernel level?

Also, when I start X here is the output concerning DRI/DRM:
(==) TDFX(0): Write-combining range (0xf8000000,0x2000000)
(II) TDFX(0): Textures Memory 7.93 MB
(0): [drm] created "tdfx" driver at busid "PCI:0:17:0"
(0): [drm] added 4096 byte SAREA at 0xc4971000
(0): [drm] mapped SAREA 0xc4971000 to 0x40014000
(0): [drm] framebuffer handle = 0xf8000000
(0): [drm] added 1 reserved context for kernel
(II) TDFX(0): [drm] Registers = 0xfa000000
(II) TDFX(0): visual configs initialized
(II) TDFX(0): Using XFree86 Acceleration Architecture (XAA)
        Screen to screen bit blits
        Solid filled rectangles
        8x8 mono pattern filled rectangles
        Indirect CPU to Screen color expansion
        Solid Lines
        Dashed Lines
        Offscreen Pixmaps
        Driver provided NonTEGlyphRenderer replacement
        Setting up tile and stipple cache:
                10 128x128 slots
(==) TDFX(0): Backing store disabled
(==) TDFX(0): Silken mouse enabled
(0): X context handle = 0x00000001
(0): [drm] installed DRM signal handler
(0): [DRI] installation complete
(II) TDFX(0): direct rendering enabled

Here is the DRI section from my XF86Config:
Section "DRI"
    Mode  0666
EndSection

And here is the output of me running quake3 with the command:
/usr/local/games/quake3/quake3.x86 +set r_smp 1

Q3 1.27g linux-i386 Dec 18 2000
----- FS_Startup -----
Current search path:
/home/fultz/.q3a/baseq3
/usr/local/games/quake3/baseq3/pak5.pk3 (7 files)
/usr/local/games/quake3/baseq3/pak4.pk3 (272 files)
/usr/local/games/quake3/baseq3/pak0.pk3 (3539 files)
/usr/local/games/quake3/baseq3

----------------------
3818 files in pk3 files
execing default.cfg
couldn't exec q3config.cfg
couldn't exec autoexec.cfg
Hunk_Clear: reset the hunk ok
Joystick is not active.
----- Client Initialization -----
----- Initializing Renderer ----
-------------------------------
----- Client Initialization Complete -----
----- R_Init -----
...loading libGL.so: Initializing OpenGL display
...setting mode 3: 640 480
Using XFree86-VidModeExtension Version 2.0
Xlib:  extension "XFree86-DGA" missing on display ":0.0".
Failed to detect XF86DGA Mouse
XFree86-VidModeExtension Activated at 1280x1024
Using 4/4/4 Color bits, 16 depth, 0 stencil display.
GL_RENDERER: Mesa GLX Indirect
Initializing OpenGL extensions
...GL_S3_s3tc not found
...ignoring GL_EXT_texture_env_add
...not using GL_ARB_multitexture, < 2 texture units
...using GL_EXT_compiled_vertex_array
Trying SMP acceleration...
...failed.

GL_VENDOR: VA Linux Systems, Inc.
GL_RENDERER: Mesa GLX Indirect
GL_VERSION: 1.2 Mesa 3.4
GL_EXTENSIONS: GL_ARB_multitexture GL_ARB_texture_cube_map GL_ARB_tranpose_matri
x GL_EXT_abgr GL_EXT_blend_color GL_EXT_blend_func_separate GL_EXT_blend_logic_o
p GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_compi
led_vertex_array GL_EXT_histogram GL_EXT_packed_pixels GL_EXT_paletted_texture G
L_EXT_point_parameters GL_EXT_polygon_offset GL_EXT_rescale_normal GL_EXT_shared
_texture_palette GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_env_add GL_
EXT_texture_env_combine GL_EXT_texture_object GL_EXT_texture_lod_bias GL_EXT_ver
tex_array GL_HP_occlusion_test GL_INGR_blend_func_separate GL_MESA_window_pos GL
_MESA_resize_buffers GL_NV_texgen_reflection GL_PGI_misc_hints GL_SGI_color_matr
ix GL_SGI_color_table GL_SGIS_pixel_texture GL_SGIS_texture_edge_clamp GL_SGIX_p
ixel_texture
GL_MAX_TEXTURE_SIZE: 2048
GL_MAX_ACTIVE_TEXTURES_ARB: 0

PIXELFORMAT: color(16-bits) Z(16-bit) stencil(0-bits)
MODE: 3, 640 x 480 fullscreen hz:N/A
GAMMA: software w/ 0 overbright bits
CPU: 
rendering primitives: single glDrawElements
texturemode: GL_LINEAR_MIPMAP_NEAREST
picmip: 1
texture bits: 0
multitexture: disabled
compiled vertex arrays: enabled
texenv add: disabled
compressed textures: disabled
Initializing Shaders
...loading 'scripts/gfx.shader'
...loading 'scripts/base.shader'
...loading 'scripts/base_button.shader'
...loading 'scripts/base_floor.shader'
...loading 'scripts/base_light.shader'
...loading 'scripts/base_object.shader'
...loading 'scripts/base_support.shader'
...loading 'scripts/base_trim.shader'
...loading 'scripts/base_wall.shader'
...loading 'scripts/common.shader'
...loading 'scripts/ctf.shader'
...loading 'scripts/eerie.shader'
...loading 'scripts/gothic_block.shader'
...loading 'scripts/gothic_floor.shader'
...loading 'scripts/gothic_light.shader'
...loading 'scripts/gothic_trim.shader'
...loading 'scripts/gothic_wall.shader'
...loading 'scripts/hell.shader'
...loading 'scripts/liquid.shader'
...loading 'scripts/menu.shader'
...loading 'scripts/models.shader'
...loading 'scripts/organics.shader'
...loading 'scripts/sfx.shader'
...loading 'scripts/shrine.shader'
...loading 'scripts/skin.shader'
...loading 'scripts/sky.shader'
...loading 'scripts/test.shader'
----- finished R_Init -----

------- sound initialization -------
------------------------------------
----- Sound Info -----
sound system is muted
    1 stereo
32768 samples
   16 samplebits
    1 submission_chunk
22050 speed
0x44b55000 dma buffer
No background file.
----------------------
Sound memory manager started
Loading vm file vm/ui.qvm.
VM file ui compiled to 583332 bytes of code
ui loaded in 1945504 bytes on the hunk
30 arenas parsed
32 bots parsed
--- Common Initialization Complete ---
Opening IP socket: localhost:27960
Hostname: foley.fultzs.net
Alias: foley
IP: 192.168.1.13
RE_Shutdown( 1 )
Hunk_Clear: reset the hunk ok

If you need any more information please let me know.
Thanks SO much for  helping me.

Charles Fultz

Yesterday, Charles Fultz wrote:

>The following message is a courtesy copy of an article
>that has been posted to alt.os.linux.slackware,3dfx.glide.linux,alt.games.quake3,comp.os.linux.misc as well.
>
>Philip Willoughby <pgw99@doc.ic.ac.uk> writes:
>
>> Today, Charles Fultz wrote:
>
>> >Here is the output of glxinfo:
>> >display: :0.0  screen:0
>> >direct rendering: No
>>
>>                    ^^
>> that means it is using software GL... Chack the kernel module is loaded and
>> that DRI is enabled in your XF86Config, and that you have read and write
>> access in the DRI mode command.
>
>Here is the output from dmesg concering DRM:
>Linux agpgart interface v0.99 (c) Jeff Hartmann
>agpgart: Maximum main memory to use for agp memory: 322M
>agpgart: no supported devices found.
>[drm] Initialized tdfx 1.0.0 20000928 on minor 63
>
>I don't have any AGP cards, so the complaint from agpgart should be
>fine.  Is this good enough for the kernel level?

Probably.  Are you using the drm from the kernel or from the DRI tree?  The
one in the DRI tree is the best one to use, especially if you are using the
DRI X server.  Which X server are you using?

>Also, when I start X here is the output concerning DRI/DRM:
<snip>
>(II) TDFX(0): direct rendering enabled

This means that it has loaded and enabled the DRI... So your kernel part is
probably correct.

>Here is the DRI section from my XF86Config:
>Section "DRI"
>    Mode  0666
>EndSection

This should be OK.

>And here is the output of me running quake3 with the command:
>/usr/local/games/quake3/quake3.x86 +set r_smp 1

Try /usr/local/games/quake3/quake3.x86 +set r_smp 0 +set r_gldriver
/usr/X11R6/lib/libGL.so

Regards,

Philip Willoughby

--
echo bzidd@nfo.ho.co.se | tr "bizndfohces" "pwgd9ociaku"

"Crap Name [AGQx]" <warren@NOSPAM.leggatt.demon.co.uk> writes:

> The prob is caused by the 3dfx driver not supporting SMP.

Is there any way to get a driver that DOES support SMP?

Charles Fultz
fultz

Philip Willoughby <pgw99@doc.ic.ac.uk> writes:

> Yesterday, Charles Fultz wrote:

> >I don't have any AGP cards, so the complaint from agpgart should be
> >fine.  Is this good enough for the kernel level?
> 
> Probably.  Are you using the drm from the kernel or from the DRI tree?  The
> one in the DRI tree is the best one to use, especially if you are using the
> DRI X server.  Which X server are you using?

I'm using DRM built into the kernel.  Should I rebuild a kernel and
build DRM as a module?  Or can I use the kernel I have now (w/ DRM builtin)
and just insmode the DRI module?

> >Also, when I start X here is the output concerning DRI/DRM:
> <snip>
> >(II) TDFX(0): direct rendering enabled
> 
> This means that it has loaded and enabled the DRI... So your kernel part is
> probably correct.
> 
> >Here is the DRI section from my XF86Config:
> >Section "DRI"
> >    Mode  0666
> >EndSection
> 
> This should be OK.
> 
> >And here is the output of me running quake3 with the command:
> >/usr/local/games/quake3/quake3.x86 +set r_smp 1
> 
> Try /usr/local/games/quake3/quake3.x86 +set r_smp 0 +set r_gldriver
> /usr/X11R6/lib/libGL.so

I'll give it a try.

Again, thanks for helping me out here.
I know my machine can do better, I just need a bit of help getting it
to do better.

Charles Fultz
fultz

Today, Charles Fultz wrote:

>The following message is a courtesy copy of an article
>that has been posted to alt.os.linux.slackware,3dfx.glide.linux,alt.games.quake3,comp.os.linux.misc as well.
>
>Philip Willoughby <pgw99@doc.ic.ac.uk> writes:
>
>> Yesterday, Charles Fultz wrote:
>
>> >I don't have any AGP cards, so the complaint from agpgart should be
>> >fine.  Is this good enough for the kernel level?
>>
>> Probably.  Are you using the drm from the kernel or from the DRI tree?  The
>> one in the DRI tree is the best one to use, especially if you are using the
>> DRI X server.  Which X server are you using?
>
>I'm using DRM built into the kernel.  Should I rebuild a kernel and
>build DRM as a module?  Or can I use the kernel I have now (w/ DRM builtin)
>and just insmode the DRI module?

You shoulf build the drm as a module unless you have a good reason not to.
This will allow you to use the module out of DRI cvs should it become
necessary.B

>> >Also, when I start X here is the output concerning DRI/DRM:
>> <snip>
>> >(II) TDFX(0): direct rendering enabled
>>
>> This means that it has loaded and enabled the DRI... So your kernel part is
>> probably correct.
>>
>> >Here is the DRI section from my XF86Config:
>> >Section "DRI"
>> >    Mode  0666
>> >EndSection
>>
>> This should be OK.
>>
>> >And here is the output of me running quake3 with the command:
>> >/usr/local/games/quake3/quake3.x86 +set r_smp 1
>>
>> Try /usr/local/games/quake3/quake3.x86 +set r_smp 0 +set r_gldriver
>> /usr/X11R6/lib/libGL.so
>
>I'll give it a try.
>
>Again, thanks for helping me out here.
>I know my machine can do better, I just need a bit of help getting it
>to do better.
>
>Charles Fultz
>fultz
>

Regards,

Philip Willoughby

--
echo bzidd@nfo.ho.co.se | tr "bizndfohces" "pwgd9ociaku"

I have seen this exact symptom when software gl is the driver in linux
and in windoze.

I am leaning towards there being a problem with the 3dfx driver under
X. smp compatibility or not, the 3dfx driver is not working properly.

Charles Wilkins


On Wed, 2 May 2001 20:02:29 +0100, "Crap Name [AGQx]"
<warren@NOSPAM.leggatt.demon.co.uk> wrote:

>I used to run a p2-300 + v3 without much issues. It was in vertex mode and
>at 800*600 but I still managed to get 40-50 fps. The person with his Dual p2
>setup should have NO problems running Q3.
>
>I still have my V3 in my new Athlon tbrid 750 on a 21" screen and still run
>it at 800*600. Yes the display would be better at a higher resolution but I
>prefer to keep stable at 60fps at all times instead of having the variations
>I get when I run at the higher resolutions.

I second that - there is something distinctly wrong with the 3dfx
drivers. I finally got mine working half-decent, but Unreal Tournament
looked like crap because of the 16 bit colordepth the 3dfx driver uses,
so I replaced it with an old TNT2 card - less hassle, much more stable,
and it renders UT correctly.

-Fredrik


Charles Wilkins wrote:
> 
> I have seen this exact symptom when software gl is the driver in linux
> and in windoze.
> 
> I am leaning towards there being a problem with the 3dfx driver under
> X. smp compatibility or not, the 3dfx driver is not working properly.
> 
> Charles Wilkins
> 
> On Wed, 2 May 2001 20:02:29 +0100, "Crap Name [AGQx]"
> <warren@NOSPAM.leggatt.demon.co.uk> wrote:
> 
> >I used to run a p2-300 + v3 without much issues. It was in vertex mode and
> >at 800*600 but I still managed to get 40-50 fps. The person with his Dual p2
> >setup should have NO problems running Q3.
> >
> >I still have my V3 in my new Athlon tbrid 750 on a 21" screen and still run
> >it at 800*600. Yes the display would be better at a higher resolution but I
> >prefer to keep stable at 60fps at all times instead of having the variations
> >I get when I run at the higher resolutions.

Fredrik Olausson wrote:

> I second that - there is something distinctly wrong with the 3dfx
> drivers. I finally got mine working half-decent, but Unreal Tournament
> looked like crap because of the 16 bit colordepth the 3dfx driver uses,

Voodoo 3s don't do 3d in any other depth - it's not the driver.

Andy.