|
From: Thorsten R. <tho...@sc...> - 2020-09-28 13:43:58
|
> What does it mean, for a weather scenario to omit the <local-weather> > section in its definition? Does it imply that weather scenario is not > applicable to local-weather, or something else? > > I’m asking because the launcher currently does: > > - a popup list of all weather scenarios > > - a toggle to enable advanced weather or not > > If you select for example ‘early morning fog’ (which has no > <local-weather> section in its XML), what should happen? I *think* Stuart is the person who knows the combined weather GUI (I've grudgingly accepted the need for it...) What *probably* is the point here is whether you're driving AW by the METAR string (as in the case of the morning fog) or whether you're calling a native AW scenario (that will be close to the METAR string, but really start the full offline weather engine including weather changes etc.) So what /should/ happen for morning fog is that the associated METAR string for the scenario gets parsed and dumped into properties, then AW starts in METAR mode, reads out the properties and starts a METAR-defined weather scenario. * Thorsten |