Those don't seem like the right commands, let me fire it up and check.

Edit: OK, commands are:

\timedemo 1
\demo four

The leading backslash makes it a command instead of a chat message.

I think demo001 related to the shareware version or something? "four" is what's generally used.

Edit2: Also, it will insert the backslash if you hit tab to autocomplete the commands themselves (e.g. timed[TAB] will autocomplete to \timedemo)

SquallStrife wrote:

\timedemo 1
\demo four

Yep, that did it!

What is a decent framerate for a K6-III-450 at 1280x1024 (non-3dfx)? I get 33.0 fps. This is about what I got in Quake II at 640x480. Why does Q3 seem so fast?

Is there any way to put Quake 3 it into software mode?

No software mode for Quake 3 only OpenGL.

I get about 35fps on a K6-3-400 with a Voodoo 2.

Pretty sure that it uses 3dnow, which helps a lot.

The latest patch only includes Demo004 (I think it deletes Demo001 and Demo002 for whatever reason). Make sure to also type these before you run a timedemo:
s_initsound 0
snd_restart
disconnect

why not just choose and play demo from the game's main menu(after setting timedemo 1)?
and i invite you to test my demo in this thread:
introducing my quake3 benchmark demo

feipoa wrote:

Yep, that did it! […]
Show full quote

SquallStrife wrote:

\timedemo 1
\demo four

Yep, that did it!

What is a decent framerate for a K6-III-450 at 1280x1024 (non-3dfx)? I get 33.0 fps. This is about what I got in Quake II at 640x480. Why does Q3 seem so fast?

Is there any way to put Quake 3 it into software mode?

i guess you havn't set quake3 to high image quality, and your quake2 score is a crusher demo rather than a simple "demo01" demo.

feipoa wrote:

Is there any way to put Quake 3 it into software mode?

r_allowSoftwareGL 1, then go disable directdraw acceleration. Then, watch your framerate plummet to 4spf 😀

Q3A usually goes around 30fps in busy scenes on a Pentium II 300, so a K6-2 450 scoring in that area should be normal. I squeezed 37fps out of a PCX2.