If you set a trigger's "Timeout" option, you will notice that it countsdown until trigger activation. For example, if you set a 10 second timeout, it will take the trigger 10 seconds to activate and will not timeout. {F17539}
Description
Description
Details
Details
- Legacy ID
- 3552551260
- Severity
- Minor
- Resolution
- Duplicate
- Reproducibility
- Always
- Category
- Editor
Steps To Reproduce
- Place a trigger and set it up to do something (like sound an alarm for example)
- Set a 5 second timeout in all fields (MIN, MID, MAX)
- Enter trigger area
- You will notice it takes 10 seconds for the trigger to activate
Event Timeline
Comment Actions
Well Sidewinder is right but the other way around.
TIMEOUT - works as it should. (CORRECT)
COUNTDOWN - behaves like TIMEOUT (NOT CORRECT)
http://community.bistudio.com/wiki/Mission_Editor:_Triggers#Countdown.2FTimeout_Counters
I'm Attaching Simple (Trigger_Timeout_or_Countdown.Stratis.rar) TEST Mission that reproduces the behavior (includes visual TIMERS).