Jump to navigation Jump to search
- 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.
- Each client and the server can have differing overcast values.
- time setOvercast overcast
- time: Number - in seconds
- overcast: Number - in range 0..1
- Return Value:
- Example 1:
- 60 setOvercast 0.5;
- Posted on Aug 04, 2006 - 14:00 (UTC)
- Notes from before the conversion: Use setRain if you want to make sure it rains.
- 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.
- 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)
- 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):
- 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.
- 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. :