Damm, that Darkplaces has a nice chase cam. HoT's works flawlessly, but view is obscured by a huge player model when your back is to wall. With darkplaces, the model just slides away, or maybe the camera is moved slightly forward of player ?. Proquake (1.30?) has a nice view, but go into start map , to the corner immediate left of normal skill teleport, and view is totally obscured. FitzPlus v2 gets obscured too, and a little hard to see differences, though i suppose they exist. 

I'm having problems with custom textures for the HUD (menus, console, etc). They aren't working yet, while textures replacements for the walls, floor, ceilings, items, etc, are all working.

For example, suppose you have a texture called "NUM_2.tga" to change some of the HUD elements, where do you put it in the id1 folder ? What is the directory structure for the HUD and console textures ?

Of course, I'm using QuakeSpasm... 

try /id1/gfx? 

Replacement textures for the maps. Nothing else. Not mdl models, charset, HUD, etc.

I don't believe this has changed in Quakespasm. 

quakespasm does do mdl replacement.
the textures go in /progs/ with the format: modelname.mdl_#framenum#.tga 

Glad to see they are using the DarkPlaces replacement texture naming convention. I'd like to see that as the "standard" naming convention because the other way of doing it is very kludgy.

(Engine wise, adding external texture support for sbar pics and menu items is a bit of a pain.) 

The menus and the weapons textures replacements don't work.

I've created a "progs" and a "gfx" folder inside the "id1" directory, and added the textures (from pk3 packages found on the Quake Retexturing Project web site). It doesn't show while in the game.

For example, there's a texture called "nail.mdl_0.tga" to change the nail gun. I also tried "nail.mdl_#0#.tga". Doesn't show in QuakeSpasm.

What am I doing wrong ? 

Typically. 

Are you sure about external model texture support? I'm not seeing that in the Quakespasm change log.

/Too lazy to actually check myself but eventually I will. 

oh my... i had rmqe in my gui loader and not qs.
sorry. :S 

Damn ! So no weapons and hud replacements in QuakeSpasm ?

O well, ... 

i still play with all the original textures and i like to disable texture filtering, so fitzquake and quakespasm are perfect for me.
but quakespasm isn't really an eye candy engine. i think you would be better served with another, fancier, one. 

Quakespasm is pure eye candy. and if it means that eye poop is not supported then yay! 

Should be picked up universally if you're going to support this at all. Other ways aren't just kludgy, they're flat-out broken. Check out progs/s_light.mdl and progs/s_light.spr in your ID1 pak0.pak - if you have progs/s_light.tga, which of these is the texture for? 

Then I'm wondering why textures replacement is supported for all the floors, walls, ceillings, etc, in QuakeSpasm, while the weapons and hud textures aren't.

This is weird ! 

They are handled completely different in the code/engine. 

I tried Fitzquake and DarkPlaces and I prefer QuickSpasm.

Fitzquake is almost identical to Fitzquake, I don't see much differences.

What are your opinions on Fitzquake ?

DarkPlaces is fat, heavy, and sloooow ! The frame rate is very low for what it does.

I don't like its rendering style. There are three slide bars for the gamma and brightness, and I was unable to get the map looking right.

The weapons textures replacement is working in DarkPlaces, but it isn't that great after all. 

I meant :

Fitzquake is almost identical to QuakeSpasm, I don't see much differences. 

Quakespasm is based on Fitzquake. The differences are mostly subtle and under the hood. It's now slightly more versatile than Fitz085 and more frequently updated.

Darkplaces is indeed slow and cluttered with features (as well as 'unfeatures'). Unless you're a sucker for over-the-top eye candy or intend to play/create advanced mods, I would not recommend it (for regular Q1SP). 

i would use fitzquake, except it exhibits the multicore timing bug for me.
otoh, like neg says, qs is updated often, while fq only has sporadic updates (and that's not a dig at you, metl :))

as for DP, it breaks standard quake functionality in a few spots (tracelines in particular) which is incredibly annoying, almost requiring you to make two seperate progs.
that said, DP isn't horrible. it's all those absurd texture packs and OTT particle packs that make it seem that way. it does require a more powerful machine, but it also has some great stuff in it to. of course, i'm probably the only person who runs with nearest neighbour texture filtering and q3 water shaders. (the reflection/refraction effects are nearest neighbour too!) 

I wouldn't be negative towards an engine feature like external texture support just because it gets used in a manner you find tasteless.

A lot of single player maps are bad, but that doesn't make mapping bad nor the idea of people learning mapping bad. 

Ok then, it's all clear to me now.

I'm sticking to QuakeSpasm.

I hope there will be an update to add FSAA and vertical sych support, and the Command-H feature of OS X. Custom textures support for the HUD and menus would be appreciated too ! (I don't care anymore about the weapons texture replacement...) 

Just force FSAA and v-sync in the nvidia/ati control tab. 

There is no nvidia/ati control tab on OS X. It's an app thing. 

On linux you can do it with
nvidia-settings --query=fsaa --verbose
to get FSAA modes, then
__GL_FSAA_MODE=12 quakespasm
But it doesnt seem to work/do anything with OS X.

http://arstechnica.com/civis/viewtopic.php?f=19&t=313756