Difference between revisions of "skipTime"

From Bohemia Interactive Community
Jump to navigation Jump to search
m
m (Text replacement - "|Game version=" to "|Game version= |gr1= Environment |GROUP1= ")
Line 5: Line 5:
  
 
|1.00|Game version=
 
|1.00|Game version=
 +
 +
|gr1= Environment |GROUP1=
 +
 +
 
|serverExec= server |Exec=
 
|serverExec= server |Exec=
  

Revision as of 17:03, 18 September 2020

Template:Command

Notes

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

Bottom Section