Why visibility suddenly to 1 hex?

[vionville]

The weather.dat is like this. The date is 10, Jun, and the visibility started in 3 hexes then drop to 2 then to 1? Although programmed weather is selected and the data said it should vary from 3 to 5.

10 6 1989 80 20 0 0 0 3 5
11 6 1989 100 0 0 0 0 3 4
12 6 1989 100 0 0 0 0 4 5
13 6 1989 100 0 0 0 0 4 5
14 6 1989 100 0 0 0 0 4 5
15 6 1989 80 20 0 0 0 2 4
16 6 1989 100 0 0 0 0 3 4
17 6 1989 100 0 0 0 0 2 3
18 6 1989 100 0 0 0 0 2 3
19 6 1989 70 30 0 0 0 1 2
20 6 1989 70 30 0 0 0 1 3
21 6 1989 60 40 0 0 0 2 3
22 6 1989 30 60 10 0 0 3 4
23 6 1989 40 60 0 0 0 4 5
24 6 1989 80 20 0 0 0 3 4
25 6 1989 100 0 0 0 0 4 5
26 6 1989 90 10 0 0 0 3 4
27 6 1989 95 5 0 0 0 4 5
28 6 1989 100 0 0 0 0 2 4
29 6 1989 100 0 0 0 0 2 3
30 6 1989 90 10 0 0 0 2 3
1 7 1989 80 20 0 0 0 2 3
2 7 1989 100 0 0 0 0 2 3
3 7 1989 100 0 0 0 0 3 4

[vionville]

B.T.W it is day turn.

[Liquid_Sky]

There is a random chance that visibility can drop due to fog/mist/dust. It usually only lasts for about a day, but can be for only a few turns. You will get a message in your command report saying visibility is worsening/improving.

[Volcano Man]

It looks like it shouldn't go to 0, but in your game turn select to view the weather report. If it says "none" in the dialog then it means that the weather.dat file with your dates in them for 1989 were added later, after you started. In that case there is a known issue where 1/2 way through the scenario it will drop to 1 hex vis.

I am not saying this is what it is, but it could be a possibility which comes from starting a scenario with "programmed weather" selected and with no weather data available.

[vionville]

But should that dust/fog effect be connected with a storm? If the weather data doesn't contain any value for storm, does that mean there is no possiblity for storm, or storm would happen for a random probability?

I now try it with a human vs human game (default scenario west germany invaded) with programe weather on. This time same problem returns, as visibility worsen on 15.00 (to 2 hexes). Before it could further worsen on, the dusk turn arrived, so the visibility down to 1 hex anyway.

This time obviously there is no problem with "no weather data avaiable", as this is a local game, not email one. So why it doesn't follow weather data?

The weather data for default scenario, you could see aaron's botb weather data is pratically a copy from original one, just change 1985 to 1989.

10 6 1985 80 20 0 0 0 3 5
11 6 1985 100 0 0 0 0 3 4
12 6 1985 100 0 0 0 0 4 5
13 6 1985 100 0 0 0 0 4 5
14 6 1985 100 0 0 0 0 4 5
15 6 1985 80 20 0 0 0 2 4
16 6 1985 100 0 0 0 0 3 4
17 6 1985 100 0 0 0 0 2 3
18 6 1985 100 0 0 0 0 2 3
19 6 1985 70 30 0 0 0 1 2
20 6 1985 70 30 0 0 0 1 3
21 6 1985 60 40 0 0 0 2 3
22 6 1985 30 60 10 0 0 3 4
23 6 1985 40 60 0 0 0 4 5
24 6 1985 80 20 0 0 0 3 4
25 6 1985 100 0 0 0 0 4 5
26 6 1985 90 10 0 0 0 3 4
27 6 1985 95 5 0 0 0 4 5
28 6 1985 100 0 0 0 0 2 4
29 6 1985 100 0 0 0 0 2 3
30 6 1985 90 10 0 0 0 2 3
1 7 1985 80 20 0 0 0 2 3
2 7 1985 100 0 0 0 0 2 3

[vionville]

I am reading user manual, there is no mention about "rain" or other element should drastically decrease visibility. All it said is that visibility should change only inside the range defined by weather data, with the exception of dusk/dawn/night/ turns of course.

[vionville]

And of course it mentioned storm. But if I am correct this weather data contains no value for storm.

[vionville]

No, it is not storm. If it is storm, it should drop to 1 hex immediately, not first to 2 then to 1. And I still have air mission avaiable. So why...

[Volcano Man]

So does it or does it not say "None" in the weather dialog of your scenario???

[Glenn Saunders]

There is enough unknown and confusion in the info in this thread so I'll resist adding further speculations and instead stick to KNOWN info.

You keep putting part of the Weather file in the post and this file does NOT have any storm data period - so NO STORMS will ever come into play. Disregard anything on storms in the rules in this instance.

Secondly - the weather file is read on the midnight turn, and you keep showing the file starting from June 10th, so the 3-5 value is for June 10th. A Scn that starts on June 10th will read the Vis Setting from the Scn file not the Weather.dat file. A Scn that starts on the 9th will read and obey the weather.dat for June 10th if the Programmed weather is ON in teh optional Rules. In default scns we check this to make sure we set Scn Vis and Ground conditions are in line with the info in the weather.dat file. But we don't have Scns in 1989 and there is no certainty the scn designer in this case picked values that agreed with the weather.dat file.

Finally, try not to read to much into GAME weather vs what you have in real life. In Real life VIS doesn't jump in 1 km steps to mtch the onset of rain or other conditions. And whether you see something or not at a range of 1, 3 or 5 km has factors other than fog or if it is raining coming into play. So best not to try and translate Vis =x into atmosphereic weather as we know it. There is Ground conditions, NORMAL, SOFT, MUD SNOW and FROZEN. There is Vis in Hexes 1, 2, 3, 4, and sometimes 5.

If you don't like the way the programed weather works, don't use it and the game will try to make logical assumptions based on starting poins defined in the Scn file - but it is still Vis = 1, 2 3 ect and ground = Normal, Soft ect. Whether you us the Optional Programmed weather or not - it is stil Vis = 1, 2 3 ect

Programmed weather came along when we had to exercise some control in what we wanted weather to be after the start of a Scn. Later, after this first implementation we had to come up with an addon to this - STORMS because these played a huge role in the Rzhev Campaign.

Hope this info helps a little.

Glenn