Jump to content

alganthe

Member
  • Content Count

    178
  • Joined

  • Last visited

  • Medals

Everything posted by alganthe

  1. They actually are already there but are not documented, yet. Check: Creating an action Adding it to an object Adding it to a class All of them are local and need to be globaEvent'd or remoteExec'd to work on all machines properly.
  2. The new function (it was a script previously) support backward compatibility, the guide was written for the script before it was put into a function and refactored. It's better used as described above since it makes the unit config more readable and it's easier to modify. If you want to have your addon XEH compatible but don't want to add it as requirement you can create an adapter addon For more informations about the function params check the wiki page about it.
  3. BIS_fnc_unitHeadgear support backwards compatibility but it's easier to ditch all the old stuff and only use the arrays when calling it. like this init = "[_this select 0, ['TRYK_H_pakol2',1],['TRYK_Beard_BK',0.2,'TRYK_Beard_BK2',0.2,'TRYK_Beard_BK3',0.2,'TRYK_Beard_BK4',0.2]] call BIS_fnc_unitHeadgear"; The first array being headgear and the second one being facewear.
  4. That is not an ACE3 issue but a battleye one, starting the game once through the Arma 3 launcher fixes it. It might also refuse to update itself even when launching through the Arma 3 launcher, this happens when their servers are down and multiple users (including me) suffered from it today.
  5. Check in your ace settings if it's enabled. You'll find the option next to medical, it'll be called medical menu.
  6. danil-ch that video is pretty old and that behavior was fixed in 1.46.
  7. you CREATE the action THEN you add it, for more help hop in slack or pm me.
  8. When creating the action the code block cannot be empty. _action = ["Logistic","Logistic","",{code},{true}] call ace_interact_menu_fnc_createAction;
  9. Actions need to be created before being added. It goes like this Create the action -> add it to a class / object -> the menu is compiled -> the condition and code are true / non empty.
  10. For captives it's normal, the module is set like that by default, just place the module and tweak it / change it via the settings framework.
  11. alganthe

    (SMA) Specialist Military Arms

    There's no need to "merge" both projects since you can add ACE3 native support without adding a dependency, a compat pbo is also possible.
  12. Yep it's bugged atm and will be fixed in the next version. On the topic of some medical variables that changed (as pointed above) ACE3 doesn't have a public API for medical yet, they are subject to change and will not be "fixed".
  13. in basic CPR is only available when revive is enabled and it reset the revive timer, that way you can CPR the unit until the medic get to you and the patient and fixes him.
  14. alganthe

    RHS Escalation (AFRF and USAF)

    Absolutely not Redphoenix this is not the case, ACE3 doesn't touch ANYTHING related to tracked vehicle physx configs. I can also confirm after some testing that WITHOUT any other mods than RHS 0.3.9 the BMPs CAN drive around water.
  15. @Meaty that's not an issue caused by ACE, we do not force you to update nor we have anything in place to do it. @zriel what he meant is that we do not have public APIs for wounds, meaning that the current functions are subject to changes and are not documented on the wiki.
  16. alganthe

    RHS Escalation (AFRF and USAF)

    ACE3 issue do not try to use 3.3 at the moment and wait for a hotfix.
  17. It was only a temporary measure to avoid the upload of early WIP work, this condition is now lifted, any released package can now be uploaded on the steam workshop. Workshop full support is going to be added next update.
  18. That was also fixed, I just made sure of it.
  19. All of the issues mentionned above are now fixed, a hotfix is on the way. The documentation for the frameworks and usage of the new features should come in end of this week / next week.
  20. The current release was NOT done properly and is being investigated, please refrain from updating.
  21. The compatibilty pbos are not assured to work with this version, they were mostly example for modders until they introduced ACE3 native compatibility themselves see HLC weapons, BWMod.
  22. Nou has it on his todo list but It won't be fixed in 3.3
  23. alganthe

    RHS Escalation (AFRF and USAF)

    since i didn't saw it in the changelogs it's fair to assume you didn't fixed the fov issues on your weapons, or did you?
  24. Mod makers I have the pleasure to announce that we worked on the ACE3 frameworks documentation for an easier integration of ACE3 native support.They are available at http://ace3mod.com/wiki/framework/ and are classed by pbo name. Note that not all of them are present, we'll work on fixing that ;)
×