setOvercast: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - " <dl class="command_description"> <dt><dt>" to " <dl class="command_description"> <dt><dt>") |
Lou Montana (talk | contribs) m (Some wiki formatting) |
||
Line 1: | Line 1: | ||
{{RV|type=command | {{RV|type=command | ||
| ofp | |game1= ofp | ||
|version1= 1.00 | |||
|1.00 | |game2= ofpe | ||
|version2= 1.00 | |||
|game3= arma1 | |||
|version3= 1.00 | |||
|game4= arma2 | |||
|version4= 1.00 | |||
|game5= arma2oa | |||
|version5= 1.50 | |||
|game6= tkoh | |||
|version6= 1.00 | |||
|game7= arma3 | |||
|version7= 0.50 | |||
|gr1= Environment | |gr1= Environment | ||
Line 9: | Line 26: | ||
|eff= local | |eff= local | ||
| 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. | |descr= 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. | |||
|mp= Each client and the server can have differing overcast values.{{Feature|arma3|In {{arma3}} weather values are periodically synchronised with the server.}} | |||
| time | |s1= time [[setOvercast]] overcast | ||
|p1= time: [[Number]] - In seconds | |p1= time: [[Number]] - In seconds | ||
Line 17: | Line 37: | ||
|p2= overcast: [[Number]] - Range 0 to 1 | |p2= overcast: [[Number]] - Range 0 to 1 | ||
|r1=[[Nothing]] | |r1= [[Nothing]] | ||
|x1= <code>50 [[setOvercast]] 0.5</code> | |||
|seealso= [[overcast]], [[nextWeatherChange]], [[simulSetHumidity]] | |seealso= [[overcast]], [[nextWeatherChange]], [[simulSetHumidity]] | ||
}} | }} | ||
Line 28: | Line 48: | ||
<dt><dt> | <dt><dt> | ||
<dd class="notedate">Posted on August 4, 2006 - 12:00</dd> | <dd class="notedate">Posted on August 4, 2006 - 12:00</dd> | ||
<dt class="note">[[User:Hardrock|hardrock]]<dd class="note">''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> | <dt><dt> | ||
<dd class="notedate"> | <dd class="notedate"> | ||
<dt class="note">[[User:Ceeeb|Ceeeb]]<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. | <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> | |||
<dt><dt> | <dt><dt> | ||
<dd class="notedate"> | <dd class="notedate"> | ||
<dt class="note">[[User:Joris|Joris]]<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. | <dt class="note">[[User:Joris|Joris]]</dt> | ||
<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. | |||
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) | <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]] | |||
<code>86400 [[setOvercast]] 1; | <code>86400 [[setOvercast]] 1; | ||
[[skipTime]] 24; | [[skipTime]] 24; | ||
{{cc|to remain on the same date:}} | |||
[[skipTime]] -24; | [[skipTime]] -24; | ||
86400 [[setOvercast]] 1; | 86400 [[setOvercast]] 1; | ||
[[skipTime]] 24; | [[skipTime]] 24; | ||
</code> | </code> | ||
</dd> | |||
<dt><dt> | <dt><dt> | ||
<dd class="notedate"> | <dd class="notedate"> | ||
<dt class="note">[[User:Killzone_Kid|Killzone_Kid]]<dd class="note">With removal of [[simulSetHumidity]], in order to add instant cloud cover, execute [[simulWeatherSync]] with delay (for now): | <dt class="note">[[User:Killzone_Kid|Killzone_Kid]]</dt> | ||
<dd class="note">With removal of [[simulSetHumidity]], in order to add instant cloud cover, execute [[simulWeatherSync]] with delay (for now): | |||
<code>[[skipTime]] -24; | <code>[[skipTime]] -24; | ||
86400 [[setOvercast]] 1; | 86400 [[setOvercast]] 1; | ||
Line 60: | Line 90: | ||
};</code> | };</code> | ||
There is slight freeze with simul command. | There is slight freeze with simul command. | ||
</dd> | |||
<dt><dt> | <dt><dt> | ||
<dd class="notedate"> | <dd class="notedate"> | ||
<dt class="note">[[User:Adanteh|Adanteh]]<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. | <dt class="note">[[User:Adanteh|Adanteh]]</dt> | ||
</ | <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> | ||
<dt></dt> | <dt></dt> | ||
Line 82: | Line 105: | ||
<code>(7200 * [[timeMultiplier]]) [[setOvercast]] 1</code> | <code>(7200 * [[timeMultiplier]]) [[setOvercast]] 1</code> | ||
</dd> | </dd> | ||
</dl> | </dl> |
Revision as of 17:10, 12 June 2021
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:
- Each client and the server can have differing overcast values.
- Groups:
- Environment
Syntax
- Syntax:
- time setOvercast overcast
- Parameters:
- time: Number - In seconds
- overcast: Number - Range 0 to 1
- Return Value:
- Nothing
Examples
- Example 1:
50 setOvercast 0.5
Additional Information
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
- Posted on August 4, 2006 - 12:00
- hardrock
- Notes from before the conversion: Use setRain if you want to make sure it rains.
- Ceeeb
- 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.
- Joris
- 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_Kid86400 setOvercast 1; skipTime 24; // to remain on the same date: skipTime -24; 86400 setOvercast 1; skipTime 24;
- Killzone_Kid
- 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 = [] spawn { sleep 0.1; simulWeatherSync; };
There is slight freeze with simul command. - Adanteh
- 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.
- Posted on May 4, 2016 - 22:41 (UTC)
- AgentRev
-
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
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint version 1.00
- Operation Flashpoint: New Scripting Commands
- Operation Flashpoint: Scripting Commands
- Operation Flashpoint: Elite: Scripting Commands
- ArmA: Armed Assault: Scripting Commands
- Arma 2: Scripting Commands
- Arma 2: Operation Arrowhead: Scripting Commands
- Take On Helicopters: Scripting Commands
- Arma 3: Scripting Commands
- Command Group: Environment
- Scripting Commands: Local Effect