Difference between revisions of "skipTime"

From Bohemia Interactive Community
Jump to navigation Jump to search
m (repaired link)
m (Text replacement - "[[daytime" to "[[dayTime")
(64 intermediate revisions by 15 users not shown)
Line 1: Line 1:
{{Command|= Comments
+
{{RV|type=command
____________________________________________________________________________________________
 
  
| ofp |= Game name
+
|game1= ofp
 +
|version1= 1.00
  
|1.00|= Game version
+
|game2= ofpe
 +
|version2= 1.00
  
|eff= local |= Effects in MP
+
|game3= arma1
____________________________________________________________________________________________
+
|version3= 1.00
  
| Skiptime duration is in hours. The time of day and tides are adjusted, but no changes are made in any units. If present, the lower level of clouds instantly jump to the position they would be in if time had passed normally.|= Description
+
|game4= arma2
____________________________________________________________________________________________
+
|version4= 1.00
  
| '''skipTime''' Hours|= Syntax
+
|game5= arma2oa
 +
|version5= 1.50
  
|p1= Hours: [[Number]] |= Parameter 1
+
|game6= tkoh
 +
|version6= 1.00
  
| [[Nothing]] |= Return value
+
|game7= arma3
____________________________________________________________________________________________
+
|version7= 0.50
 
 
|x1= <code>'''skipTime''' 5</code>  |= Example 1
 
____________________________________________________________________________________________
 
  
| |= See also
+
|serverExec= server
  
}}
+
|gr1= Time
  
<h3 style="display:none">Notes</h3>
+
|gr2= Environment
<dl class="command_description">
 
<!-- Note Section BEGIN -->
 
<dd class="notedate"></dd>
 
<dt class="note"></dt><dd class="note">
 
Here is a very useful function - great for giving a "campaign" feel to a running battle. Try this in your init.sqs file:
 
while(true) do {
 
skiptime 0.00333  ~0.1  }
 
  
This will make each day pass in around 12 minutes - great fun watching sunsets and the night sky!</dd>
+
|descr= Jumps the specified number of hours forward or backward.<br>The time of day and tides are adjusted, but no changes are made to any units. If present, the lower level of clouds instantly jump to the position they would be in if time had passed normally.
  
<dd class="notedate"></dd>
+
|mp= In {{arma3}} (around v1.14) [[skipTime]] executed on the server will get synced in 5 seconds or so with all the clients. It will also be [[Multiplayer Scripting#Join In Progress|JIP]] compatible. [[skipTime]] executed on a client will change time on client for about 5 seconds after which it will sync back to server time.<br>
<dt class="note"></dt><dd class="note">skipTime is not to be confused with [[accTime]].</dd>
+
For other games' behaviour, see {{HashLink|Multiplayer Scripting#Join In Progress}}.
  
<dd class="notedate"></dd>
+
|s1= [[skipTime]] duration
<dt class="note"></dt><dd class="note">Here is a useful piece of code that will enable the mission to skip forward to any given time, irrespective of what time it happens to be in the mission:
 
skipTime (_timeToSkipTo - [[daytime]] + 24 ) % 24
 
  
See also: [[a % b]]</dd>
+
|p1= duration: [[Number]] - Hours to skip. A positive value will create a forward time jump, a negative value will jump backwards.
  
<dd class="notedate">Posted on Feb 25, 2007</dd>
+
|r1= [[Nothing]]
<dt class="note">'''[[User:Manny|Manny]]'''</dt><dd class="note">Note that time can also be skipped "backwards", ie. you can provide negative values and jump back in time.</dd>
 
  
<dd class="notedate">Posted on March 21, 2007</dd>
+
|x1= <code>[[skipTime]] 5;</code>
<dt class="note">'''[[User:granQ|granQ]]'''</dt><dd class="note">One second is roughly 0.00026.</dd>
 
  
<dd class="notedate"></dd>
+
|x2= <code>[[skipTime]] (5/60); {{cc|be sure to use parentheses, otherwise here ([[skipTime]] 5)/60 will happen}}</code>
<dt class="note">'''[[User:Ceeeb|Ceeeb]]'''</dt><dd class="note">In ArmA & OFP, skipTime does not actually estimate weather changes beyond moving the clouds across the sky. Weather counters continue as if no time has passed. The [[setDate]] command can be used instead of skiptime to change the time ''without'' the visual give-away of the lower clouds jumping.</dd>
 
  
<dd class="notedate">Posted on August 28, 2008</dd>
+
|x3= <code>[[while]] {[[true]]} [[do]]
<dt class="note">'''[[User:BarmyArmy|BarmyArmy]]'''</dt><dd class="note">Always always always wrap any calculation in brackets.
+
{
 +
[[skipTime]] 0.00333;
 +
[[sleep]] 0.1; {{cc|smooth time transition}}
 +
};</code>
  
skipTime seconds*3600
+
|x4= <code>[[skipTime]] ((_timeToSkipTo - [[dayTime]] + 24) [[a % b|%]] 24); {{cc|skip forward to a specific time, irrespective of the current mission time}}</code>
  
will acutally only do skipTime seconds,  
+
|seealso= [[setDate]], [[accTime]], [[setTimeMultiplier]], [[timeMultiplier]]
 +
}}
  
skipTime (seconds*3600)
+
<dl class="command_description">
  
will achieve the desired result</dd>
+
<dt><dt>
 +
<dd class="notedate">
 +
<dt class="note">[[User:Ceeeb|Ceeeb]]</dt>
 +
<dd class="note">In ArmA & OFP, skipTime does not actually estimate weather changes beyond moving the clouds across the sky.
 +
Weather counters continue as if no time has passed.
 +
The [[setDate]] command can be used instead of skiptime to change the time ''without'' the visual give-away of the lower clouds jumping.</dd>
 +
 
 +
<dt><dt>
 +
<dd class="notedate">
 +
<dt class="note">[[User:Kju|kju]]</dt>
 +
<dd class="note">I cannot confirm this for OA 1.60 beta (85889):
 +
MP: Even though the immediate effect of skipTime is only local,
 +
the new time will propagate through the network after 30 seconds or so.
 +
Instead the [[date]], which includes time, is synced automatically for new JIP clients - NOT for present instances.
 +
So one has to apply skipTime on all instances in MP (server + all present clients).
 +
</dd>
 +
 
 +
<dt><dt>
 +
<dd class="notedate">
 +
<dt class="note">[[User:Killzone_Kid|Killzone_Kid]]</dt>
 +
<dd class="note">This command is blocking and in some cases it may take up to 1.5 seconds (probably depends on CPU) for it to calculate the changes to the environment, during which the game will microfreeze. It largely depends on weather changes, which are quite random. However one thing remains consistent, [[skipTime]] 24 hours is always almost instant. This is quite helpful when used in conjunction with commands such as [[setOvercast]] for instant and seamless effect. To try it yourself use this script:
 +
<code>[] [[spawn]] {
 +
[[for]] "_i" [[from]] 1 [[to]] 24 [[do]] {
 +
_time = [[diag_tickTime]];
 +
[[skipTime]] _i;
 +
[[diag_log]]  [_i, [[diag_tickTime]] - _time];
 +
[[sleep]] 3;
 +
};
 +
};</code>
 +
One of the results (results will vary depending on weather conditions):<br>
 +
<spoiler text="Show results">
 +
<pre>[1,1.44507]
 +
[2,1.46118]
 +
[3,1.33105]
 +
[4,1.396]
 +
[5,0.0310059]
 +
[6,1.37891]
 +
[7,1.4502]
 +
[8,1.37817]
 +
[9,1.37695]
 +
[10,1.37012]
 +
[11,1.448]
 +
[12,1.32593]
 +
[13,1.45508]
 +
[14,1.448]
 +
[15,0.0349121]
 +
[16,0.0368652]
 +
[17,1.25903]
 +
[18,1.38599]
 +
[19,1.4519]
 +
[20,0.052002]
 +
[21,0.0400391]
 +
[22,0.0490723]
 +
[23,1.35205]
 +
[24,0.0151367] // this is always the lowest</pre>
 +
</spoiler>
 +
</dd>
  
<!-- Note Section END -->
 
 
</dl>
 
</dl>
 
<h3 style="display:none">Bottom Section</h3>
 
[[Category:Scripting Commands|SKIPTIME]]
 
[[Category:Scripting Commands OFP 1.96|SKIPTIME]]
 
[[Category:Scripting Commands OFP 1.46|SKIPTIME]]
 
[[Category:Scripting Commands ArmA|SKIPTIME]]
 
[[Category:Command_Group:_Environment|{{uc:{{PAGENAME}}}}]]
 

Revision as of 01:03, 13 July 2021

Hover & click on the images for description

Description

Description:
Jumps the specified number of hours forward or backward.
The time of day and tides are adjusted, but no changes are made to any units. If present, the lower level of clouds instantly jump to the position they would be in if time had passed normally.
Multiplayer:
In Arma 3 (around v1.14) skipTime executed on the server will get synced in 5 seconds or so with all the clients. It will also be JIP compatible. skipTime executed on a client will change time on client for about 5 seconds after which it will sync back to server time.
For other games' behaviour, see Multiplayer Scripting - Join In Progress.
Groups:
TimeEnvironment

Syntax

Syntax:
skipTime duration
Parameters:
duration: Number - Hours to skip. A positive value will create a forward time jump, a negative value will jump backwards.
Return Value:
Nothing

Examples

Example 1:
skipTime 5;
Example 2:
skipTime (5/60); // be sure to use parentheses, otherwise here (skipTime 5)/60 will happen
Example 3:
while {true} do { skipTime 0.00333; sleep 0.1; // smooth time transition };
Example 4:
skipTime ((_timeToSkipTo - dayTime + 24) % 24); // skip forward to a specific time, irrespective of the current mission time

Additional Information

See also:
setDateaccTimesetTimeMultipliertimeMultiplier

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
Ceeeb
In ArmA & OFP, skipTime does not actually estimate weather changes beyond moving the clouds across the sky. Weather counters continue as if no time has passed. The setDate command can be used instead of skiptime to change the time without the visual give-away of the lower clouds jumping.
kju
I cannot confirm this for OA 1.60 beta (85889): MP: Even though the immediate effect of skipTime is only local, the new time will propagate through the network after 30 seconds or so. Instead the date, which includes time, is synced automatically for new JIP clients - NOT for present instances. So one has to apply skipTime on all instances in MP (server + all present clients).
Killzone_Kid
This command is blocking and in some cases it may take up to 1.5 seconds (probably depends on CPU) for it to calculate the changes to the environment, during which the game will microfreeze. It largely depends on weather changes, which are quite random. However one thing remains consistent, skipTime 24 hours is always almost instant. This is quite helpful when used in conjunction with commands such as setOvercast for instant and seamless effect. To try it yourself use this script: [] spawn { for "_i" from 1 to 24 do { _time = diag_tickTime; skipTime _i; diag_log [_i, diag_tickTime - _time]; sleep 3; }; }; One of the results (results will vary depending on weather conditions):
Show results