*EHEM* help! Created 19 years ago2005-07-02 08:57:57 UTC by Instant Mix

It was a wee while ago i tried to make a door which was starnge, sotra like this .It came out , then flew into the wall.All it did was when i pushed the button , it made the ""stop"" sound.Any help? (I have not fixed it)

sometimes to door doesnt appear where you want it to, it only happens when your using path corners to make a door. Wierd error, are you using path_corners?

If you mean that you use a rotating door then you need to create brush with an origin texture on it in the place that you want the door to rotate around it!

its must be a rotating door error,like elon said create a origin brush.
what kinda door is it? (its not possible in func_door/i guess) :

Path_corners for doors thats stupid but if you do use path_corners then you will need an origin!(Even regular trains need it)

Might need to set a Lip value.

First question :Yes I Am Using Path_Corner.
Second question :It's Not A Rotating Door.
Third Q :Still No!
Forth Q :Eh??Yariv , You ARE The Only One Who Can Help Me!
Fifth Q :Nope , I Don't Need LIP Value's.

Oh , Did I mention , The door was a Func_train , and strangeley enough (Yariv!)I have Never , Never-Ever Needed a Origin Texture in the middle of Func_Trains , ORIGIN IS FOR ROTATING THINGS!!

You need an origin in the func train. It wont work. Why do you think you put origin brushes in cars and stuff (they do rotate). Evenif they dont, they still need it.

Origin....ooooooorrrrrriiiiiigggggiiiiinnnnn

Once I didn't use an origin when I built trains and lots of strange stuff heppened(train living the texture behind, train hurts you with out setting it to do it and it doesn't smash you) and they were only elevator!

I have a question that might pertain to this, tell me to do another topic if i doesnt.

I have created a box that i would like to pop open revealing a key used to open a door later on. The inner part/lid of the box and the brush for the key are set up as func_trains traveling from a path_corner at their closed positions to another at their open positions. These are activated by triggering two buttons tied to a multisource, which then targets a mm that targets the two func_trains. This sequence worked well at first, but then i tied the mm to another multisource which acted as a master for a 1-time trigger extending from the opening of the "opened" box. This targeted a mm sequence to remove the key and all according to the "key" tut on this website. Now.... there is a 11 second delay from the activation of the first two buttons to the opening of the box. y? Everything else works perfectly; just confused about the unwanted delay.

Note, that i dont have an origin brush for the func_trains.... could that be y?