skipTime: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
(Effects are Local)
m (weather change is not estimated, the clouds just jump about)
Line 9: Line 9:
____________________________________________________________________________________________
____________________________________________________________________________________________


| Skiptime duration is in hours.
| 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
 
Daytime is adjusted, weather change is estimated, no changes are made in any units.
 
The tide is also adjusted. |= Description
____________________________________________________________________________________________
____________________________________________________________________________________________


Line 57: Line 53:


<dd class="notedate"></dd>
<dd class="notedate"></dd>
<dt class="note">'''[[User:Ceeeb|Ceeeb]]'''</dt><dd class="note">In ArmA, skipTime does not actually estimate weather changes beyond moving the clouds across the sky. Weather counters continue as if no time has passed.</dd><dd class="note">In ArmA, [[setDate]] can be used instead of skiptime to change the time ''without'' the lower clouds jumping.</dd>
<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.[[SetDate|setDate]] 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>
<dd class="notedate">Posted on August 28, 2008</dd>

Revision as of 23:12, 30 August 2008

Hover & click on the images for description

Description

Description:
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.
Groups:
Uncategorised

Syntax

Syntax:
skipTime Hours
Parameters:
Hours: Number
Return Value:
Nothing

Examples

Example 1:
skipTime 5

Additional Information

See also:
See also needed

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

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!
skipTime is not to be confused with accTime.
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
Posted on Feb 25, 2007
Manny
Note that time can also be skipped "backwards", ie. you can provide negative values and jump back in time.
Posted on March 21, 2007
granQ
One second is roughly 0.00026.
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.setDate can be used instead of skiptime to change the time without the visual give-away of the lower clouds jumping.
Posted on August 28, 2008
BarmyArmy
Always always always wrap any calculation in brackets. skipTime seconds*3600 will acutally only do skipTime seconds, skipTime (seconds*3600) will achieve the desired result

Bottom Section