Weather Commands, Explained

The weather commands (Weather, Weather_Char, Clouds, Winds, Temperature, Baro_Pressure, and Visibility) collectively enable an adventure to create a local weather area. This topic is an overview of the weather commands, providing a brief description of how the weather commands work together to form the complex entity of a weather area.

Only one adventure weather area can exist at any given time. The Weather command controls the existence and defines the scope of the current adventure weather area. Each time a Weather command is executed, any existing weather area created by an adventure (whether the current adventure or a previous one) is deleted, and a new weather area is initialized. This behavior isn't dependent on whether the names of the adventure weather areas (as specified in the name parameter of the Weather command) match or not.

The Clouds, Winds, and Temperature commands specify parts of the weather area in terms of altitude layers. For example, there can be up to three layers of clouds, and each Clouds command specifies one layer. After three Clouds commands have been executed in the current weather area, all the possible cloud layers have been defined and additional Clouds commands have no effect. Even if a subsequent Clouds command specifies the same altitude region as an earlier Clouds command, the subsequent command does not replace the earlier one. Cloud layers are identified by layer numbers. The layer number does not have anything to do with the physical order in which the layers are displayed or presented in Flight Simulator; it simply identifies the layer for later commands. Alternatively, if a subsequent Clouds command specifies the same layer number, the subsequent layer replaces the earlier layer with the same layer number or deletes it if the Delete form of the command is used. Layers work in much the same way for Winds and Temperature commands.

The Weather_Char, Baro_Pressure, and Visibility commands specify global characteristics of the weather area. These commands aren't layer specific, so a subsequent command simply overrides an earlier command.