This guide walks through creating an Arma 3 Advanced Flight Model RotorLib XML profile for a custom helicopter. It is written to match the RotorLib XML Profile Builder workflow and assumes the final XML will be tested in Arma 3 with Advanced Flight Model enabled. The first XML is not a finished flight model. Treat it as a structured, documented starting point. Every estimated value should be recorded, tested, and replaced when better source data becomes available.

Before entering values, collect these files and references:

1. The target helicopter addon source.
2. The target model, memory points, Geometry LOD, LandContact points, and any proxy gear/wheel geometry.
3. The target vehicle config class.
4. Any existing RotorLibHelicopterProperties / RTDconfig reference.
5. A closest matching BIS or mod RotorLib XML baseline.
6. Real aircraft data, if available: mass, dimensions, rotor diameter, blade count, engine power, RPM, wheel dimensions, and gear layout.

Use the closest proven RotorLib XML as the baseline. Match by:

1. Approximate aircraft mass class.
2. Main rotor count and tail rotor arrangement.
3. Landing contact type: wheels, skids, fixed hull/tail points.
4. Role: light, attack, transport, heavy transport.
5. Similar rotor RPM and engine/transmission layout.

Keep the selected baseline recorded in the tool. Some sections, especially drive trains and control-system conventions, are easier to preserve from a working profile than to recreate from documentation.

RotorLib coordinates use:

All position values must be converted into this coordinate system. Do not assume Arma model-space labels or visual axes match the value names without checking the model and a known working XML. Useful rules:

1. Positive X moves a point to the aircraft right side.
2. Positive Y moves a point toward the nose.
3. Positive Z moves a point upward.
4. Wheel, skid, tail rotor, rotor hub, and stabilizer positions should be measured relative to the same aircraft reference/datum used by the baseline XML.

If the exact datum is unclear, compare the baseline XML values against visible geometry and memory points. Preserve the same convention when adapting it.

Enter:

Example Arma config pattern:

class RotorLibHelicopterProperties
{
    RTDconfig = "\my_addon\air\RTD_MyHelicopter.xml";
};

Verify the exact placement and property names against a working vanilla helicopter config before packing.

Enter mass in kilograms. Best sources, in order:

1. Geometry LOD mass from the finished model.
2. Existing addon config/source documentation.
3. Real aircraft maximum takeoff weight or empty weight, depending on what you are modelling first.
4. Closest baseline XML scaled to the new helicopter.

Start with a realistic operating/test mass, not necessarily the absolute maximum load. Later, test loaded and unloaded behavior separately.

Enter approximate dimensions in meters:

These dimensions are used for first-pass inertia and generated contact positions. They are not a substitute for measured contact or rotor stations.