setOvercast: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - ">Posted on August ([0-9]{1}), ([0-9]{4})" to ">Posted on $2-08-0$1")
m (Text replacement - "[] spawn" to "0 spawn")
 
(3 intermediate revisions by 2 users not shown)
Line 29: Line 29:
An overcast setting of zero means clear (sunny) weather, and one means storms and rain are very likely. Higher overcast values also result in higher [[wind]] speeds.
An overcast setting of zero means clear (sunny) weather, and one means storms and rain are very likely. Higher overcast values also result in higher [[wind]] speeds.


|mp= Each client and the server can have differing overcast values.{{Feature|arma3|In {{arma3}} weather values are periodically synchronised with the server.}}
|mp= '''Pre {{arma3}}:''' Each client and the server can have differing overcast values. {{Feature|arma3|In {{arma3}} weather values are periodically synchronised with the server.}}


|s1= time [[setOvercast]] overcast
|s1= time [[setOvercast]] overcast


|p1= time: [[Number]] - In seconds
|p1= time: [[Number]] - in seconds


|p2= overcast: [[Number]] - Range 0 to 1
|p2= overcast: [[Number]] - in range 0..1


|r1= [[Nothing]]
|r1= [[Nothing]]


|x1= <sqf>50 setOvercast 0.5;</sqf>
|x1= <sqf>60 setOvercast 0.5;</sqf>


|seealso= [[overcast]] [[nextWeatherChange]] [[simulSetHumidity]]
|seealso= [[overcast]] [[nextWeatherChange]] [[simulSetHumidity]]
}}
}}


<dl class="command_description">
{{Note
 
|user= Hardrock
<dt><dt>
|timestamp= 20060804140000
<dd class="notedate">Posted on 2006-08-04 - 12:00</dd>
|text= ''Notes from before the conversion:''
<dt class="note">[[User:Hardrock|hardrock]]</dt>
<dd class="note">''Notes from before the conversion:''


Use [[setRain]] if you want to make sure it rains.
Use [[setRain]] if you want to make sure it rains.
</dd>
}}
 
<dt><dt>
<dd class="notedate">
<dt class="note">[[User:Ceeeb|Ceeeb]]</dt>
<dd class="note">Only one script command induced weather change (either setOvercast or [[setFog]]) can be happening at a time. Starting a new weather change will immediately halt the current weather change. [[setRain|SetRain]] changes are independent and can occur simultaneously to a weather change.</dd>


{{Note
|user= Ceeeb
|timestamp= 20070420042400
|text= Only one script command induced weather change (either setOvercast or [[setFog]]) can be happening at a time. Starting a new weather change will immediately halt the current weather change. [[setRain|SetRain]] changes are independent and can occur simultaneously to a weather change.
}}


<dt><dt>
{{Note
<dd class="notedate">
|user= DnA
<dt class="note">[[User:Joris|Joris]]</dt>
|timestamp= 20130814112200
<dd class="note">[[Arma 3|Arma 3]]'s volumetric clouds cannot be instantly changed (it would take up to a few seconds to do a full recompute). Therefore, ''0 setOvercast 0'' will not have the desired effect. You can use [[skipTime|skipTime]] to get to the desired cloud coverage.
|text= {{arma3}}'s volumetric clouds cannot be instantly changed (it would take up to a few seconds to do a full recompute). Therefore, ''0 setOvercast 0'' will not have the desired effect. You can use [[skipTime|skipTime]] to get to the desired cloud coverage.


<br><br>
<br><br>
NOTE: To get instant, seamless overcast change to overcast 1 advance the time 24 hours with [[skipTime]] while setting overcast transition time to 86400 seconds (24 hours) - [[User:Killzone_Kid|Killzone_Kid]]
NOTE: To get instant, seamless overcast change to overcast 1 advance the time 24 hours with [[skipTime]] while setting overcast transition time to 86400 seconds (24 hours) - [[User:Killzone_Kid|Killzone_Kid]] (12:08, 15 August 2013)


<sqf>86400 setOvercast 1;
<sqf>
86400 setOvercast 1;
skipTime 24;
skipTime 24;


Line 74: Line 73:
skipTime -24;
skipTime -24;
86400 setOvercast 1;
86400 setOvercast 1;
skipTime 24;</sqf>
skipTime 24;
</dd>
</sqf>
}}


<dt><dt>
{{Note
<dd class="notedate">
|user= Killzone_Kid
<dt class="note">[[User:Killzone_Kid|Killzone_Kid]]</dt>
|timestamp= 20131028110600
<dd class="note">With removal of [[simulSetHumidity]], in order to add instant cloud cover, execute [[simulWeatherSync]] with delay (for now):
|text= With removal of [[simulSetHumidity]], in order to add instant cloud cover, execute [[simulWeatherSync]] with delay (for now):
<sqf>skipTime -24;
<sqf>
skipTime -24;
86400 setOvercast 1;
86400 setOvercast 1;
skipTime 24;
skipTime 24;
0 = [] spawn {
0 = 0 spawn {
sleep 0.1;
sleep 0.1;
simulWeatherSync;
simulWeatherSync;
};</sqf>
};
</sqf>
There is slight freeze with simul command.
There is slight freeze with simul command.
</dd>
}}


