setWaypointTimeout: Difference between revisions
Jump to navigation
Jump to search
m (Text replace - "{{uc:{{PAGENAME}}}}" to "{{uc:{{PAGENAME}}}} {{uc:{{PAGENAME}}}}") |
m (Text replace - "{{uc:{{PAGENAME}}}}" to "{{uc:{{PAGENAME}}}} {{uc:{{PAGENAME}}}}") |
||
Line 51: | Line 51: | ||
[[Category:Command_Group:_Waypoints|SETWAYPOINTTIMEOUT]] | [[Category:Command_Group:_Waypoints|SETWAYPOINTTIMEOUT]] | ||
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] |
Revision as of 12:07, 25 March 2013
Description
- Description:
- Defines the time between condition satisfaction and waypoint finish (randomly from min to max, with an average value mid).
- Groups:
- Uncategorised
Syntax
- Syntax:
- waypoint setWaypointTimeout [min, mid, max]
- Parameters:
- waypoint: Array - format Waypoint
- [min, mid, max]: Array
- min: Number
- mid: Number
- max: Number
- Return Value:
- Nothing
Examples
- Example 1:
[_grp, 2] setWaypointTimeout [5, 10, 6]
Additional Information
- See also:
- addWaypointwaypointTimeout
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
Notes
-
LUCKY44: The example doesn't seem to make sense, according to the listed syntax. It seems to set a Max time greater than the Mid time.
tom_48_97 04:30, 12 December 2010 (CET):
If mid is greater than max, the result will be really near the mid value.
Results with the values of the example: 8.237, 9.383, 10.425, 9.417, 9.43401, 10.425, 9.90601, 9.96701, 9.42401, 9.42502, 9.96698, 9.89999...
Ps: I'll delete these comments on saturday.