in an older version of cooledit it worked like that (at least iirc).
then you'll have to set
(loop) markers at start/end. 

Thanks, I'll take a look. 

Neg!ke, even if the loop properties was set correctly, it was missing the loop marker. I added it and it is working fine now...
I'm now able to add new sounds to my map... Thanks a lot ! You rock ! 

jpl 

can anyone explain me why doesn�t the fucking door dont work after i pass? :\

http://trinca.no.sapo.pt/l.zip

thks in advance! 

I'm getting a 'not a valid file' error from Winzip. 

http://trinca.no.sapo.pt/l.bsp
http://trinca.no.sapo.pt/l.map 

standard triggers can only have one single function: target or killtarget or message.
put the message in a trigger_relay with the same targetname as the door and it works. 

I want to have a func_button (for a deliberate player action) and a trigger_once (for a non-deliberate/unintentional action) pointing to the same target.

Can I tell from within the target's function, which of the two activated the target? This would enable me to give a different response e.g. if activated by a button, do this, else do that (to the targeted entity) 

As far as I can see, there isn't a nice self contained way to do it - meaning a way to write it that doesn't involve changing the code for the buttons and the trigger_once in some way. There is a global entity variable called "activator" that stores who is performing the triggering when something uses its targets. Unfortunately this stores the player entity that pressed the button, not the button entity itself. This inspires us to create such a global to store the entity that is doing the actual using, which I will refer to as the "mechanism"(although effector might be a better term).

Ok, first open up defs.qc and add to the bottom:

entity mechanism;

We will use this global to store the entity that is enacting the trigger, for example the button or trigger.

Next up is subs.qc, find the function
SUB_UseTargets
Right at the top of it add a temporary entity called "mech" to the existing list, followed immediately by this code:

if(self.classname == "DelayedUse")
mech = self.owner;
else
mech = self;

Next add

t.owner = self;

right after the line

t.target = self.target;

This relates to the DelayedUse line above, so that if the trigger has a delay, we still count the mechanism as the real trigger, not this temporary entity.

Now go down to the big loop at the bottom and add

mechanism = mech;

right above the line
t = find (t, targetname, self.target);
in the loop marked //fire targets(not the killtarget loop). We keep resetting this each time we run the loop, as each time we trigger something it might call SUB_UseTargets itself, which may change mechanism.

Now it's very simple to test which one of your entities set off the thing. In your new entity's use function, perform a check like

if(mechanism.classname == "func_button")
do stuff
else
do other stuff

I think this is a fairly robust system, but I've not tested it so just say if there are problems. 

Thanks, this looks good.

I will test it later this evening and report back. 

i have a lot func_illusionaries consisting of several brushes which are seperated from each other. this gives 'too many efrags' warnings. changing them to func_walls solves the problem, but i'd rather have them be nonsolid. creating a seperate func_illusionary for every single brush is out of question because (i think) there are more than 128.
so what's the principle underlying this, how far can the brushes be apart from each other, what's the difference between static and dynamic entites concerning this distance? 

Said in English with a very French accent and much overuse of the hands...

...soooperrrb!!

Thanks. 

I don't fully understand efrags, but from what I do understand, any large entity is divided into multiple efrags based on how many nodes of the BSP it occupies. This is why a large func_* with many seperate small parts is problematic.

I also don't know if/why it's different for func_wall vs. func_illusionary. But the one obvious difference is func_illusionary is a static object, and func_wall is an edict. So maybe that is partly why. 

why in gl i dont have any HOM�s and in software i got a lot of then? is there any way to solve this? 

how can i attenuate a spotlight (light with a target) in quake - pretty sure ive read something on this somewhere but can't remember where. if i remember rightly its just a single key with float value . . .

neg!ke - why not just split the big 128 brush illusionary into 2x64 brush versions? if that doesn't work split into 4x32 and so on until you get rid of the error. don't know if that'll work because i haven't come across the problem before. 

The thing you're describing is called "greyflash" -- solution: increase r_maxsurfs and r_maxedges in the console. 

aguire's light has support for custom light attentuation on spotlights. the text on his site outlines how it works 

metl: yes, static entities are definately treated differently in this respect. the first few illusionaries worked fine, the warnings only started to appear after a certain amount, i think.

ijed: i meant there are probably more than 128 (limit for static ents) brushes to be illusionary'd scattered throughout the map. most of the objects consist of around 5 brushes. apparently, that's too much already if they aren't close enough together.

my main concern was they could block the monsters but then again it wouldn't be that much of a problem either.. i might do some more tests. 

You could always use the non-static illusionary hack to make some of them info_nonulls with models, I think I've posted it somewhere in the teaching progs new tricks thread. Or if you're using a custom progs, making an info_illusionary clone that isn't a static entity is very easy. 

just read back through aguire�s readme�s and found the relevant stuff on lighting - amazing how much control is possible, and that i forgot to check there first.

reckon preach has the dodge for the static entity limit problem . . . sounds like the only way to solve it without is by testing, as you say. 

the question just posed itself:

can I make two Quake2 teleporters point at each other, like their Quake1 counterparts? Can I do a teleporter setup like in DM6 in Quake2?

Quake2 has no trigger_teleport, but instead uses misc_teleporter, which like monsters is associated with a specific model (the idiotic disc-and-particle-thing.) Can I make it use a different model (perhaps a nice slipgate?)

Anyone knows the answers by heart or do I have to build a test map?

another question: does anyone have linux binaries of qbsp3/qvis3/qrad3 and is willing to share them? Shit just doesn't compile here. No idea why.

Without them, even a test map is hypothetical :-( 

was a great mod that does exactly want you want - trigger_teleport, but it forces you to use the mod, which means for DM it probably isnt what you want. you can change the model (the base) for anything you like (big rectangle with slipgate texture) although it�ll be solid, if memory serves, and the texture won�t animate, it�ll also keep the glittery yellow particle effect. its probably best just to delete the model from inside the md2 inside the pack and place it next to world geometry as you would for q1 (except it�ll be 32x32x64 for the teleport box) but since this�d mean modifying the pack anyway you might be better off with lazarus, which�ll save you from fucking about - it also has alot of other extremely nifty stuff in there, since its made for mappers and not players; it doesn�t modify weapons or anything, just gives you alot more options, like misc_actor and (very clever)monster AI. 

I know... I actually use the lazarus library for normal playing (better monster AI among other things.) but as you say, DM maps should work with stock quake.

I guess I can live with the particle fountain thingy. Guess what; I found out that you can use an info_notnull for the teleport destination :-) now that's far more flexible than those red discs! (by the way, you can aim two misc_teleporters at each other, but you keep bouncing back and forth.)

I got something to halfway work and now I can at least make .bsp files (no vis or rad sadly.)

Quake1's teleporter setup is much more elegant though. You can have invisible/huge/tiny/... teleporters in Q1. Not so in Q2. Probably no teleport traps, too (no trigger_teleport).

Sucky. 

There is something like if you bury a misc_teleporter 6 or 8 units into the floor, then the disc and particles no longer appear in game, but you can still teleport like normal. Try that.

Also, as you tiggered out, target the teleporters at something just in front of the other teleporter (isn't there a misc_teleport_destination?) instead of at the other teleporter itself.