If you target a light with your doors(only one though) yes, every open and close cycle of the doors will turn the light off/on or on/off(spawnflag set to "start off").

If you give both doors the light as a target nothing will happen. 

testing again... 

Sorry for the confusion.

From what I tested, it seems you'll need to set the door to "toggle", then set up a trigger brush to open the door and turn on the light. Then copy that trigger brush where the player will hit it again. Setting up delays and resets as needed.

BTW, the door and light can have the same name, the trigger brush will activate both.

If I left it up to only the door to trigger the light it only worked for either the open OR close operation. You couldn't get both. 

I don't know. Neither sounds very useful so I've never tried them. 

Thank you, timing will be hard to calculate though.. if only there would be closed event to know exactly when it is actually fully closed.

Func_train have these corner events, but re-creating door to be func_train might not be wise move. Unless it is easy to create func_train behave like doors, also including same sounds like door's have. 

func_train as a door which triggers the light ;)

http://www.quaketastic.com/files/misc/func_train_ex_Newhouse.zip

If you need an explanation let me know. 

More experienced AD mappers, here is questions for you.
How do you use func_train's corner_route, corner_switch and corner_pause, is there any maps already using these a lot? 

now i know why the orange box is called the orange box

there is a pack of developer textures for quake like those in HL2 ? 

After some testing it seems like I can use trigger_once, disable it and then reset it when needed. Since func_train door has only two states: open / closed, triggering that same trigger_once in a right moment makes it behave like doors, by that mean they open again. 

Without extra triggers/complications.

In the example map I posted in #18110, all you need to do is give path corner 2(p2) a wait value(wait at corner) that you want.

Ex: Giving it a wait value of 4 would be 4 seconds before it closed.

I gave both path corners a -1 wait value just to demonstrate the functionality in a controlled way. 

There is no problem with wait atm.

All I need to know atm is how do you change path_corner state from forward to alt forward? I use Corner Event to set active trigger again to check if player is near the door still. 

Better question, how do you make it change path_corner's state only when trigger_once calls it? 

It might be best to send an e-mail to Sock himself if you do not find your answers. I can't think of a test map that uses the corner events but it is described in detail in the AD readme. 

I tried but I don't know what you want anymore :(

A door has an open position and a closed position, thus, using a func_train as a door requires two path corners. The door targets the first path corner... then the first path corner targets(target of forward route) the second path corner with the second targeting the first. So they loop.

I can't envision what you want since that is a door. It can be toggled or close automatically same as any door. Using standard triggers or buttons targeting the door.

Either way, hope you get it sorted out. 

Thank you for helping me. I will try to understand what readme tells me, before I bother Sock too much.

Here is picture to help you visualize what I'm trying to do:
https://drive.google.com/file/d/0BwxYkKdSD855UWF5bVpRUm90NWc/view?usp=sharing 

Seems back in the day people tried to keep targetnames short. There even is a switch in some light tool to shorten the names after compiling. What's the reason for that? Did old engines have issues with long strings or was it memory consideration? 

So I recently started fiddeling with trenchbroom.
I figured most of the stuff but I dont know how to do skyboxes.
My other request is to find out how to make a certain music track play.
Thank you in advance.
Ps.: I've just set up an amazing double helix staircase and cannot wait to show it off. 

Skyboxes
In TB, when you add some texture wads to your texture collection menu. Some wads has simple skybox textures, their name starts with sky it seems: something like sky1, sky_stars etc.

You can place brushes with those textures, and they will work as a sky. What I know, you can only have one sky texture.

Music
when you click whatever normal brush, you will have keys listed on your right side window. Search through them and find the key "message". Type number on empty textfield near it and it corresponds the track number. 

"sounds" not "message".

To use a skybox instead of a sky texture, specify the skybox name in the "sky" field in worldspawn (same entity as where you specify music) 

 

Why would you use sky field in worldspawn, if you need to seal map anyway? 

Lolwut 

The texture given in the sky field replaces whatever sky texture you use in your map for the skybox. It won't draw sky on void areas if that's what you thought it did.