Page MenuHomeFeedback Tracker

Trigger "Timeout" setting functions the same as the "Countdown" setting. As a result, the trigger does not timeout
Closed, ResolvedPublic

Description

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}

Details

Legacy ID
3552551260
Severity
Minor
Resolution
Duplicate
Reproducibility
Always
Category
Editor
Steps To Reproduce
  1. Place a trigger and set it up to do something (like sound an alarm for example)
  2. Set a 5 second timeout in all fields (MIN, MID, MAX)
  3. Enter trigger area
  4. You will notice it takes 10 seconds for the trigger to activate

Event Timeline

Sidewinder36 edited Additional Information. (Show Details)
Sidewinder36 set Category to Editor.
Sidewinder36 set Reproducibility to Always.
Sidewinder36 set Severity to Minor.
Sidewinder36 set Resolution to Duplicate.
Sidewinder36 set Legacy ID to 3552551260.May 7 2016, 11:49 AM

Slight error in my Steps to Reproduce. Step 2 should be a 10 second timeout, not 5.

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).

Closing in favor of #8398, which contains more correct info.