Wena

Dynamic-AI-Creator [DAC] Version 3.0

________

ArmA2 1.05 required / Addons : MAP_EU V1.1
Warning, DAC has lots of functions, the documentation is accordingly comprehensive.
If you had a look at the 33-part demonstration it should be easier for you to understand the different topics.
If you want to create DAC-zones quickly with standard parameters I recommend you to read
the enclosed“quick start guide”. There you will learn how to build DAC zones in a few steps.

Content of the Zip:

DAC Readme.pdf
DAC Short instruction.pdf (short readme)
DAC AI Behavior Plan (infantry only)
DAC V3 Bonus Functionality (designed by MadRussian)
DAC Demonstration (Part 1-33)
DAC_Source.pbo + DAC_Sound.pbo (the standard DAC-Addons)
DAC folder (with all the config files, if you use the“DAC_extern” logic)
MAP_EU V1.1

Theme overview:
02
03
07
09
10
11
12
14
15
16
17
18
19
21
22
23
24
25
26
27
33
34

Advice to the DAC + prepare the DAC
The DAC script requestion for a zone
The selection of the side, the unit-,
behaviour- and camp configuration
Creating several DAC zones (copy)
Linking DAC zones
Create waypoint zones
Merge user defined waypoints
Assigninglogics to DAC zones
Activate / deactivate DAC zones
Reduce infantry groups
activate and configurate AI respawn
connect camps with zones
adjust zone values
(size, position and configuration)
Creating DAC zones mid mission
Deleting DAC zones mid mission
The DAC Artillery
The DAC Ground-support
Integrate editor-groups
Release DAC-groups
DAC-object generator
The configuration filesDAC_Config_Creator

39
40
43
44
47
49
51
53
54
55
56
57

DAC_Config_Units
DAC_Config_Behaviour
DAC_Config_Waypoints
DAC_Config_Camp
DAC_Config_Arti
DAC_Config_Events
DAC_Config_Marker
DAC_Config_Objects
DAC_Config_Sound
DAC_Config_Weapons
Thanksgivings
Attachment

# A hint to the DAC
This version of DAC 3.0 is still a Beta version. So keep in mind that errors might occurconsidering the beta
status. Additionally, DAC may not behave as intended.
It´s pretty much important though to always make sure to feed DAC with valid datas only.
Those ones are mostly stored in the different configuration-files. If problems occur so
you should feed the zone constellation within your mission with default datas (DAC_intern), at first.
It also might be helpful to deactivatecritical zones just for a test. You can do that by
defining false in the Conditions line of each zone. The respective Zone is no more active then.

# Preparing the DAC
Because the DAC in the Version 3.0 is more an Addon than a script resource, you should handle the pbo file
as any other addon/Mod file. Create a Mod folder or use an already existing one (that’s pretty much up to you,
but Irecommend to create an own DAC related Mod folder).
To get the DAC started or even initiated, you have to place a player on the map and name it "S1".
Then the DAC Logic also needs to be placed on the map (insert units - F1).
Insert units (F1) >>> Game-Logics >>> DAC >>> DAC_intern

The Game Logic DAC_intern is using, as the name already explains itself, intern configuration files.
The defaultbehaviour and default units are defined right in there. This variant is always the first choice if you
want to learn the DAC or even for a quick Test.
But if you are a professional already and want the total control about the configuration-files, which are
providing you a high grade of Adjustment, you’ve got to use the DAC_extern Logic. But this logic requires the
DAC Folder itself to be placedright into your Missions folder (DAC Folder is part of the Zip-file). In this case
DAC is expecting all configuration files right in this folder. Which settings are adjustable will be explained in
the sub item [The DAC-Configuration_files]. You will also learn there that there’s a further, third variant to
store configuration-files individually outside the main DAC resource.
OK, if...