Yes, or some other way to remotely control a server. ProQuake's RCON works well and is easy to use. And since ProQuake already contains this functionality, it seems like it would be easiest to just copy the ProQuake stuff. Then FitzQuake would be able to RCON to a ProQuake server or to a FitzQuake server.

Another nice ProQuake feature that would be easy to add is the longer text chat lines....

I'm going to compose an e-mail with more feedback/bug reports/suggestions. 

Christ, if someone's naming Forwards Compatible as "secretly one of the best releases of 2008" then the rest of y'all should be ashamed of yourselves. 

I was wondering if you looked into LordHavoc's dynaimc lights speed up option and the possibility of putting it in Fitzquake? Thx 

I haven't really looked into it yet, but based on baker's post, it sounds like that was merely a speedup to the code for determining the floor light value under a monster (since that is how monsters and players are lit, based on what they're standing on.)

Second, i already probably use that optimization, since i got my .lit support code from darkplaces, and that includes the changes to R_LightPoint and related functions.

The major issue with glquake lighting in general is that it requires uploading new lightmap textures anytime the lightmaps change, which is one of the slowest things you can do with a video card. At some point I will look at ways that can be improved; I can think of a bunch off the top of my head (using 8bpp textures when level has no colored light, uploading more, smaller rectangles of texture data instead of fewer, larger ones, etc.) 

What is the proper command line to run nehahra with Fitzquake 0.85? 

no Nehahra support (...yet) 

I installed DP once, a while ago, and for some dark reasons it crashes after some minutes...

You're using DP. 

... I'm not using it anymore :P 

Is the business. 

Can somebody explain what the -nomtex command line option does? 

That disables multitexture rendering. 

Can you explain a little bit more in depth? I was wondering how disabling the multitexture rendering helped the dynamic light speed up issue. 

In Fitzquake, (and glquake with gl_texsort 1) polygons are sorted by texture and then all the polygons for each texture are rendered, then all polygons for the next texture, and so on.

With multitexture enabled, the lightmaps are rendered at the same time, and when a lightmap needs to be updated for dynamic lighting, it triggers an upload.

Without multitexture, the lightmaps are rendered in a second stage after all textures. And, during this second stage, the polygons are sorted by which lightmap they use. And there might be a difference in how the uploads are done, since the lightmaps are encountered in a different order.

Since switching textures while rendering is somewhat expensive, but uploading textures is more expensive, but the total amount of lightmap uploads vs. the actual total number of lightmap pixels uploaded might have different costs, either one could be faster on different maps, different video cards, etc.

One of the things on my to-do list is a general optimization and rendering overhaul, so i might be able to get this stuff sped up even more. 

Very happy with this other than water is very foggy and hard to see in it. What inputs make it clear? Otherwise it is deff. keeper! :P 

And I think the Ring of Shadows fog is too foggy as well.... and when you're wearing a ring AND are underwater, it's way-too-super-foggy!

I don't want the fog effects turned off completely though....

(metlslime, did you get that e-mail I sent?) 

sorry, haven't had a chance to respond to your email yet, but i did recieve it.

About the screen coloring for water and powerups, i haven't changed this from GLQuake as far as i can remember, so i'll have to check again and see what's up with that. 

There seems to be some issue with ATI.

Some german guy reported this:
http://r4d1um.seitzinger.eu/DSC00038.JPG
Ati Radeon X1250 with latest drivers
AMD Turion 64 X2 TL-60 2x2,0 GHz & 2 GB Ram
Windows XP SP2 (32 Bit)

If he starts the game it looks like that. If he alt-tabs out and right back in it fixes itself. But as soon as the next map is loaded it is garbled again and he has to alt-tab out and in once more.

He encounters the same in GL Quake, GL QuakeWorld and Hexen II. 

at work (shhh) ;) 

any idea, does he have this issue with all glquake engines or do some have fixed behavior? 

Dunno, I could ask him to try some. Which ones would be good? aguirRe's and Joequake maybe? 

I have the same problems on ATI hardware. The fix? Add -bpp 32 to the command line or in the case of Fitzquake it can be set in the config. 

That fixed it for that guy too. Thanks!
Maybe make 32 bit the default in the future? 

Doesn't it run slower then? 

These days? I can't imagine. 

but it uses more memory (since quake loads all textures are at the same color depth as the framebuffer.) So 32bpp uses twice the total video memory compared to 16bpp.