setRain: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "\|game([0-9]) ?= (.+) \|version([0-9]) ?= (.+) " to "|game$1= $2 |version$3= $4 ")
m (Text replacement - "</dd> </dl>" to "</dd> </dl>")
(4 intermediate revisions by the same user not shown)
Line 31: Line 31:
A rain density of zero is no rain, one is maximum rain. Rain is not possible when [[overcast]] is less than 0.7.
A rain density of zero is no rain, one is maximum rain. Rain is not possible when [[overcast]] is less than 0.7.


{{Feature|arma3 | Since {{arma3}} this command is multiplayer synchronised:
{{Feature | arma3 | Since {{arma3}} this command is multiplayer synchronised:
* If executed on server, the changes will propagate globally.
* If executed on server, the changes will propagate globally.
* If executed on client, the effect is temporary and will soon change to the server setting.
* If executed on client, the effect is temporary and will soon change to the server setting.
Line 45: Line 45:


|r1= [[Nothing]]
|r1= [[Nothing]]
 
 
|x1= <code>60 [[setRain]] 1;</code>
|x1= <code>60 [[setRain]] 1;</code>


Line 56: Line 56:


<dl class="command_description">
<dl class="command_description">
<dt></dt>
<dt></dt>
<dd class="notedate">Posted on December 15, 2015 - 14:31 (UTC)</dd>
<dd class="notedate">Posted on December 15, 2015 - 14:31 (UTC)</dd>
Line 62: Line 63:
[[setTimeMultiplier]] does '''not''' affect transition time.
[[setTimeMultiplier]] does '''not''' affect transition time.
</dd>
</dd>
<dt><dt>
<dt><dt>
<dd class="notedate">Posted on November 16, 2016 - 22:06 (UTC)</dd>
<dd class="notedate">Posted on November 16, 2016 - 22:06 (UTC)</dd>
Line 68: Line 70:
Using '''Example 2''' on dedicated server might need additional interference on JIP clients. The reason is that JIP has [[rain]] value > 0 slowly changing to 0. To force client to sync one can execute this on client: <code>[[skipTime]] 1; [[skipTime]] -1;</code>
Using '''Example 2''' on dedicated server might need additional interference on JIP clients. The reason is that JIP has [[rain]] value > 0 slowly changing to 0. To force client to sync one can execute this on client: <code>[[skipTime]] 1; [[skipTime]] -1;</code>
</dd>
</dd>
</dl>
</dl>

Revision as of 17:10, 13 June 2021

Hover & click on the images for description

Description

Description:
Sets rain density smoothly over the given transition time. A transition time of zero means an immediate change. A rain density of zero is no rain, one is maximum rain. Rain is not possible when overcast is less than 0.7.
Arma 3
Since Arma 3 this command is multiplayer synchronised:
  • If executed on server, the changes will propagate globally.
  • If executed on client, the effect is temporary and will soon change to the server setting.
Minimum overcast needed for rain in Arma 3 is 0.5.
Multiplayer:
Prior to Arma 3, each client and the server could have different rain values.
Groups:
Environment

Syntax

Syntax:
time setRain rain
Parameters:
time: Number - Transition time in seconds to the new value
rain: Number - New rain value in range 0 to 1.
Return Value:
Nothing

Examples

Example 1:
60 setRain 1;
Example 2:
Force no rain: 0 setRain 0; forceWeatherChange; 999999 setRain 0;

Additional Information

See also:
overcastsetOvercastrainnextWeatherChangeforceWeatherChangesetFog

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 December 15, 2015 - 14:31 (UTC)
Zapat
setTimeMultiplier does not affect transition time.
Posted on November 16, 2016 - 22:06 (UTC)
Killzone Kid
Using Example 2 on dedicated server might need additional interference on JIP clients. The reason is that JIP has rain value > 0 slowly changing to 0. To force client to sync one can execute this on client: skipTime 1; skipTime -1;