Difference between revisions of "setRain"

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "{{Command " to "{{RV|type=command ")
m (Text replacement - "| mp =" to "|mp=")
Line 32: Line 32:
 
[[forceWeatherChange]];
 
[[forceWeatherChange]];
 
999999 [[setRain]] 0;</code>
 
999999 [[setRain]] 0;</code>
| mp = Pre-Arma 3, each client and the server could have different rain values. |Multiplayer=
+
|mp= Pre-Arma 3, each client and the server could have different rain values. |Multiplayer=
  
 
| [[overcast]], [[setOvercast]], [[rain]], [[nextWeatherChange]], [[forceWeatherChange]], [[setFog]]
 
| [[overcast]], [[setOvercast]], [[rain]], [[nextWeatherChange]], [[forceWeatherChange]], [[setFog]]

Revision as of 14:24, 25 January 2021

Hover & click on the images for description

Description

Description:
Description needed
Multiplayer:
Pre-Arma 3, each client and the server could have different rain values.
Groups:
Environment

Syntax

Syntax:
Syntax needed
Parameters:
time: Number - transition time to the new value in seconds
rain: Number - new rain value in range 0...1
Return Value:
Return value needed

Examples

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

Additional Information

See also:
See also needed

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;