PMC Editing Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== ArmA 2 ======

ArmA 2 (Armed Assault 2, which is **NOT** its real name!) main editing page.

[[arma2:class_names|Class names]]

[[arma2:config|Config]]

[[arma2:editor_modules|Editor Modules]]

[[arma2:file_formats|File formats]]

[[arma2:missions|Missions]]

[[arma2:modeling|3D Modeling]]

[[arma2:port_arma|Port ArmA (1) addons]]

[[arma2:port_ofp|Port OFP addons]]

[[arma2:scripting|Scripting]]

[[arma2:terrain|Terrain]]

[[arma2:texturing|Texturing]]

[[arma2:tools|Tools]]

The links on red are to do, stay tuned.


====== General Editing ======

ArmA 2 will be largely compatible with Armed Assault. To make porting of content from ArmA as simple as possible, there are few important things:

  * using of undefined variable in scripts (nil value) will be in ArmA 2 strictly reported as an error. All variables used in any scripts must be initialized before first use.

  * in ArmA 2 namespaces will be introduced for user scripts and variables. There are many low level reasons to do this and most of the content will be not be affected by this in any negative way. However, in order to be prepared, it is very important to separate UI related scripts and code as much as possible and not simply share global variables between UI and missions as UI namespace needs to be handled differently.

  * in order to maintain smooth frame rate in real-time content, time limit for all scripts in each frame is enforced by the engine in ArmA 2. Generally speaking, in case of more demanding scripts, be prepared that their result may come way later and also there probably can suffer from significant latency. It is under evaluation if and how possibly allow user scripts to change how much time they may take from the CPU in every frame.

  * SQS script format will be fully supported in ArmA 2.
PMC Editing Wiki

User Tools

Site Tools

Page Tools
