setFog: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Some wiki formatting) |
No edit summary |
||
Line 96: | Line 96: | ||
</dl> | </dl> | ||
{{Note | |||
|user= samatra | |||
|timestamp= 20220705052931 | |||
|text= Few notes about network behavior of the fog: | |||
* Fog is the only weather parameter that is ''somewhat'' properly network-synchronized by the engine. You can rely on it for both connected players and JIP players without jumping through hoops like other weather commands. | |||
* ''time'' is not synchronized over the network exactly, fog values changes will be linear over time where you run the command, while network-synced ''time'' will be non-linear, but in the end fog is still will be somewhat close between clients and servers, so its not much of a game breaker. | |||
* Say fog all 0 on both server and client, instantly setting fog on the server with <sqf inline>0 setFog 1</sqf> or even <sqf inline>0 setFog [1,1,1]</sqf> will not set it instantly on clients, but rather interpolate it there over few seconds (~10-15), non-linearly (slower the closer it gets to server values) | |||
* Setting ''fogValue'' to values above 1 is allowed where you run the command, but network sync will still clamp it to 1, so if you do <sqf inline>0 setFog 100</sqf>, clients will still interpolate ''fogValue'' to 1, including JIP, so make sure you don't set it above 1 if you expect consistent values between server and client for some calculations. | |||
}} |
Revision as of 06:29, 5 July 2022
Description
- Description:
- Smoothly change the fog over given time (in seconds). See also fogParams.
- Multiplayer:
- Before Arma 3, each client and the server could have different fog values
- Groups:
- Environment
Syntax
- Syntax:
- time setFog fog
- Parameters:
- time: Number - transition time to the new value
- fog: Number - fog density. Range 0..1
- Return Value:
- Nothing
Alternative Syntax
- Syntax:
- time setFog [fogValue, fogDecay, fogBase]
- Parameters:
- time: Number - transition time to the new value
- fogValue: Number - normal fog value that represents fog density at fogBase level. Range 0..1
- fogDecay: Number - decay of fog density with altitude. Range -1..1
- fogBase: Number - base altitude (ASL) of fog (in meters). Range -5000..5000
- Return Value:
- Nothing
Examples
- Example 1:
- 15 setFog 0.5;
- Example 2:
- Force no fog:
0 setFog 0; // forceWeatherChange; // change is immediate 999999 setFog 0;
- Example 3:
- 0 setFog [1, 0.01, 0];
- Example 4:
- Mountain fog, starts from 70m ASL and thickens more the higher you climb:
0 setFog [1, -1, 70];
- Example 5:
- Valley fog, starts from 60m ASL and thickens more the lower you descend: 0 setFog [1, 1, 60];
- Example 6:
- Fooooog on the waaaater: 0 setFog [1, 1, 0];
Additional Information
- See also:
- Arma 3: Improved Fog fog fogParams fogForecast nextWeatherChange forceWeatherChange setRain
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
- 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.
- Posted on December 15, 2015 - 14:32 (UTC)
- Zapat
- setTimeMultiplier DOES affect transition time.
- Posted on January 10, 2019 - 10:23 (UTC)
- killzone_kid
- A little information about how Alt Syntax works. The fogValue is normal fog value that could be set independently with original setFog command. fogBase is the ASL altitude at which the fog will start. 0 is the sea level. fogDecay is how defined the fog start is. The more defined, the denser is the fog. 1 (or -1) are the max values. If it is positive the fog will be generated below fogBase line, if negative, above it. If fogDecay is small, the fog will transition more smoothly from no fog to full fog, and because of that it will cross fogBase line by quite a lot, depending on how small is fogDecay value. Current values of fogDecay and fogBase can be retrieved with fogParams
- Posted on Jul 05, 2022 - 05:29 (UTC)
-
Few notes about network behavior of the fog:
- Fog is the only weather parameter that is somewhat properly network-synchronized by the engine. You can rely on it for both connected players and JIP players without jumping through hoops like other weather commands.
- time is not synchronized over the network exactly, fog values changes will be linear over time where you run the command, while network-synced time will be non-linear, but in the end fog is still will be somewhat close between clients and servers, so its not much of a game breaker.
- Say fog all 0 on both server and client, instantly setting fog on the server with 0 setFog 1 or even 0 setFog [1,1,1] will not set it instantly on clients, but rather interpolate it there over few seconds (~10-15), non-linearly (slower the closer it gets to server values)
- Setting fogValue to values above 1 is allowed where you run the command, but network sync will still clamp it to 1, so if you do 0 setFog 100, clients will still interpolate fogValue to 1, including JIP, so make sure you don't set it above 1 if you expect consistent values between server and client for some calculations.
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: Global Effect
- Scripting Commands: Server Execution