CMA:DevelopmentSetup

Development setup

This site focuses on getting your work ingame, as well as all aspects of addon,
pbos as a subset, development.

Motivation

• Correct setup to use binarize to track down errors and improve the quality.
• Best addon design for easy recognition, updating and quality.
• Dev setup to work with least time and resource effort.

Related topics

• Minimal Addons Setup
• PBO naming thoughts
• Good design - separate an addon in multiple PBOs
• Formatted A2 configs and all-in-one config as part of the CMB git repository.

Unpacking A1/A2

Motivation

For non simple addons you have references to BI configs, textures or proxies.
More specially the BI namespace CA.
Binarze is trying to locate these references during the optimization process.
In other words without these files available binarize is unable to do its job properly.

The models referenced by other models or wrp files can be both MLOD or ODOL format.

Process

Virtual partition P

We will create a virtual partition P: to map your arma folder.
This is required by the BI toolset and allows easy access to the arma folder.
It is recommended to create a link on your desktop or quicklaunch bar to P.

As a sidenote, at the same time you should create one central folder with
all your arma related tools in it. Map this one to T.

Are two arma installations necessary

The BI tools create by default a separate folder/location called ArmAWork.
This may or may not be needed.

Considerations:

• Two separate folder/locations to keep your play-install clean.
• Duplication of files may be needed for two separate.
  Possible to avoid with Junctions, if both are on the same HDD.
• Both play and dev combined in one folder avoids messing around.
  You only need to keep your folder structure well designed.
  You can ensure that only PBOs, and NO unpacked data, are loaded via

-noFilePatching

Done via ArmA: Startup Parameters.

Create P drive

1. Create a file called mapGameFolderToP.bat.
2. Add the line and adapt the path your arma folder:

subst p: "D:\Games\arma"

3. Move the file to the autostart location. IE (XP32b):

C:\Documents and Settings\YourUserAccount\Start Menu\Programs\Startup
or 
C:\Documents and Settings\All Users\Start Menu\Programs\Startup