Dynamic-AI-Creator (DAC) V3.0 released

[SavageCDN]

^ not sure what you mean... so DAC wasn't working with older versions of Lingor? That seems odd.. are there other island where this is a known issue?

[7th_Serf]

nope DAC worked 100% fine on older Lingor versions (Internal version using the built in DAC in ACE). On Lingor 1.337 it stopped functioning sometimes (some things wouldn't spawn and some spawn areas would not restart after being deactivated). Started using the script version out of frustration and now everything spawns correctly. What was odd was that some spawns would work and others wouldn't - yet when I switched to external (script) they all worked all the time - deactivated spawn areas activated on trigger - that sort of thing.

The reason I noticed the problem was that I updated one of my older maps by setting it up on the newer version of Lingor and discovered that none of my spawns was working right - at first it seemed that only infantry was spawning - no vehicles or armor. Then I discovered that deactivated spawns wouldn't fire. I remade the map several times (changing and updating the spawn areas) to no avail - then I decided to put it back to the script version and it worked. It really is odd because the internal version of DAC works great on all other maps (I use @ACE all the time and DAC is built in).

[SavageCDN]

hmm.. I've always used the script version so never noticed. Hope you didn't spend too many hours pulling your hair out on that one!!

I've recently fallen in love (again) with ACE however and am starting to use it with ACRE in missions... so I have an ACE/DAC question for you

If I use the built-in DAC with ACE, and place a DAC_Extern logic on the map, it errors looking for a certain file under DAC\scripts\ I believe (I can verify from home PC).. I thought with the Extern all you needed was a DAC folder inside your mission folder with all the config.sqf files (ie: DAC_Unit_Config.sqf, DAC_Config_Creator.sqf, etc), and DAC_Intern was for the default configs (ie: 0,0,0,0 lots of Russians!!) and no other files needed?

Or do I have that wrong? Intern expects the DAC folder with just the config files and Extern wants basically the entire script version inside the mission folder?

Sorry if this is a dumb question I've never used the addon version before

[7th_Serf]

Dac internal just needs the game logic, everything in the scripts is included. If you check the instuctions it shows how to setup changed configs. By using the internal version of dac found in ace you will save about 1 meg in your mission size.

[Orcinus]

DAC_Intern in a Game Logic demotes the pbo version; DAC_Extern is for the script package in the mission folder. So if you want to use the DAC pbo from the ACE folder, use DAC_Intern. To use mission-specific configs (e.g., for units, camps, behaviour, etc.) place a game logic called DAC_Intern and in the init put, e.g.,

DAC_Single_Config = ["Camps","Behaviour","Weapons","Units"];

[Hellfire257]

DAC_Single_Config = ["Camps","Behaviour","Weapons","Units"];

Pop those files in your mission root for them to work as well. If you don't have clean copies of those files you can grab them from the DAC package in the OP:

\DAC_V3_c\DAC_pbo\DAC_Configs\DAC

[SavageCDN]

Ok thanks a lot guys...I went and re-read the manual for the pbo-specific stuff...looks pretty straight-forward not sure how I messed it up.

I think my problem was that I was using Intern with configs but I had them in a \DAC folder not in the mission root.

[cuel]

Hello

There are four different global settings related to ground support, which I have
unfortunately not described ... sorry

The standard settings are:



1. The "DAC_Radio_Dist" is the max range in which a group leader can reach groups for support (that what you mean).

Example: If u play your mission with DAC_AI_Level 3 and the average strength of the group (the group wich requesting support)
is 0.6 then the value for the "DAC_Radio_Dist" is: ((1000 * 3) * 0.6) = 1.800m

2. The "DAC_Alert_Dist" is the maximum distance, in which the groups provide support, without they being called for support.

3. The "Radio Time" is the time interval in which a leader tries to reach a group for ground support (sending a radio message).
The calculation with the above values would be: ((15 / 3) / (0.6 + 0.1)) = ~ 7 sec.

That means, the group leader will send each 7 sec. a support request to another DAC-group, within the "DAC_Radio_Dist", but nor each request is a hit ;-)

4. The "DAC_Radio_Count" specifies the maximum number of support groups that each group leader can request.

Maybe it's better to reduce this value (example): DAC_Radio_Count = "(DAC_AI_Level / 2)"

If u want to change one of the settings, write the new code into the init line of the DAC-logic, for example:

DAC_Radio_Dist = "((500 * DAC_AI_Level) * _skillgroup)";

Greeting
Silola

Is there a variable or something I could use to make sure that groups stay within their zone and not try to support other zones, only groups in their own zone?
Sort of like how UPSMON works, they don't "chase" units across the map, only within their zone

edit: No, the zones are not linked.

[SavageCDN]

Is there a variable or something I could use to make sure that groups stay within their zone and not try to support other zones, only groups in their own zone?
Sort of like how UPSMON works, they don't "chase" units across the map, only within their zone

edit: No, the zones are not linked.

Yes if you look in the DAC_Config_Behaviour file there is a variable in each case called _setSupport = [1,2]

The first number is what you are looking for - change it to _setSupport = [0,2] and units will no longer leave their zone to support (they will continue to support within the zone).

The second number is for artillery support and must match up with (for example) case 2 in DAC_Config_Arti


You can of course assign different behaviour configs to different zones - just change an entry in the DAC trigger in the editor (to match the appropriate behaviour case)
fun=["z1",[1,0,0],[4,2,20,4],[],[2,2,10,6],[],[0,0,1,0]] spawn DAC_Zone

[cuel]

Very useful, thanks Savage. Nice seeing you