Trigger_presence

zil

<div class="IPBDescription">creating an automatic door</div> I've made a door that opens automatically for everyone that comes neer it and closes when everone leaves. However if u leave and re-enter quickly the system gets messed up even though i have the doors speed set very high. The reason this is happening is because the trigger_presenec is sending the trigger message to the door while it is in motion and therefore the door ignores the message. Ive tried increasing the speed of the door to an amount where that won't happen but then the door moves way to fast to be visible inbetween psotions and looks really bad. I need a way for the message that the trigger_presence sends to be held until the door is free to recieve it. I tried to do this by giving a multi_source children but when u do this it seems that u are unable to make the multisource as a master to something so it won't work. Any ideas as to what i can do? Apart from just making a normal door like everyone else would <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo-->

Carling

Humm.
You could try using a train as your door.
How about a momentery door, they open while your turing a wheel and start closing when u stop. i belive you can use that trig as the activator for it.

Ollj

momentary doors ONLY work with MOMENTARY buttons. anything else causes bad errors.

Trigger relays are easy time deelays (argh).
No clue whats the simplest way of synciong it. tried lots without succes.

Another idea could be triggering an invisible func_wall_toggle (for the blocking effect) and an illusionary door for the visual effect.

The problem with trigger presence is that it goes out of sync with objects that dont toggle in zero-time. Lights, single initiations and not moving objects are fine.
Phasegates and super fast movements will always cause timing/ sync problems on trigger_presence.

I dont like trigger-presence doors. I hate them in eclipse because they never hehave like they should.
Just give them a button or make them use-only.

zil

yea i guess ill just have to make a normal door then. pitty because an automatic door would've been nice

thx for the help

Ollj

other simple idea.
Use a func button AS door.
Func buttons have an "activate on touch" flag, a lip value and a reset time to close again. Jiust causes little headache on skulks running against a door to open it.
you can also make a second, normal, func button that aims on that func button, that is your door.

using Buttons as doors and doors_or_buttons as elevators are simple tricks for better NS performance.

The_Real_Quasar

Or just use trigger_multiple?

zil

i'm afraid i cant use buttons because the door is actually made up of a couple of parts. I just have to fallback to the old standby of trigger_multiple

Ollj

when 2 buttons have the same name they dont move at once?

Lt_Gravity

use trigger_multiple. its also used for doors that consists of different parts like doors with an window (rendermode additiv). otherwise it can be happen that the door moves but the window doesnt. trigger_multiple is the best way to achieve the automatic door.