When using QFUNC, the intend most often is to have the name of the variable referencing the function as a string. This behaviour works when compiling without debug enabled. However if debug is enabled, QFUNC compiles in with the debug wrapper, becoming a code string instead of a string representation of a variable reference. A good example where this change of behaviour can be a problem is config attributes that refer to a call back (used a lot within ACE). In normal build, you will use a getvar to get the relevant code, as it is expected to point to the function. When using debug, you will need to do a compile instead, as it's a string representing a code block. |
||
---|---|---|
.github | ||
addons | ||
docs | ||
extensions | ||
extras | ||
optionals | ||
tools | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.travis.yml | ||
ace_advanced_ballistics.dll | ||
ace_break_line.dll | ||
ace_clipboard.dll | ||
ace_fcs.dll | ||
ace_medical.dll | ||
ace_parse_imagepath.dll | ||
Arma3_workshop_addon.jpg | ||
AUTHORS.txt | ||
LICENSE | ||
logo_ace3_ca.paa | ||
meta.cpp | ||
mod.cpp | ||
README.md |
Requires the latest version of CBA A3.
Visit us on Twitter | Facebook | YouTube | Reddit
ACE3 is a joint effort by the teams behind ACE2, AGM and CSE to improve the realism and authenticity of Arma 3.
The project is entirely open-source and all contributions are welcome. Feel free to maintain your own custom version, so long as the changes you make are open to the public in accordance with the GNU General Public License (GPLv2).
The mod is built modularly, so almost any included PBO can be easily removed from the configuration. This way, a team can maintain its own tailored version of ACE3 by simply excluding any components they don't need, or those possibly in conflict with other mods. Modules themselves, e.g. the medical system, also include various customization options, allowing mission designers to tweak the overall experience.
Core features
- Brand new 3D interaction/action system
- Performance and reliability framework
- Focus on modularity and customization
- New flexible client and server settings & configuration
- Improved medical system with various levels (basic/advanced) focus on gameplay/realism
- Proper & consistent network-synced weather
- Wind and weather-based ballistics
- Captivity system
- Explosives system, including different trigger types
- Map screen improvements – marker placement and map tools
- Logistics
- Advanced missile guidance and laser designation
Additional features
- Carrying and dragging
- Realistic names for vehicles and weapons
- A fire control system (FCS) for armored vehicles and helicopters
- Realistic ballistics/FCS calculated in C/C++ extensions
- Backblast area and overpressure simulation
- Disposable launchers
- Realistic G-forces
- Vehicle locking
- Realistic night and thermal vision modes
- Magazine repacking
- Realistic weapon overheating mechanic
- Combat deafness (temporary loss of hearing) simulation
- Improved interactions for AARs and ammo bearers
- Adjustable sniper scopes
- No idle animation with lowered weapon
- No talking player avatar
- Jumping over obstacles, climbing over walls and cutting down fences
- Vector, MicroDAGR and Kestrel devices
and much more...
Guides & how-tos
If you installed ACE3 but have trouble understanding how it all works, or where to start, read this first:
Contributing
You can help out with the ongoing development by looking for potential bugs in our code base, or by contributing new features. To contribute something to ACE3, simply fork this repository and submit your pull requests for review by other collaborators. Remember to add yourself to the author array of any PBO you will be editing and the AUTHORS.txt
file; including a valid email address.
Please, use our Issue Tracker to report a bug, propose a feature, or suggest changes to the existing ones. See also:
Testing & building
To help us test the latest development changes, download our master branch (directly, or with git), then assemble a test build:
- Setting up the development environment – step-by-step instructions on how to properly setup and build a version of ACE3 for testing purposes.