a bunch of well-made assets ready to go that a lot of people would use

Sock has some really nice ones:

http://www.simonoc.com/pages/artwork/tp_plants.htm 

Baker - thanks very much for that! Looks interesting, I'll have a play with that :)

adib - sock's foliage assets are great for Q3, but I would want to be making stuff that fits in with quake's established chunky-pixel aesthetic. 

I might try deleting the config. 

Checking to see changes involved:

Engine modification requires:
1) Creating a color table for alpha masked textures (probably already exists since QS/Mark V both support this for the .bsp)
2) A method for specifying if a model's texture should be an alpha masked. (Sadly, since some rare models do use color 255 in them ...). Options cvar list var, external file, model name, somehow adding more model flags to a .mdl (like blood trail). Default option is probably creating a cvar with model names like the existing r_nolerp_list.
3) Checking such a model's texture for actual palette index 255 alpha masking, and if not disabling it.
4) Turning on alpha test during draw for specified models, then turning it off. Since GLQuake model lighting and FitzQuake overbrighting is just a color modification, no other drawing consequences.
5) Permitting external textures to have an alpha channel for models where alpha masking is indicated. 

Cheers, sounds reasonably doable ;}

2) I guess a list cvar fits in with the existing list stuff. To ensure that everyone gets the list in my mod even if quake.rc doesn't run (e.g. if someone loads the mod from the console), would it work if I did a stuffcmd from the QuakeC? 

I'd rather Spike suggest a better solution than the cvar list thing. ;-)

I hate the cvar list thing. Consider it an ugly placeholder until someone comes up with a better idea or a standard.

So consider the cvar list as a temporary placeholder until someone comes up with a great idea. 

Spike says something about a model flag that Hexen 2 uses above. Hmmm. 

I'd personally be down for using a new flag (like blood trail).

However that requires tools that would support it. It personally doesn't bother me in the slightest as I bang out .mdls from blender using a script that I can easily edit. 

For existing tools (QME) to conveniently work, I would personally opt for checking BOTH a rocket trail and grenade trail (selecting multiple trails is non-sensical in the engine, it only uses the first trail flag).

In model.c in model load, engine authors can just add a

if (model->flags & (EF_ROCKET | EF_GRENADE) == EF_ROCKET | EF_GRENADE ) model->flags ~= EF_ROCKET | EF_GRENADE, model->flags |= EF_ALPHA_MASKED;

A non-supported engine it's going to render horribly wrong anyway with pink everywhere.

This would allow QME to be able to edit the flag, instead of putting terrible burdens on mappers.

/One thought ... Spike said only FTE has a mechanism currently. 

QME lets you set any flag I think, not just the ones in use...

http://i.imgur.com/w3MTNZt.png

So, using an unused flag might be ok, even for people who for some masochistic reason use QME to make mdls. 

Awesome, did not know that!

Methinks Spike may not have known that, I didn't like the "must use Hex Editor idea". 

and reading his above comment,

looks like 0x4000 (16384 decimal) is the flag that would be most compatible with FTE. 

Sometime in the next 24 hours I'll grab bush1.mdl and palmleav.mdl (a palm tree) from Kurok, edit the model flag in QME and post a Windows OpenGL .exe Mark V with the implementation. 

I'd better get my modelling trousers on 

Another possible way to specify that the model should be alpha masked is making the skin name start with "{". Hexen2's TEX_HOLEY model flag (16384) seems OK though. Are hexen 2 and quake mdl's the same format, aside from extra flags used by h2?

I was reading the uhexen2 source, it looks like both palette index 0 and 255 are transparent for TEX_HOLEY, at least in uhexen2. But we would just use 255 since that's what is used elsewhere in quake.

Last thing: it might be worth comparing this with a different approach: trying obj2map's new UV/texturing import feature, and then either compile the foliage maps to bsp (disadvantage: lighting would be static) or even try using itendswithtens's new map instance inserter tool to automate pasting prefabs in your map (?). My light tool can even raytrace through the fence textures properly, giving natural shadows under trees. This route is likely more of a pain to set up, but it would have the advantage of working in all the engines that already support "{" textures. 

Quake loads up a hexen2 .mdl fine. Other than that, I don't know how the formats differ.

I'm thinking of making the foliage move in some cases, so bsp wouldn't be great for that.

Also I just don't think bsp feels right for the sort of geometry I have in mind.

Also: plant monsters. 

killer hedges / vines.. looking forward to seeing this! 

Alphamasked MDL texture support has existed in Makaqu for ages, and Super8 inherited it.

I've also implemented it in the x86 ASM version of the MDL drawing code, for fast performance. 

So far, I've deleted the Config, and It still crashes on startup. Is it not compatible with Windows 7? 

Experimental Windows GL Build with alpha texture support for models (with changed source files)

Palette 255 is transparent color, model must have flag 0x4000 set in the .mdl QME 3.1.

A test mod is supplied. Type in console:
"game alphamaskmodeltexture; map start" and watch the lavaball in the HARD hallway which has been replaced with palm leave .mdl.

And looks like this:

Screenshot 

I develop on Windows 7. I don't know why you are having the problem, somewhere around 100 ppl have used Mark V WinQuake.

If you are committed to helping me identify the nature of the problem, I might be able to get it running for you if you are willing to post logs and such. I think in another thread Skiffy said he had a problem like yours.

Let me know. 

@ericw - agreed, heh.

@mk - that's awesome that Makaqu has that feature already. Even more awesome that you have asm for it. 

Wow, that's perfect. Thanks so much for this!

I'm going to be making a lot of assets that showcase this in my mod. Might even be ready for the 20th anniversary expo! 

ok, i'm sold. that looks terrific! 

@necros -- updated the above download raising max static entities from 512 to 8192.

Client-side entities are very small and just keep track a couple of dozen numbers/positions/times and the static limit was just an array of client-side entities and nothing more.

(MH and Spike point out other limiting factors.)