setOvercast: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<dl class="command_description"> <dd class="notedate">" to "<dl class="command_description"> <dt></dt> <dd class="notedate">") |
Lou Montana (talk | contribs) m (Text replacement - " <dd class="notedate">" to " <dt><dt> <dd class="notedate">") |
||
Line 26: | Line 26: | ||
<dl class="command_description"> | <dl class="command_description"> | ||
<!-- Note Section BEGIN --> | <!-- Note Section BEGIN --> | ||
<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]]<dd class="note">''Notes from before the conversion:'' | ||
Line 32: | Line 32: | ||
Use [[setRain]] if you want to make sure it rains. | Use [[setRain]] if you want to make sure it rains. | ||
<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]]<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><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]]<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. | ||
Line 49: | Line 49: | ||
[[skipTime]] 24; | [[skipTime]] 24; | ||
</code> | </code> | ||
<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]]<dd class="note">With removal of [[simulSetHumidity]], in order to add instant cloud cover, execute [[simulWeatherSync]] with delay (for now): | ||
Line 60: | Line 60: | ||
};</code> | };</code> | ||
There is slight freeze with simul command. | There is slight freeze with simul command. | ||
<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]]<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. |
Revision as of 00:10, 6 April 2021
Description
- Description:
- Description needed
- Multiplayer:
- Each client and the server can have differing overcast values.
- Groups:
- Environment
Syntax
- Syntax:
- Syntax needed
- Parameters:
- time: Number - In seconds
- overcast: Number - Range 0 to 1
- Return Value:
- Return value needed
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_Kid
86400 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