I'll probably just wait for the next development build to be released and then try it with the Elite Force gamepack.

Thanks for all your help, Obsidian.

I don't personally know anyone else who's interested in modding Elite Force, but I'd be willing to test the STVEF gamepack with GtkRadiant 1.6 (according to the gamepack repository, it's recently been updated to use the new 1.6 gamepack directory structure, so perhaps I could just go ahead and try i...

Okay, I tried GtkRadiant 1.4 and the qer_trans and qer_editorimage directives are interpreted correctly (i.e., triggers, clips, etc. are translucent and textures specified using qer_editorimage are shown in the editor). Since this appears to be a bug in GtkRadiant 1.5, is it worth filing an issue on...

Thanks for the suggestion; I'll try GtkRadiant 1.4 to see if the same issue occurs. I suspect it may be an issue with the game pack, however, since that "Chris Parker" fellow was apparently able to fix the problem (for GtkRad 1.5) simply by editing stvef.game.

These are actually shaders that came with the game/editor, but I checked the shaderlist (and GtkRadiant's default-shaderlist file for Elite Force) and all the shader directories are listed. (The problematic shaders are listed in GtkRadiant, they just aren't displayed correctly.) I came across a post...

Hello, I've just started using GtkRadiant 1.5 (I'm pandering to my own nostalgia and messing around with cutscenes in Elite Force) and I've noticed that it appears to have a couple of problems related to the display of certain shaders. The qer_trans property appears to be ignored, so all the trigger...