I just got trigger_push working, and I didn't set the speed. Boy, that scared the SHIT outta me when I tested it. 

For some reason, I can't make push go in a specific angle, just 90 degrees up and down, and full rotation going around. So, yeah. 

angles 90 45

You have to specify more than one direction when using the angles key. In Quakespasm...to really get exact, you can play the map and in the console type: r_pos 1

This will give you constant location data of your player including viewing angle. Have your player face the direction where you want the push to go and record the values labeled Pitch Yaw Roll. For your requirements, you are looking for Pitch and Yaw values.

At least I think this is how it works. :p 

That's what I did, but more
angles 90 85

It failed to launch me into the air, and looked like it was trying to accelerate me into the ground. 

angles -15 45 0

if you want it to push you up, first value should be negative (-90 straight up, 90 straight down) 

I looked back at the one time I used the angles key for a trigger_push and the pitch should be negative for upwards motions...DeeDoubleU has it right.

I still recommend using r_pos 1 (or viewpos) to get the exact desired "push" you are looking for! ;) 

Now all I have to do is calculate (aka experiment) how much force (speed) I need to go 64 units up plus the angle. Make it triggerable with a floor button, and bang. Jump pad! 

I use a trigger_once for a func_door or plat elevator able one time? triggered by a button 

So, what I think you are asking is how to press a button once, and it will trigger only once. To do that, add this in keys/values of the button:

time -1

What time does is after you press the button, it will stay depress for x amount of time before being repressable. Setting time to -1 just means for the button to stay indented after pressed. 

in a way, it's too bad everyone is using only hammer and tb these days. both those editors do not display the old school entity descriptions like radiant did and that is a much easier way to learn the stuff. :(

Plats are always drawn in the
extended position, so they will
light correctly.

If the plat is the target of another
trigger or button, it will start out
disabled in the extended position
until it is triggered, when it will lower
and become a normal plat.

Flags:
"plat_low_trigger"
plat will only be triggered when in
lowered position

Keys:
"speed"
moving speed, default is 150
"height"
determines the amount the plat
moves, instead of being implicitly
determined by the model's height.
"sounds"
1 = base fast
2 = chain slow

so a trigger_once in this case would unlock and lower a plat and then the plat would work as normal. 

I believe you meant "wait" key. 

What editor are you using? I'm interested... 

 

I get try 

i use tb now, but i used to use qeradiant for many years, then a version of radiant sikkpin had worked on. radiant doesn't have those 'smart' keys, instead it just displays the text left by the developers and you would have to manually add in the key names. it was a bit more work, but you would learn how the entity behaved a lot faster.
of course, radiant, as an editor isn't as fun to use as tb. and it's not hammer either. if you want to give radiant a spin, netradiant 1.5 is the one that is still being worked on. 

Hopefully in his successor, he will add an entity list with keys and examples of values. 

TB2 shows you everything that's in the FGD file. It shows you all keys that have default values (in italics), and it shows you the descriptions (either in tooltips or in the text field below the property table). 

keeps the brushing mode? I like the Smart brushing mode of TB 

By smart brushing? 

30 seconds per quadrant, soft bristles, don't forget to floss. 

srry, easy brush grid 

 

 

easy brush, pues hablo ingl�s a medias. :S 

"no filling performed" why happens?

I don't know if the problem of dissapeared �TEMS in the bsp file have relation with it...