Self Inflicted Dynamic Campaign

“C:\Users\current_user\Documents\1C SoftClub\il-2 sturmovik cliffs of dover\missions\Single\“

1. "Campaign Creation Tool.exe", the tool used to transform a .mis file created in the Full Mission Builder into a dynamic campaign, or to roll back a backup of a previously flown campaign;
2. "SIDC.exe", the executable which will be invoked by the "SIDCMission.cs" script after every mission.This program will, based on the events which occurred during the previous mission, calculate the new unit rosters and positions of front markers and, based on the balance of power and pilot' s health, end and reset the campaign and the pilot’ s log book, or generate the subsequent mission, campaign progress report and briefings. This program only runs between missions which leaves the computer resources available for the actual process of simulating flight;
3. "SIDCMission.cs" is the script which will be executing while the mission is in progress, during the actual simulation. It records the events significant for the flow of events during a campaign: destruction of aircraft, static objects, vehicles and ships. It only contains the necessary minimum of code and, for this reason, will only cause a negligible loss of performance. It is, however, possible to add to the script in order to provide new functionality.

• A squadron should contain only a single air group. Only a single squadron should be placed on a single airfield. Attempting other approaches could cause irregular functioning of the mission generator. All the user sets for a particular air group , including pilot skill and weapon load outs, will apply to that air group throughout the campaign. After an air group is placed onto an airfield, one needs to set the first waypoint of that air group to “Take off” (Image 1). Nothing else pertaining to the path of the air group needs to be set.

• Since vehicle columns set on the map tend to disappear when passing through populated areas, and because it’s no fun to fly for half an hour in order to bomb a tank column which will never appear, vehicle column paths shouldn't be set to pass through towns and cities, but around them instead. The final few waypoints before the last one on the path of a vehicle column should be set close to each other. It is also important for the section defining the path of a vehicle column in the .mis file not to exceed two hundred waypoints. If this condition isn’ t met, the Campaign Creation Tool will warn the user.
• At least one side in the conflict must have at least a single squadron of bombers or fighter bombers for the campaign not to end immediately.
• Static objects which have nothing to do with factories, subcontractors, ports and airfields can be placed on the map at will.
• The usage of .cpp scripts wasn't’ t tested, but it shouldn't’ t present a problem as long as the proto .mis file is saved by the Full Mission Builder.
• If one wishes radar destruction missions to be generated, it is necessary to place radars on the map.
• An airfield is defined by placing four static tractors within two kilometers of the spot on the map onto which an air group is placed. For the allies, one should place the F. N Tractor onto the map, while for the axis one should use U. P- 107 Tractors. While the IL- 2 Sturmovik Cliffs of Dover simulator probably is aware of the positions of the airfields, tractors will help indicate the position of the airfields to the Self Inflicted Dynamic Campaign. Placing a few counter air artillery pieces near the airfield will also help, because the airfields will be targets for the opposing side (Image 2). By placing an air group on a place on the map from which it is possible for the air group to take off without placing the tractors near it, one indicates to the Self Inflicted Dynamic Campaign that such a place is an improvised airfield. An improvised airfield will not be a target for the enemy air power. This way, the campaign creator can model operations of smaller air groups from improvised airfields and influence the flow of the campaign.

• Ports can be defined by placing four static tractors within two kilometers of a port crane (Image 3). The simmer can bomb ports out of pure malice because their destruction will not influence the flow of the campaign.

• Factories are defined by placing four static bicycles of the appropriate side within a kilometer of a static object representing the product of the factory. Any static object that can be placed onto the map can be produced in a factory, but if one wishes to have products which can reinforce the army, one needs to see to it that the product is of the exact same type as the type serving in the army units. For instance, if a Spitfire IIa is serving in the squadrons, one needs to place a static Spitfire IIa onto the factory grounds (Image 4). If more static objects are placed onto the factory grounds, said factory will produce more products. One can have up to ten products in a single factory.

• Not every bit needed to build an aero plane was built by the main factories during World War II. Cockpit canopies and engines were, for instance, produced by subcontracting factories. For this reason, it is possible to define a subcontractor by placing four static bicycles within a kilometer of each other (Image 5), and then connecting the four bicycles with the main factory by a truck convoy, a train, or a ship. It is important that the way points at the opposite ends of the path of the means of transport are within a kilometer of the bicycles defining the subcontractor and the factory being connected. If a subcontractor is connected to several factories by means of transport, it will be producing subassemblies for several factories (Image 6). One subcontractor can produce subassemblies for up to ten factories.

• For the sector identifiers to be generated properly, it is necessary to select the “Battle area” option in the Full Mission Builder and make sure that every object placed onto the map is enveloped by the grid. Grid step size can be set to whatever seems appropriate (Image 7).