We asked for them during the Aleutians FSO for filming.....was told no.
Reason: Wouldn't be fair as we could practice flying in wartime conditions.
May have changed but?
Strip
Well they post the settings in the rules...far in advance for the entire scenario, and wind direction is modified and posted typically a week in advance...
If changes are made to the rules either after the beta or during the scenario run, they are posted immediately as a rules modification...in the change log.
I would think that as settings become known and or changed, it would be a simple matter to make the change and save the file as a designer and then upload the changed file and issue an update.
Aside from weather, I am more bothered by having to change the dozens and dozens of other settings such as which base belongs to which side, which fields are opened and which are closed, which task groups are enabled or disabled, clock time etc...
It would seem logical that a Special Events Terrain Settings File could be and should be part of the game, and it should be savable, nameable etc...and loadable in a minimal series of mouse clicks...
ie Settings -> Load File -> Select File -> OK
Under the present regime, the user can modify, save and then load hardness, arena settings fields etc...but it is an all manual affair to modify the settings in these categories, and further, each of the sub elements of the arena setup are modified, saved and loaded separately...further still, you cannot have more than one blind settings file saved for any of the sub elements. In other words you cannot save multiple settings files such CoralSea_default.***, CoralSea_Frame1.***, CoralSea_Frame2.*** etc.
When a change is made to an arena setup you end up with 3 sub files in your terrain folder with the file extensions *.fld, *.pln, *.dod for Fields, Planes and Down Time / Hardness...
Wind is never saved and must be manually configured every time you load up the offline terrain.
To me in this modern age of computers that having the ability to edit settings, save them to a single settings file, save multiple versions and be able to distribute them is a no brainer.
Oneway
