Eliteness Version 2.00

General inspection and play tool by Mikero@norfolk.nf

Originally designed to assist with Flashpoint : Elite for the xbox and developed as such by  Mikero and Hoz.

Version 2 uses improved techniques to accommodate ArmA as well as being fully compatible with earlier BI engines. This version has been tested, developed, and used by Hoz, Mikero, staff at Ofpec and many members of the ArmA beta development team.

This tool has no  other association with Bohemia Interactive and no approval, warranty, implied use, or permission has been given by them. Nor is that ever likely to be the case. Use this tool at own risk.

Installation instructions.


General Functionality.

OFP Elite Functions:


Notes:

This is a multi-purpose tool for all engine varieties. Specifically

As such, there are specific quirks for each engine that this tool cannot discover for itself unless told specifically about the engine output required.

Use the options panel in the gui to explicitly MAKE pbo's, or, raPified (binarised) files for a given engine.

PBO's

All later versions of the engine 'understand' earlier headers. However, to specifically create a header of specific type (eg Arma), use the options panel to do so. Default on installation is Resistance.

Arma PBO's

Arma Pbo's are identical to Resistance pbo's except the official addons from BI. These require special handling in the header. The engine, takes care of this detail.

Config.bin (eg)

Rapification for Armed Assault and Elite.

Binarised files for Armed Assaullt and Elite use a newer method of raPifcation. To convert a config.cpp (eg) to a config.bin for THESE engines, the tool must explicitly know that  it is required. It mus be explicit because the text concerned (be it config.cpp, mission.sqm, or description.ext) is identical for all engines. (some exceptions)

The preferred method is to explicitly state which engine in the text file with the use of a #pragma directive

First line of any text file for arma or elite should read

#pragma ARMA  or
#pragma XBOX or
#pragma ENHANCED

All three token names are synonymous and achieve an identical result. Specifically, binarising, (raPifying) output to the new format.

Without the pragma, text files are assumed to be for Flashpoint. This means no files from and for OFP require any modification.

Alternatively, you can force the issue (and not need to write tjhe #pragma) in the options panel.

XBOX Signatures

Mission,pars, header.bins and other files intended for the Xbox (and unique to the xbox) require correct signatures inserted into them by this tool.

The special #pragma

#pragma XBOX withSignature

is required in the mission.par text file and similarly the header.bin text file for this to take place automatically.

Alternatively, you can force the tool to insert (or check) signatures in any file required.

Enjoy