Obs:
If the wind strength is ever exactly 0, all wind effects become disabled for the rest of the mission, even if the wind is subsequently increased by either the in built weather system or script commands. The returned value of windStr continues to change as expected, but no environmental effects are observed (moving vegetation and clouds), and the wind vector remains at [0,0,0].
Exp:
Wind effects and wind vector should always reflect the current wind strength.
Mission weather method:
Script method:
Tested using Dev build 1.21.124754
Only tested in the mission editor.
User tortuosit here, cannot login with that account any more... :-(
There are also problems with setwind array:
[setWind]
Also wind vector values should be limited to like 12 beaufort, i.e. ~30m/s.
[n setGusts [0-1]]:
Does it work at all? I see no effect.
Another observation: If you do
setwind [10,10,true];
1000 setwindstr 0;
the wind immediately stops with the second command, i.e. you won't see the strong wind set first.
My workaround currently is to use a moderate setwind array at init and then keep the windstr always =>0.01.
I avoid using setwind array in scripting. It can create stronger wind, BUT can never change seemless.