Difference between revisions of "sleep"

From Bohemia Interactive Community
Jump to navigation Jump to search
m
m (Text replacement - " *\| *([Cc]omments|COMMENTS|Game|[Gg]ame [Nn]ame( +[0-9])?|Game [Vv]ersion( +[0-9])?|Game Version \(number surrounded by NO SPACES\)|Arguments in MP|MP[Aa]rg|Multiplayer Arguments( \("local" or "global"\))?|Effects|Execution|Effects...)
 
(45 intermediate revisions by 16 users not shown)
Line 1: Line 1:
−
{{Command|= Comments
+
{{Command
−
____________________________________________________________________________________________
 
  
−
| arma |= Game name
+
| arma1
  
−
|1.00|= Game version
+
|1.00
−
____________________________________________________________________________________________
 
  
−
| Suspend execution of [[Function]] or [[SQF_syntax|SQF]] [[Script]] for given time in seconds. |= Description
+
|gr1= Program Flow
−
____________________________________________________________________________________________
 
  
−
| '''sleep''' delay |= Syntax
+
| Suspends code execution for given time in seconds. The sleep precision is given by a framerate, the delay given is the minimal delay expected. Must be called inside of a context which is interruptible, i.e. a [[Script (Handle)|script]] executed by [[execVM]] or [[spawn]].
 +
{{Informative |
 +
* this command will suspend the code for '''''at least''''' the given amount of time, and can be way more if the [[Scheduler|script scheduler]] is busy.
 +
* this command will suspend the script as the game gets paused in single player (and will resume with it). To avoid this, use [[uiSleep]].
 +
}}
 +
 
 +
| '''sleep''' delay
 +
 
 +
|p1= delay: [[Number]] - in seconds. Negative values will not be considered.
 +
 
 +
| [[Nothing]]
  
−
|p1= delay: [[Number]] |= Parameter 1
+
|x1= <code>[] [[spawn]] {
 +
[[sleep]] 5;
 +
[[hint]] "after (at least) 5 seconds...";
 +
};</code>
  
−
| [[Nothing]] |= Return value
+
|x2= <code>[[sleep]] 5 + [[random]] 10; {{cc|incorrect - will only sleep for 5 seconds, as it will be interpreted as (sleep 5) (+(random 10))}}
−
____________________________________________________________________________________________
+
[[sleep]] (5 + [[random]] 10); {{cc|correct}}</code>
−
 
 
−
|x1= <pre>sleep 0.5;</pre> |= Example 1
 
−
____________________________________________________________________________________________
 
  
−
| [[Control Structures]] |= See also
+
|x3= <code>[[if]] ([[isMultiplayer]]) [[then]]
 +
{
 +
[[uiSleep]] 3; {{cc|more precise in (non-pausable) multiplayer}}
 +
} [[else]] {
 +
[[sleep]] 3; {{cc|[[sleep]] gets paused as the game is, usually wanted behaviour}}
 +
};</code>
  
 +
|  [[uiSleep]], [[waitUntil]], [[canSuspend]], [[execVM]], [[spawn]], [[sleep vs uiSleep]], [[Control Structures]]
 
}}
 
}}
  
Line 27: Line 40:
 
<dl class="command_description">
 
<dl class="command_description">
 
<!-- Note Section BEGIN -->
 
<!-- Note Section BEGIN -->
−
<dd class="notedate">Posted on December 20, 2006 - 19:53</dd>
+
<dd class="notedate">Posted on December 20, 2006 - 19:53
−
<dt class="note">'''[[User:CrashDome|CrashDome]]'''</dt><dd class="note">Sleep suspends both SQF functions and SQF scripts. In functions, the calling script is still in suspension due to waiting for a return from the [[call]] command. The game engine will continue, however. See [[Function]] for more detail.</dd>
+
<dt class="note">[[User:CrashDome|CrashDome]]<dd class="note">Sleep suspends both SQF functions and SQF scripts. In functions, the calling script is still in suspension due to waiting for a return from the [[call]] command. The game engine will continue, however. See [[Function]] for more detail.
−
<dd class="notedate">Posted on February 12, 2007 - 20:16</dd>
+
 
−
<dt class="note">'''[[User:Kronzky|Kronzky]]'''</dt><dd class="note">Sleep durations between .0005 and .02 will cause the same delay (roughly .02 seconds).<br>Delays of .0005 and less have '''no''' effect (ie, the sleep call will return immediately).</dd>
+
<dd class="notedate">Posted on February 12, 2007 - 20:16
−
<dt class="note">'''[[User:Sbsmac|Sbsmac]]'''</dt><dd class="note">The comment above is a little misleading. The game engine appears to work by processing frames and then checking to see whether scripts are available to execute.  Sleep causes the script/function to be suspended until at least the specified time has elapsed.  To wait for the next frame, or give other scripts a chance to run, use Sleep 0.001. </dd>
+
<dt class="note">[[User:Kronzky|Kronzky]]<dd class="note">Sleep durations between .0005 and .02 will cause the same delay (roughly .02 seconds).<br>Delays of .0005 and less have '''no''' effect (ie, the sleep call will return immediately).
−
<dd class="notedate">Posted on July 16, 2007 - 00:13</dd>
+
 
−
<dt class="note">'''[[User:galatei|Galatei]]'''</dt><dd class="note">Use of '''sleep''' within compiled [[SQF]] scripts/[[function]]s is not possible in ArmA v1.08. It will return an error '''Generic error in expression''', whenever you try to [[call]] such [[function]]. In order to make use of delays like this, use [[exec]], [[execVM]], [[spawn]].</dd>
+
<dt class="note">[[User:Sbsmac|Sbsmac]]<dd class="note">The comment above is a little misleading. The game engine appears to work by processing frames and then checking to see whether scripts are available to execute.  Sleep causes the script/function to be suspended until at least the specified time has elapsed.  To wait for the next frame, or give other scripts a chance to run, use Sleep 0.001.  
−
<!-- Note Section END -->
+
 
 +
<dd class="notedate">Posted on July 16, 2007 - 00:13
 +
<dt class="note">[[User:Inkompetent|Inkompetent]]<dd class="note">For scripts called by the [[Armed_Assault:_EventHandlers_List#Init|Init Event Handler]] the first sleep command will suspend the script at the briefing screen at the start of a mission. The script will continue after the briefing screen, when actually "in game".
 +
 
 +
<dd class="notedate">Posted on October 18, 2014 - 21:24 (UTC)</dd>
 +
<dt class="note">[[User:AgentRevolution|AgentRevolution]]</dt>
 +
<dd class="note">
 +
For server scripts, if you are creating "while true" timers, it is best to use [[uiSleep]] instead, as the sleep from that command is not slowed down by simulation / server lag, so the timers will execute at intervals that are much closer to real time, even under heavy lag.
 +
</dd>
 
</dl>
 
</dl>
 +
<!-- DISCONTINUE Notes -->
  
−
<h3 style="display:none">Bottom Section</h3>
+
{{GameCategory|arma2|Scripting Commands}}
−
[[Category:Scripting Commands|SLEEP]]
+
{{GameCategory|arma3|Scripting Commands}}
−
[[Category:Scripting Commands ArmA|SLEEP]]
+
{{GameCategory|tkoh|Scripting Commands}}

Latest revision as of 11:27, 18 January 2021

Introduced with Armed Assault version 1.001.00
Hover & click on the images for descriptions

Description

Description:
Suspends code execution for given time in seconds. The sleep precision is given by a framerate, the delay given is the minimal delay expected. Must be called inside of a context which is interruptible, i.e. a script executed by execVM or spawn.
ⓘ
  • this command will suspend the code for at least the given amount of time, and can be way more if the script scheduler is busy.
  • this command will suspend the script as the game gets paused in single player (and will resume with it). To avoid this, use uiSleep.


Syntax

Syntax:
sleep delay
Parameters:
delay: Number - in seconds. Negative values will not be considered.
Return Value:
Nothing

Examples

Example 1:
[] spawn { sleep 5; hint "after (at least) 5 seconds..."; };
Example 2:
sleep 5 + random 10; // incorrect - will only sleep for 5 seconds, as it will be interpreted as (sleep 5) (+(random 10)) sleep (5 + random 10); // correct
Example 3:
if (isMultiplayer) then { uiSleep 3; // more precise in (non-pausable) multiplayer } else { sleep 3; // sleep gets paused as the game is, usually wanted behaviour };

Additional Information

See also:
uiSleepwaitUntilcanSuspendexecVMspawnsleep vs uiSleepControl Structures
Groups:
Program Flow

Notes

i
Only post proven facts here. Report bugs on the Feedback Tracker and discuss on the Arma Discord or on the Forums.

+ Add Note (Help)

Notes

Posted on December 20, 2006 - 19:53
CrashDome
Sleep suspends both SQF functions and SQF scripts. In functions, the calling script is still in suspension due to waiting for a return from the call command. The game engine will continue, however. See Function for more detail.
Posted on February 12, 2007 - 20:16
Kronzky
Sleep durations between .0005 and .02 will cause the same delay (roughly .02 seconds).
Delays of .0005 and less have no effect (ie, the sleep call will return immediately).
Sbsmac
The comment above is a little misleading. The game engine appears to work by processing frames and then checking to see whether scripts are available to execute. Sleep causes the script/function to be suspended until at least the specified time has elapsed. To wait for the next frame, or give other scripts a chance to run, use Sleep 0.001.
Posted on July 16, 2007 - 00:13
Inkompetent
For scripts called by the Init Event Handler the first sleep command will suspend the script at the briefing screen at the start of a mission. The script will continue after the briefing screen, when actually "in game".
Posted on October 18, 2014 - 21:24 (UTC)
AgentRevolution
For server scripts, if you are creating "while true" timers, it is best to use uiSleep instead, as the sleep from that command is not slowed down by simulation / server lag, so the timers will execute at intervals that are much closer to real time, even under heavy lag.
Retrieved from "https://community.bistudio.com/wiki?title=sleep&oldid=211055"