weyne/dcs_liberation
1
0
Fork 0
mirror of https://github.com/dcs-liberation/dcs_liberation.git synced 2025-11-10 14:22:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

be more precise about the iads_config in the campaign yaml

RndName 2022-11-08 18:48:29 +01:00
parent bad2cfea4a
commit f6d8d9c0e8
1 changed files with 23 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
Custom-campaigns.md

@ -81,7 +81,29 @@ A best practice to follow is to set up one base per side as a transit hub. This
_Will be available in DCS Liberation 6.0 with Campaign Version 10.2_\
Liberation can automatically generate the IADS network for you but if you want to have more control about the network and which assets are connected with each other it is possible to define the whole IADS network in the campaign.yaml. The iads configuration will only be used when the campaign supports the advanced iads (set `advanced_iads` to true) and the checkbox to use the Advanced mode is checked during campaign generation.
To define the iads network in the campaign.yaml one has to add all connections to the `iads_config` property. Every primary node (SAM, EWR, Command Center, Naval Unit) which should participate to the network has to be added to the list with the exact Group Name used in the campaign.miz. AWACs should not be added to this list!. Every primary node can have 0..N connections (Comms, Power Source, Point Defense) which have to be added as a list to the primary node with the exact group name used in the campaign.miz. If no connections are added to a primary node it will participate to the IADS Network without requiring Comms or Power (equal to the functionality of the Basic mode).
To define the iads network in the campaign.yaml one has to add all connections to the `iads_config` property. Every primary node which should participate to the network has to be added to the list with the exact Group Name used in the campaign.miz.
Primary nodes are:
* SAM
* EWR
* Command Center
* Naval Unit (Carrier)
What should **not** be added to that list as primary node:
* AWACS
* Connection Nodes
* Power Sources
* Point Defense
These nodes (except AWACS which will be added automatically) will be added to the connected primary Nodes. Example of such a connection where `SAM1` has a connection to `CN1` and `PS1`:
```yaml
iads_config:
- SAM1: # Group name of the SAM, EWR or Command Center used in the campaign.miz
- CN1 # All connected nodes (Comms, Power, PointDefense)
- PS1 # Exact name of the connected group used in the campaign.miz
```
Every primary node can have 0..N connections (Comms, Power Source, Point Defense) which have to be added as a list to the primary node with the exact group name used in the campaign.miz. If no connections are added to a primary node it will participate to the IADS Network without requiring Comms or Power (equal to the functionality of the Basic mode). It is not possible to connect two Connection Nodes with each other. Every connection has to be between one Primary Node (see above) and a non-Primary Node.
Example of the IADS Configuration used in the Golan Heights campaign:
```yaml