If not, then the server is just syncing the engine value to all clients If that setting is on, the server will need updateWind so that ace weather is applied. I think that is overridden by useAceWeather, so it all hinges on that setting I can see no need to run updateWind on the server unless useAceWeather is activeīut will it update along with the forecast then? The wind is constant at mission start until the first serverController fires, that's when it starts jumping in small valuesĪnd eventually it'll reach high values because of the jumping Then on the clients updateWind sets the wind to those params With useAceWeather off, it just reads the actual wind and sets that as the params. My understanding is server controller handles syncing all clients. Would that not just be a feedback loop? Since the server controller is feeding fnc_getWind Not sure how that plays along with forecast set in eden shouldn't the serverController use fnc_getWind instead? So it's like a mismatch in timing between updating the GVAR and reading it? UpdateWind gets called every sec and uses ACE_wind (from getWind, that uses ACE_WIND_PARAMS) but since serverController uses the current wind it will slowly increase Ok it should be since useAceWeather is off, ACE_WIND_PARAMS is only set in fnc_serverController to current wind wind changes slowly at start, but once serverController has run a couple of times it's very off and extreme windsĪnd from what i can tell it only happens when useaceweather is offĬalling updateaceweather seems to stabilize itĪnd I triple checked the maths and it's right 😛 Yea it just feels like it's all connected somehow. This seems to suggest BI worked on improving weather sync about the same time as the weather module was created #help chatlog By default the update timer is 60s, so it can take up to 20 minutes before it gets very high On those missions, doing call CBA_fnc_addPerFrameHandler will increase the wind extremely fast, reaching unplayable values. On some missions, reasons unknown, the value will eventually get extremely high This is due to using vectorMagnitude on wind, but updateWind and getWind will jump between engines wanted values and ACE_WIND_PARAMS, most likely. Most likely Ace Weather (world data) shouldn't be synchronizing either, only setting the values on the server As for syncMisc, it requires some further investigation. Missions or servers with useAceWeather off needs to turn syncRain and syncWind off. In some recent patch, rain and wind synchronization seems to be done by the engineĬlients will overtime start using the value the server has.

Arma 3 sync really slow