Jump to content


  • Content Count

  • Joined

  • Last visited

  • Medals

  • Medals

Posts posted by SavageCDN

  1. Just an FYI it appears they work with ACE but are not 100% compatible (ACE medic and healing system for example). Also ACRE will work but without any ACRE radios (148, 117) added to crates it leaves you with just your short range 343 radio.

    On the plus side our new dedi runs this mission quite well...still low FPS after 10-15 mins of mission start but as you said before with FSMs it is certainly playable. Now if I could only get people to download Dingor.... :p

  2. ?? - if you use DAC_Extern (denoting the script version) having only the config files in the mission folder cannot work at all because there won't be any of the scripts to which the configs relate.

    It is when using DAC_Intern [the PBO version] that you need only place configs in the mission folder, and then solely for those features that you wish to vary from default. And yes, I've seen an instance where setting a parameter in the config_creator did not change what DAC did when using the PBO version, though I've pretty much switched over completely to the script version for various reasons.

    I think that was my issue initially.. it seems using the PBO version with custom DAC_Config_Creator doesn't work well.. forcing me to add stuff to the init of the DAC Logic if I want to change anything from the defaults (ie: DAC_Comm_Value=[1,2,0] ). This gets a bit messy if I'm changing a lot of defaults in Config_Creator. Not sure if saving ~1MB of mission file size is worth the headache :)

    @tpM - I could be wrong but I don't think DAC has any way of adjusting the 'detection' range when it comes to AI and sounds.. you might have to look at another AI mod (believe GL4 has this feature)

  3. 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

  4. @friznet2: +1

    I don't play MP so can't comment on that aspect, but agree with everything else 200%.

    @all: apologies for the continued delay in releasing the HAC + DAC demo missions, but RL (work) is currently very time-consuming. Basically all is now working - thanks especially to Ryd & MadRussian - & I need to clean up & amalgamate various scripts controlling activation/inactivation of DAC zones, etc. I was hoping to finish a lightweight automatic medic script for the first demo, but probably better left til the second demo.

    @friznet2 - another +1 - I agree this is sorely missing in Arma (SP and MP) but would change the game entirely if MP-compatible

    @Orcinus - that is great to hear looking forward to the demo

  5. If your CPU is overheating I'd recommend two things:

    Open your case and make sure your CPU heatsink is securely attatched and that the CPU fan is running @ full RPM.. your mobo may have a BIOS setting for CPU fan speed - make sure it's set to Full or SuckAsMuchPowerAsPossible mode.

    Get a small but powerful fan, leave your case side open and setup the fan to point directly at the CPU/board. Not a permanent solution obviously but it might get you through a few days.

    Either way you shouldn't run your PC if it continues to overheat like that as you will burn out components

    Edit: right I will check this out over the next few days... won't be able to give it serious time until the weekend though

  6. I can confirm ALICE2 works on Fallujah running vanilla Arma2 CO. Where the problems arise are when other maps seem to conflict somehow (mentioned before), and with Fallujah, I believe civilians will only spawn out of one type of house (one of the 2 storey ones with the upper balcony... read this on the forums somewhere recently). Apparently this was done to conserve resources as there are a lot of enter-able buildings on that map. When I was testing this the other day I can see why people think it's not working as sometimes it's pretty quiet on the streets :)

  7. 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 :p

    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