* 2 new levels, describing one as "crazy". 
* the machine gun spews shell casings on the floor
* when you shoot at water, it bubbles. 
* invisibility is being used, 
* the grenade launcher which is "bouncy and cool".
* bots are reportedly very impressive, so as much as people couldn't tell who was real and who wasn't.

Thanks to Homeboy Foozmelon for reporting this. 

This new version changes which file it loads on startup. If refreshed.dat exists from a previous execution of X11Spy, it will load that file. If refreshed.dat does not exist, it will load the servers from servers.dat. Other new features include the ability to manually add servers and delete them. 

Snag it HERE

At E3 today, Macmillan Computer Publishing announced Quake: The Offering and Quake II: Colossus for Linux. These are the game + mission pack bundles that were alluded to in somebody's .plan update awhile back. Each product will contain the full game and both mission packs for that game. The games will install via RPM (or rpm2cpio for non-rpm systems), so getting Linux Quake up and running quickly will become a whole lot easier! And we'll also finally have a glibc version of Quake 1! This is very cool. I've heard unofficially that these products should be on store shelves at the end of the month.

Whoohoo, id is on a Linux rampage, now is the time to convert ye sinners....

I know I'm really, really going to regret this, but....I'm getting enough 
tech support e-mails that, if I'm gonna deal with some of them, I'd at least
like maximum information.

IF you can't get graphics to work on your system, please do the following:

- if you have a Voodoo Graphics, Voodoo Banshee, Voodoo 2, or Voodoo Rush:
        1.) download the VERY latest Quake3-certified drivers from www.3dfx.com
        and install them.  Please be very careful that you don't have any files
        like 3DFXVGL.DLL or OPENGL32.DLL residing in your Quake3 directory.

- if you have a regular 2D/3D accelerator under Win9x, either download the
        latest drivers from your respective hardware vendor's Web site, OR
        download GLSETUP that will autodetect your hardware and install up 
        to date drivers.  GLSETUP will be much larger, but if you don't know
        what hardware you have, it will simplify things for you immensely.

- if you are running Windows NT, download the latest drivers from your 
        hardware vendor's Web site and install them.

In ALL cases please make sure that you do not have any extraneous
OPENGL32.DLL or 3DFXVGL.DLL files residing in your system search path.  They
should ONLY be in /windows/system, not in /quake3!

If you have been dicking around with files haphazardly (e.g. q3config.cfg,
unpacking the PK3 file, etc.), then you may have inadvertently hosed your
install.  In that case, toast your current installation, and re-install.  One
nice thing about the test being multiplayer only is that you don't have
to worry about any save files!

If you are still having problems and you get an error dialog with the console
debugging output (it should have a lot of text and some buttons like "Copy",
"Clear", and "Quit" or something like that), then copy that text and e-mail
it to me.

If you do not get the above, then try running Q3TEST as follows:

quake3 +cvar_restart +set logfile 2

This should generate a file called QCONSOLE.LOG somewhere in your /quake3
directory path.  E-mail that to me.

No promises, but I'm working on trying to figure out why some people are
getting that weird problem on 3Dfx stuff.  Right now the VAST majority of
bugs reported to me have to do with the new 3Dfx drivers; ATI drivers on
Windows NT; and some problems with AMD machines.  I'm trying to isolate this
stuff so we can have a rock solid retail release.

* fixed crashtest 4
* fixed crashtest 3
* fixed jumping-over-item pickup prediction error
* made "Couldn't load sound" a developer only warning
* fixed demo recording not including portal surface entities
* precache grenade bounce sounds

The donation will go to Keith Whitwell, who has been optimizing Mesa to improve performance on 3d hardware. Thanks to Keith's work, many applications using Mesa 3.1 will see a dramatic performance increase over Mesa 3.0. The donation will allow Keith to continue working on Mesa full time for some time to come.

You can bias the level of detail lower than allowed in the
menu with "r_lodbias 2", which will force all models to the lowest
lod.  The view weapon will look very ugly.

Another little speedup option that isn't offered in the menus is:
"cg_simpleitems 1" this removes the extra rings and spheres around
some items.

You can also turn off all the gibs with "cg_gibs 0".
 

* clear game memory at init, which fixes the stuck-at-intermission
        problem on mac servers
* fixed mismatched free / Z_Free in demo menu
* removed unused reference to sprites/plama.md3
* automatically get sounds from model name
* scale sensitivity by zoom
* immediately archive changes to latched cvars
* cheat protect r_portalonly
* don't print "XXX connected" on level restarts
* fixed "give item" on levels where 0,0,0 is in solid
* fixed timedemo
* don't play pain falling sound if dead
* fixed falling damage sound not snd specific
* fixed crashtest 2
* fixed crashtest 1
* q3map_backshader
* q3map_globaltexture

The main issues we're seeing are:

3Dfx drivers seem to be pretty darn difficult.  About 50% of the emails
comprise of 3Dfx issues including BSOD on NT, crashing during level changes,
and crashing due to in game mode changes.  We're working with 3Dfx on this.

The next biggest problem is that people run the game without running GLSETUP
to update their drivers.  Arrgh.  Arrgh.

People claim that the TNT slows to a crawl when you in-game change the video
color depth to 32bpp, but it's fine after a restart.

There's a "lag trap" quirk of firing the plasma gun 12 times at a wall, as
people approach it the overdraw slows their systems and makes them
vulnerable to hits.

There's a lot of people trying to run the game with 32mb of RAM.

Setting everything to "highest" (highest resolution, color depth, etc.)
causes artifacts on the TNT.

Alt-TAB on a Matrox G200 causes the system to crash.

A lot of people wrote to let us know that they just love the game.

The main game feedback seems to be:

1. the new railgun sucks / and / or is / awesome.
2. the game is too slow / too fast.
3. make it more like quake 1 / quake 2.
4. the rockets are too slow / too fast.
5. people die too slow / too fast.
6. the graphics are awesome / too cartoony.
7. don't touch a thing / change everything.