<dt><dt>
{{Note
<dd class="notedate">
|user= Adanteh
<dt class="note">[[User:Adanteh|Adanteh]]</dt>
|timestamp= 20150821195800
<dd class="note">Delay in [[Arma 3|Arma 3]] doesn't work for quick changes. Using 120 [[setOvercast]] 1 only reaches full overcast after about 50 minutes. Using [[setTimeMultiplier]] does speed up the overcast, but it doesn't render any clouds. You will need to [[skipTime]] or [[forceWeatherChange]] to render clouds if you want it to happen within the hour.</dd>
|text= Delay in {{arma3}} doesn't work for quick changes. Using 120 [[setOvercast]] 1 only reaches full overcast after about 50 minutes.
Using [[setTimeMultiplier]] does speed up the overcast, but it doesn't render any clouds.
You will need to [[skipTime]] or [[forceWeatherChange]] to render clouds if you want it to happen within the hour.
}}


<dt></dt>
{{Note
<dd class="notedate">Posted on May 4, 2016 - 22:41 (UTC)</dd>
|user= AgentRev
<dt class="note">[[User:AgentRevolution|AgentRev]]</dt>
|timestamp= 20160505004100
<dd class="note">
|text= Actual transition time is inversely proportional to the [[timeMultiplier]]. For example, a time of 7200 (2 hours) and a timeMultiplier of 2 will result in a real-life transition time of 7200 / 2 = 3600 (1 hour).<br>
Actual transition time is inversely proportional to the [[timeMultiplier]]. For example, a time of 7200 (2 hours) and a timeMultiplier of 2 will result in a real-life transition time of 7200 / 2 = 3600 (1 hour).<br>
In case of overcast, a timeMultiplier > 1 will cause gradual desyncing of the cloud cover with the [[overcast]] value, so it is advised that you multiply the transition time by the multiplier, i.e. :
In case of overcast, a timeMultiplier > 1 will cause gradual desyncing of the cloud cover with the [[overcast]] value, so it is advised that you multiply the transition time by the multiplier, i.e. :
<sqf>(7200 * timeMultiplier) setOvercast 1</sqf>
<sqf>(7200 * timeMultiplier) setOvercast 1</sqf>
</dd>
}}
 
</dl>

Latest revision as of 21:24, 2 September 2024

Logo A0.png1.00ofpe logo.png1.00Logo A1 black.png1.00Logo A2.png1.00A2 OA Logo.png1.50tkoh logo small.png1.00Arma 3 logo black.png0.50
LELocal
Hover & click on the images for description

Description

Description:
Set overcast to given value smoothly during given time (in seconds). Zero time means immediate change. An overcast setting of zero means clear (sunny) weather, and one means storms and rain are very likely. Higher overcast values also result in higher wind speeds.
Multiplayer:
Pre Arma 3: Each client and the server can have differing overcast values.
Arma 3
In Arma 3 weather values are periodically synchronised with the server.
Groups:
Environment

Syntax

Syntax:
time setOvercast overcast
Parameters:
time: Number - in seconds
overcast: Number - in range 0..1
Return Value:
Nothing

Examples

Example 1:
60 setOvercast 0.5;

Additional Information

See also:
overcast nextWeatherChange simulSetHumidity

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
Hardrock - c
Posted on Aug 04, 2006 - 14:00 (UTC)
Notes from before the conversion: Use setRain if you want to make sure it rains.
Ceeeb - c
Posted on Apr 20, 2007 - 04:24 (UTC)
Only one script command induced weather change (either setOvercast or setFog) can be happening at a time. Starting a new weather change will immediately halt the current weather change. SetRain changes are independent and can occur simultaneously to a weather change.
DnA - c
Posted on Aug 14, 2013 - 11:22 (UTC)
Arma 3's volumetric clouds cannot be instantly changed (it would take up to a few seconds to do a full recompute). Therefore, 0 setOvercast 0 will not have the desired effect. You can use skipTime to get to the desired cloud coverage.

NOTE: To get instant, seamless overcast change to overcast 1 advance the time 24 hours with skipTime while setting overcast transition time to 86400 seconds (24 hours) - Killzone_Kid (12:08, 15 August 2013)
86400 setOvercast 1; skipTime 24; // to remain on the same date: skipTime -24; 86400 setOvercast 1; skipTime 24;
Killzone_Kid - c
Posted on Oct 28, 2013 - 11:06 (UTC)
With removal of simulSetHumidity, in order to add instant cloud cover, execute simulWeatherSync with delay (for now):
skipTime -24; 86400 setOvercast 1; skipTime 24; 0 = 0 spawn { sleep 0.1; simulWeatherSync; };
There is slight freeze with simul command.
Adanteh - c
Posted on Aug 21, 2015 - 19:58 (UTC)
Delay in Arma 3 doesn't work for quick changes. Using 120 setOvercast 1 only reaches full overcast after about 50 minutes. Using setTimeMultiplier does speed up the overcast, but it doesn't render any clouds. You will need to skipTime or forceWeatherChange to render clouds if you want it to happen within the hour.
AgentRev - c
Posted on May 05, 2016 - 00:41 (UTC)
Actual transition time is inversely proportional to the timeMultiplier. For example, a time of 7200 (2 hours) and a timeMultiplier of 2 will result in a real-life transition time of 7200 / 2 = 3600 (1 hour).
In case of overcast, a timeMultiplier > 1 will cause gradual desyncing of the cloud cover with the overcast value, so it is advised that you multiply the transition time by the multiplier, i.e. :
(7200 * timeMultiplier) setOvercast 1
Retrieved from "https://community.bistudio.com/wiki?title=setOvercast&oldid=369059"