Jump to content

magnetar

Member
  • Content Count

    196
  • Joined

  • Last visited

  • Medals

Everything posted by magnetar

  1. Thanks spyderblack for your answer. Unfortunately it does not work. I have tested it with just a helo synced to a Combat Support Module (CAS) and it does not detect it. I only get, "No OPCOM instances found". It shows however in the Supports tablet but I cannot assign any waypoints in there... Could this be added as a future feature? Cheers :)
  2. Hi all, I was wondering if it could be possible to assign waypoints to a CAS unit when ordering it to perform a, for example, SAD mission. Is it possible? I have been searching through the forums and in the ALiVE wiki but could not find any answer...
  3. Probably you know this already :) but just in case. I add the desired units to the curators by adding an event at DAC_Config_Events.sqf http://pastebin.com/KgUtG3aU
  4. magnetar

    Zeus without module

    At preInit means that the function, that has to be declared in description.ext, must contain the "preInit = 1;" attribute as explained in section attributes in https://community.bistudio.com/wiki/Functions_Library_(Arma_3) PreInit functions execute before the objects are initialised. If you do not execute it at PreInit stage (section Initialization Order) it won't work.
  5. I also confirm v0.60 to work really well, although I have to admit I have not played with all features.
  6. magnetar

    Zeus without module

    Do this at PreInit: if (isServer) then { // Create Zeus Module if (isNil "cc_var_centreSideLogic_Zeus") then { cc_var_centreSideLogic_Zeus = createCenter sideLogic; publicVariable "cc_var_centreSideLogic_Zeus"; cc_var_grupSideLogic_Zeus = createGroup cc_var_centreSideLogic_Zeus; publicVariable "cc_var_grupSideLogic_Zeus"; }; cc_var_moduleZeus = cc_var_grupSideLogic_Zeus createUnit ["ModuleCurator_F",[0,0,0] , [], 0, ""]; cc_var_moduleZeus setVariable ["showNotification", false, true]; cc_var_moduleZeus setVariable ["birdType", "", true]; cc_var_moduleZeus setVariable ["Owner", "#adminLogged", true]; cc_var_moduleZeus setVariable ["Addons", 3, true]; cc_var_moduleZeus setVariable ["Forced", 0, true]; publicVariable "cc_var_moduleZeus"; };
  7. Once they reach the number of assigned waypoints they get another batch of waypoints. They never stop running since DAC whips them constantly :D
  8. magnetar

    ASR AI 3

    I can confirm this as well.
  9. What you are trying to do is, I believe, a no return zone. This zone would spawn units but they will never come back if set to zero or with a probabilty of coming back with a maximum of 100 (Entry The selection of side, the unit-, behaviour-, and Camp-Configuration). A linked waypoint zone is possible (Entry Create Waypoint Zones in the manual). No return zone (spawning infantry only): ["z1",[1,0,0,0],[8,2,50,8],[],[],[],[0,0,0,0,0]] spawn DAC_Zone; Waypoint zone for infantry only (20 waypoints): ["z2",[1,0,0],[20],[],[],[],[0,0,0,0,0]] spawn DAC_Zone;
  10. magnetar

    Arma 3 Units - Closed Beta Feedback

    I have a question. It seems that at the moment Arma 3 Units has its account bound to bohemia account. Could it be possible to create a more general account in order to allow access to privileged members of the group? It is common that members within a community come and go and having this bound to the bohemia account does not seem a good idea. Otherwise I have to say it looks really good!
  11. I am trying to set some functions at preInit level that have some variables in common. What I would like to know is if there is a possibility to execute functions at PreInit level using a certain order. For example, I have the following (pseudo)-functions in which variables from function B depends on the execution of function A. fnc_A = {varA = 1; ....}; fnc_B = {if (varA == 1) then { varB == true; }; fnc_C = {if (varB = true) then { ... }}; Is, therefore, a way to define order of execution at PreInit level so that they are executed like: 1) fnc_A 2) fnc_B 3) fnc_C and not like 1) fnc_B 2) fnc_A 3) fnc_C Thanks in advance! Note: I am aware that by generating a function at preInit that defines the previous three functions would yield the desired results. I am asking however to define such order without having a "master" function.
  12. Solution: As @killzone_kid pointed out, declaring in description.ext the preInit (and by extension PostInit) functions in the desired order of execution does the trick. @SilentSpike I wonder now if CBA could be eventually extended to handle this. I am not familiar with the code at all but I will try to have a look, as long as this is something the project could benefit from :). I like alphabetical ordering of my functions :D Thanks again to all of you for posting and suggesting solutions.
  13. First of all, thanks to all of you for taking time to post! I will report on this. :) Yes, I was aware of that solution. I was wondering however if one could specify an order somehow... This is the solution I currently have implemented :) No, I was referring to how to "order" preInit functions (which extends to postInit ones as well).
  14. you are doing something strange. You pass as an argument a position in [(getMarkerPos _pos)] execVM "sidemissions\side1.sqf";}; and then you ask the position of the position in the following line: [(getPos _sidepos),300,500,0,25,_infTA] call DAC_fNewZone; Also, in // Add task //Task ID-Task name-Task description and some other options Enemy have acquired a new base on the island. Finish them off quickly.","Clear Area","Clear Area"],_sidepos,"AUTOASSIGNED",6,true,true] call BIS_fnc_setTask; you seem to have an error.
  15. If _sidepos is a marker use https://community.bi...ki/getMarkerPos instead.
  16. Maybe it has to do with the side you are selecting in the last array. Note that to spawn east side units (CSAT) it should look like this (assuming 0 is CSAT and 1 NATO in DAC_config_Units.sqf): _infVTA = ["z1",[1,0,0],[8,1,6,4],[1,1,4,3],[1,1,3,3],[1,1,4],[0,0,0,0,0]]; while _infVTA = ["z1",[1,0,0],[8,1,6,4],[1,1,4,3],[1,1,3,3],[1,1,4],[1,1,1,0,0]]; would generate west side units. Notice as well, that the forth parameter that I have put to 0 in the last array [1,1,1,0,0] is related to camp configurations. Do you have DAC camps configured?
  17. I think it has to do with _sidepos when you call DAC_fNewZone. This function expects at a first argument the position where it has to be created. If you look at what the command "position player" or equivalently "getPos player" you can see that they return an array [x,y,z]. Therefore you should give the position of "_sidepos" instead of just giving it as a value. Try please, assuming _sidepos is a marker, the following [(getMarkerPos _sidepos) ,300,300,0,0,_infVT] call DAC_fNewZone; https://community.bistudio.com/wiki/getMarkerPos https://community.bistudio.com/wiki/getPos https://community.bistudio.com/wiki/position Hope it helps
  18. Isn't the command DAC_fNewZone in the manual what you are looking for?
  19. holy moly! I have been waiting for this. Downloading now! Edit: I am totally impressed. I liked the videos a lot but wow, testing it myself was way much better. 10/10
  20. magnetar

    Game Updater. Error 0x406

    I will send them as soon as I get home. If you also need some sort of testing done I will gratefully do it.
  21. magnetar

    Game Updater. Error 0x406

    Any updates on this issue? It still persists and it is not caused by any firewall nor interruptions in internet connection...
×