There is no set process for configuration, just that there are many things that need to be done. We can start creating our prefab, but we will have to make an animation workspace, we can start making animation workspace, but we need a prefab. There is no set order of operations, so during this guide you may find yourself jumping around a lot.

graph TD
    A["Start Helicopter Configuration"]
    B["Duplicate Base Prefab"]
    C["Configure VehicleHelicopterSimulation"]
    D["Set Up Animation"]
    E["Configure Vehicle Parts"]
    F["Set Up Slot Manager"]
    G["Configure Rotor Prefabs"]
    H["Finalize Configuration"]

    A --> B
    B --> C
    C --> D
    C --> E
    C --> F
    C --> G
    D --> H
    E --> H
    F --> H
    G --> H

    %% Subprocesses
    subgraph "Animation Setup"
        D1["Select Animation Graph"]
        D2["Choose Anim Instance"]
        D --> D1
        D --> D2
    end

    subgraph "Vehicle Parts Setup"
        E1["Keep [Internal] Parts"]
        E2["Link to Slot Manager"]
        E --> E1
        E --> E2
    end

    %% Additional notes
    classDef note fill:#f9f,stroke:#333,stroke-width:2px;
    class NoteA,NoteB,NoteC note;

    NoteA["Note: No set order of operations"]
    NoteB["Use UH/Mi8 as base for compatibility"]
    NoteC["Refer to official wiki for missing info"]

    A --- NoteA
    B --- NoteB
    H --- NoteC

https://community.bistudio.com/wiki/Arma_Reforger:Car_Creation/Prefab_Configuration

To configure our model, we need to first create a duplicate prefab. It is recommended to use the UH/Mi8 as the base in order to ensure compatibility and allow for iterative testing - since we know those two helicopters work. Creating from scratch is not advised, as game updates can alter how prefabs must be configured. By duplicating Mi8/UH1 base, you will inherit from Helicopter_base.et, and be able to change/remove additions specific to the Mi8/UH1. If a game update adds a component, it will apply to your prefab automatically. Inherit is a good second choice, but you lose a lot of modularity as many vanilla items/things will not be removable. Avoid override when possible as you will prevent other helicopters from working.

This guide will be divided into different sections for each component that needs definitions. In lieu of missing information here, refer to the official wiki linked above.

RigidBody

There are some variables here which are important for the helicopter flight simulation.

Mass	This is the weight of the vehicle in engine, higher value means more force required in landing gear config and main rotor force.
Linear damping	Think of this like a global air friction parameter. The higher this value is, the more the game tries to fight to end the helicopters movement. The faster the helicopter is the more resistance it will get. A value of 0.0 will allow the helicopter to go an infinite speed, so it is advisable to balance this value with the hull simulation.
Angular damping	Think of this as the same as linear damping but only for vehicle rotation, the game will slow down it’s rotation through the air using this parameter.
Sleep thresholds	How fast/slow the vehicle needs to be before the above parameters take effect/stop taking effect.

VehicleHelicopterSimulation

This determines your helicopter’s flight model, what prefabs are used for your rotors, suspension and wheel parameters, and linking to animation components. It is very easy to mess this up.

Signals Source Access

Animation

Anim Graph
- Select your animation graph, if you haven’t started on it yet, it’s a good time to go to:
  
  Creating Helicopter/Player Animations
- A workspace consists of many different types of files, so you’ll select the helicopter.agr file.
Anim Instance
- Since this is for the vehicle, we select the one that corresponds to the vehicle (i.e. helicopter_helicopter.asi).
Vehicle Parts
- There will likely be a bunch of parts duplicated from the Mi8/UH1, it’s important to keep anything labeled [Internal]. Later, there will be a guide on creating your own [Internal] vehicle part, such as for a ramp or accessory you wish to animate.
- This is what ties your animation to slots in slot manager. Later, slot manager is explained along with rotor prefabs.
- Keep RotorMain and RotorTail as they are already linked to the Animation Graph variables.
Anim Variables
- These link the signals produced by the game engine, and the animation variables. Most signals are already linked to a corresponding variable, like with RotorState0 being linked to MainRotorState signal.
- In the animation editor, you will be able to act off of these signals, such as when animating blades based on CyclicAside/CyclicForward.
- Some signals exist based on other configurations in the simulation, for example if your helicopter has 4 wheels, you would have a wheel_0, wheel_1, wheel_2, and wheel_3 signal associated. This is dynamic, so adding additional wheels automatically creates these signals. Since the MiH only has 3 wheels, you will have to add new variables in your animation graph to account for that.
- In order to add new variables, you should ensure you have already added it to the animation editor CONTROLS tab. Refer to linked animation tutorial in the beginning of this.
Wake Command
- Can be left as is, this is a default command when the vehicle is spawned and is simulating physics. This queues the animation graph to start listening and playing animations.