|
Rich Dionne -> UV Campaign Editor Notes (6/9/2002 11:36:17 AM)
|
I'm putting together some usage notes to help you guys trying to create alternative UV scenario files. I'm not finished yet, but I did want to get some of the more important issues out to you now. I will try to have the complete document out soon. The main issue I wanted to cover here was saving files, and the limitations you will encounter. Here are the main points:
The first 20 scenario files are reserved. You cannot save over these files. In order to create a new scenario file, you must first save one of the first 20 scenario files as a new scenario file with a number greater than 20.
To create a new scenario from one of the reserved scenario files, click on the File menu item and select “Save As”. Select a scenario file number greater than 20, add a comment / name in the box provided, and click “Save Data Base in the Slot”. You can now edit your new scenario.
All reserved scenario files are not created equally, and their usefulness as new scenario starters will vary. First of all, many of the reserved scenarios have AI coding built into the UV EXE file to make them behave. This is particularly true of the short scenarios, where some extra AI prodding was required to make them go after desired objectives early. This is not as prevalent in the longer scenarios, where the main AI has some time to kick in. When you create a new scenario file from one of the existing reserved scenarios, any specialized AI coding will not carry over to the new scenario. The bottom line for this note is that the long campaign starting in May 42 and ending Dec 43 will make the best new scenario starter. Of course you can still try to create alternative scenarios starting with some of the shorter reserved scenarios, but AI performance and behavior will be more unpredictable.
Another important note: delay settings for ships, airgroups, and land units in reserved scenario files starting 1 Aug 42 or 15 June 43 are not used in the same way as other reserved scenario files. In most scenario files, the unit delay settings refer back to the starting date of that particular scenario, but for scenarios starting 1 Aug 42 or 15 June 43, the delay values refer back to a 1 May 42 date. For example, a delay setting of 100 in a scenario starting 1 Aug 42 means the unit in question will become available on 9 Aug 42, and not 9 Nov 42. The problem with creating files from reserved scenarios starting 1 Aug 42 or 15 June 43 is that the new scenario delay dates will now refer to the scenario starting date, and not back to 1 May 42, meaning that all delay values in the scenario will be incorrect and must all be adjusted manually. Confusing? Unfortunately, this is a remnant of the way the scenarios were originally created. The bottom line here is that you probably do not want to create new scenarios from reserved scenarios starting 1 Aug 42 or 15 June 43. Again, the reserved 1 May 42 campaign (17) is probably your best bet for alternative scenarios.
Hope this helps; I'll have more later...
Rich Dionne
|
|
|
|
