Bug #12921

Weird Weather/Daytime behaviour in MP (AAS at least) with 72716

Added by BCA_Cat_Toaster over 4 years ago. Updated almost 3 years ago.

Status:Expired Start date:08/14/2010
Priority:Normal Due date:11/14/2011
Assignee:Dwarden % Done:

0%

Category:Server
Target version:-
Affected ArmA II version:1.55 BETA First affected build:
Reproduced by another DH user:No First affected ArmA II version:
I am using some Mods:No Single / Multi Player?:
I am using:OA only BIForumURL:
Reproducible for you:Yes NGUrl:
Related to content of DLC: WIKIurl:

Description

Since I (and others) updated to 72716 I got reports yesterday that people who are joining our server have nighttime (0000) while the original Mission-Time is 0500 for example. If the mission is using Fog, Rain etc they have a clear sky. Indeed we had some complaints "why your server only plays missions at night" while we hosted only one mission yesterday in 12 hours that was really playing at night.

I was able to reproduce that later in LAN and on our dedicated server (server tested with 72291 and 72716, happened both times as long as the client was using 72716) while it worked last evening for me at least for some hours without such problems. Now, even if I setup certain mission parameters for weather and time of day they get completely ignored, either its 0000 at night or 1200 day with a clear sky. Weather/Daytime Settings seem still to work in the Editor.

I reverted back to 72291 and everything is fine and working again.

aas100_UltimaRatio.Takistan.pbo - Demo Mission (519.6 kB) BCA_Cat_Toaster, 08/14/2010 06:45


Related issues

related to ARMA2 Community Issue Tracker - Bug #15635: Weather cannot be changed correctly (Commands broken) Assigned 12/05/2010 02/05/2011
related to ARMA2 Community Issue Tracker - Bug #23094: Fog is not sychronized in multiplayer - the actual viewdi... Assigned 08/03/2011 11/01/2011
related to ARMA2 Community Issue Tracker - Feature #2568: Add global weather and daytime Assigned 07/05/2009
related to ARMA2 Community Issue Tracker - Bug #13581: Mission Times differ seriously in multiplayer Feedback 09/08/2010

History

Updated by BCA_Cat_Toaster over 4 years ago

Find Mission attached, perhaps someone can reproduce it.

Updated by kju over 4 years ago

  • Due date set to 11/01/2010
  • Category set to Server
  • Status changed from New to Assigned
  • Assignee set to Dwarden
  • Affected ArmA II version changed from Please select... to 1.53 BETA

Would be good if someone can whip up a simple demo mission with repro steps.

Updated by BCA_Cat_Toaster over 4 years ago

Demo-Mission is already attached.

Step one: Just load it up in LAN and see if the Time/weather conditions match up with what you see (Parameters). Should be dull (light rain) and 15:45 (press O).
Step two: Before running the mission setup different Parameters for weather/daytime and see if they match with what you see after loading the missions.

While using 72716 of course. Just tried to reproduce it again in 72291 (which I thought was save) but now it works for daytime but not for the weather. It´s 15:45 but sunny, while it should rain (default weather is set to 0.75), but at least custom settings work for me while they get ignored completely in 72716.

Updated by kju over 4 years ago

  • Affected ArmA II version changed from 1.53 BETA to 1.55 BETA

Still actual. It seems that the server not always sync setDate/time with the clients.

Updated by kju over 3 years ago

  • Due date changed from 11/01/2010 to 11/14/2011
  • Status changed from Assigned to Feedback

I think after looking into this again, this is a mission problem.
It is either not correct use of setDate/skipTime or was not build with auto date sync for JIP in mind.

Updated by kju almost 3 years ago

  • Status changed from Feedback to Expired

Also available in: Atom PDF