# Input Configuration XML Properties<no value>
The `[device_name].xml` file is the **input configuration file** which is used to create custom input bindings within the simulation for different devices. The file contains information that binds specific inputs from a controller (XBox gamepad, mouse, VR controller, joystick, etc...) to specific [input event actions.](../../programming-apis/key-events/key-events/)

 

This file is created automatically for you when you use [The Input Profile Editor](../../devmode/editors/input-editors/the-input-profile-editor/), and a such, this page is provided **purely for reference** and all edition of the file should be done using the editor to ensure that it is set up correctly. Please see the following pages for more information on how to do this:

-   [Setting Up Transversal Bindings](device-profiles/#transversal-bindings)
-   [Aircraft Category Profiles](aircraft-category-input-profiles/)
-   [Aircraft Specific Input Profiles](aircraft-specific-input-profiles/)

 

this file has the following schematic structure:

``` xml
<?xml version="1.0" encoding="utf-8"?>
<DefaultInput Primary="1" PlatformAvailability="PC">
    <Version Num="0" />
    <Device DeviceName="DEVICE" GUID="00000000-0000-0000-0000-000000000000" ProductID="00" CompositeID="0" HWVer="1.0.0.0">
        <Axes>
            
        </Axes>
        
        <Context ContextName="3RD_PARTY">
            <Action ActionName="ACTION_NAME" Flag="2" ValueEvent="0">
                <Primary>
                    
                </Primary>
                <Secondary>
                    
                </Secondary>
            </Action>
            
        </Context>
        
    </Device>
</DefaultInput>
```

 

 

### &lt;DefaultInput&gt;

This is the container element within which all the other elements that define the input bindings will be stored. It has the following sub-elements:

1.  `<Version />`
2.  `<Device>`

 

It requires the following attributes:

 

<table><thead><tr class="header"><th>Attribute</th><th>Description</th><th>Type</th><th>Required</th></tr></thead><tbody><tr class="odd"><td><code>Primary</code></td><td>This shows whether the profile is the "primary" profile or not. When set to 1, the profile will be applied as the default profile when the simulation is started and the device is connected. When set to 0, it will not be applied automatically.</td><td>Bool</td><td>Yes</td></tr><tr class="even"><td><code>PlatformAvailability</code></td><td><p>This sets what platforms the device profile is valid for. The possible options are:</p><ol><li>"PC"</li><li>"XBOX"</li><li>"PLAYSTATION"</li><li>"PC, XBOX"</li><li>"PC, PLAYSTATION"</li><li>"XBOX, PLAYSTATION"</li><li>"ALL"</li></ol></td><td>String</td><td>Yes</td></tr></tbody></table>

 

 

### &lt;Version /&gt;

This self-closing element is a sub-element of `<DefaultInput>` and is used to identify the current version of the file. Note that every time you save the file using the [Input Profile Editor](../../devmode/editors/input-editors/the-input-profile-editor/), this number will be incremented automatically.

 

It requires the following attributes:

 

{{< table-wrapper >}}

| Attribute | Description                             | Type    | Required |
|-----------|-----------------------------------------|---------|:--------:|
| `Num`     | The current version number of the file. | Integer |    Yes   |

{{< /table-wrapper >}}


 

 

### &lt;Device&gt;

This sub-element of `<DefaultInput>` is the container element that holds all the different inputs and global values related to the device that was used for the input profile. It has the following sub-elements:

1.  `<Axes>`
2.  `<Context>`

 

It requires the following attributes:

 

<table><thead><tr class="header"><th>Attribute</th><th>Description</th><th>Type</th><th>Required</th></tr></thead><tbody><tr class="odd"><td><code>DeviceName</code></td><td>The identifying name of the device.</td><td>String</td><td>Yes</td></tr><tr class="even"><td><code>GUID</code></td><td><p>The unique <a href="../Models/Animation_XML_Properties/#" class="glossterm">GUID</a> for the device. This is the reference the simulation will use to identify the device, and must be in the format "<code>{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx}</code>", all lower case, for example:</p><p><code>GUID="{3b2577e0-8753-11ed-8004-444553540000}</code>".</p></td><td>String</td><td>Yes</td></tr><tr class="odd"><td><code>ProductID</code></td><td><p>This is the product ID for the device being defined. The ID should be formatted as a hexadecimal value. For example, if the Product ID is 767 you would have:</p><p>ProductID="0x2FF"</p><p>You can find the product ID from the device properties in the <a href="../../2_DevMode/Input_Editors/The_Input_Device_Editor.htm">Input Device Editor</a>.</p></td><td>Hexadecimal</td><td>Yes</td></tr><tr class="even"><td><code>CompositeID</code></td><td>This is the composite ID for the device being defined, expressed as an integer. You can find the composite ID from the device properties in the the <a href="../../2_DevMode/Input_Editors/The_Input_Device_Editor.htm">Input Device Editor</a>.</td><td>Integer</td><td>Yes</td></tr><tr class="odd"><td><code>HWVer</code></td><td>Hardware version of the device. Similar to the composite ID, the hardware version is used to link multiple parts together when they do <em>not</em> all belong to a single product ID.</td><td>String</td><td>Yes</td></tr></tbody></table>

 

 

### &lt;Axes&gt;

This sub-element of `<DefaultInput>` is the container element that holds the global axis values, defined using multiple `<Axis />` elements. This element has no attributes.

 

 

### &lt;Context&gt;

This sub-element of `<Device>` is used to store the bound inputs associated with a specific simulation *context*. Context is an internal setting used by the simulation to enabled/disable inputs based on what the user is doing within the simulation (for example, using the drone camera, using cockpit controls, etc...). As such, the input profile XML file will normally have multiple `<Context>` entries, and within each context you will have multiple `<Action>` elements defining the inputs bound to the context. You can find more information on context here:

-   [Understanding Contexts And Profiles](input-profiles/#contexts-profiles)

 

This element has the following attribute:

 

{{< table-wrapper >}}

| Attribute     | Description                                                    | Type   | Required |
|---------------|----------------------------------------------------------------|--------|:--------:|
| `ContextName` | The context name for the actions contained within the element. | String |    Yes   |

{{< /table-wrapper >}}


 

 

### &lt;Action&gt;

This sub-element of `<Context>` is used to hold the input bindings to specific input event actions. It can have the following two sub-elements:

1.  `<Primary>`
2.  `<Secondary>`

 

This element has the following attributes:

 

<table><thead><tr class="header"><th>Attribute</th><th>Description</th><th>Type</th><th>Required</th></tr></thead><tbody><tr class="odd"><td><code>ActionName</code></td><td><p>This is the name of the input event action that the primary (and secondary) device input will be bound to. The action name is <em>either</em>:</p><ul><li><p>An <a href="../../6_Programming_APIs/key-events/key-events-index/">Event ID</a> - prefixed with "KEY_" - if the profile is <em>transversal</em> or for an <em>aircraft category</em>. For example:</p><pre class="language-xml"><code>ActionName=&quot;KEY_KOHLSMAN_INC&quot;</code></pre></li><li><p>An <a href="../models/modelbehaviors/model-behaviors/Input_Event_XML_Properties.htm">Input Event</a> taken from from the aircraft <strong>model behaviours</strong> if the profile is an <em>aircraft specific</em> profile. For example:</p><pre class="language-xml"><code>ActionName=&quot;AIRFRAME_ALTERNATE_AIR_GEAR_INC&quot;</code></pre></li></ul></td><td>String</td><td>Yes</td></tr><tr class="even"><td><code>Flag</code></td><td><p>This is a <em>bit-flag</em> which is used to define the kind of input that is being received from the device being defined. The following values can be combined to create a single flag value that defines the way the input will be interpreted:</p><ol><li>1 = FL_ANALOG</li><li>2 = FL_DIGITAL</li><li>4 = FL_AXIS</li><li>8 = FL_NO_MOD</li><li>16 = FL_MOD_CTRL</li><li>32 = FL_MOD_SHIFT</li><li>64 = FL_MOD_ALT</li><li>128 = FL_MOD_INV</li><li>256 = FL_MOD_UP</li><li>512 = FL_MOD_VALUE</li><li>1024 = FL_MOD_NO_SENS_CURVE</li><li>2048 = FL_MOD_RESET_ONCONTEXT_DISABLED</li><li>4096 = FL_MOD_AXIS_OVERRIDE</li><li>8192 = FL_MOD_PRESSED</li><li>16384 = FL_MOD_DELAYED_EXCLUSIVE</li><li>32768 = FL_MOD_NO_KEYBOARD_LAYOUT</li></ol><p>For a full description of these flags, please see the section on <a href="../../2_DevMode/Input_Editors/The_Input_Profile_Editor/#input_options">Action Options</a>. It should be noted that:</p><ul><li>MOD_VALUE will require the <code>ValueEvent</code> attribute to be used, and <em>cannot</em> be used on <a href="Transversal_Input_Profiles.htm">Transversal Input Profiles</a>.</li><li>MOD_AXIS_OVERRIDE can <em>only</em> be used on <a href="Transversal_Input_Profiles.htm">Transversal Input Profiles</a></li></ul></td><td>Integer</td><td>Yes</td></tr><tr class="odd"><td><code>ValueEvent</code></td><td>This is the value that will be sent when the event is triggered.</td><td>Float/Integer</td><td>No</td></tr></tbody></table>

 

 

#### &lt;Primary&gt;

This is a sub-element of `<Action>` and is used to define the primary input for the event action. The element has no attributes and must contain one `<KEY>` sub-element, and optionally - depending on whether the input has a custom axis definition - one `<Axis />` sub-element.

 

 

#### &lt;Secondary&gt;

This is a sub-element of `<Action>` and is used to define the secondary input for the event action. The element has no attributes and must contain one `<KEY>` sub-element, and optionally - depending on whether the input has a custom axis definition - one `<Axis />` sub-element.

 

 

### &lt;Axis /&gt;

This element can be used in the `<Axes>` and `<Action>` elements to define the properties of a single axis of the device. This is a self-closing element with the following attributes:

 

<table><thead><tr class="header"><th>Attribute</th><th>Description</th><th>Type</th><th>Required</th></tr></thead><tbody><tr class="odd"><td><code>AxisName</code></td><td><p>The name of the axis being defined. Must be one of the following:</p><ol><li>"X"</li><li>"Y"</li><li>"Z"</li><li>"rX"</li><li>"rY"</li><li>"rZ"</li><li>"SliderX"</li><li>"SliderY"</li></ol></td><td>String</td><td>Yes</td></tr><tr class="even"><td><code>AxisSensitivy</code></td><td>The positive sensitivity of the chosen axis, defined as a value between 0 and 100.</td><td>Integer</td><td>Yes</td></tr><tr class="odd"><td><code>AxisSensitivyMinus</code></td><td>The negative sensitivity of the chosen axis, defined as a value between -100 and 0.</td><td>Integer</td><td>Yes</td></tr><tr class="even"><td><code>AxisDeadZone</code></td><td>The inside position of the chosen axis dead zone, defined as a value between 0 and 100.</td><td>Integer</td><td>Yes</td></tr><tr class="odd"><td><code>AxisOutDeadZone</code></td><td>The outside position of the chosen axis dead zone, defined as a value between 0 and 100.</td><td>Integer</td><td>Yes</td></tr><tr class="even"><td><code>AxisNeutral</code></td><td>The chosen axis neutral position, defined as a value between -100 and 100.</td><td>Integer</td><td>Yes</td></tr><tr class="odd"><td><code>AxisResponseRate</code></td><td>The response rate for the chosen axis, defined as a value between 100 and 2000. You can use -1 to ignore this attribute and use the default sensitivity.</td><td>Integer</td><td>Yes</td></tr></tbody></table>

 

 

### &lt;KEY&gt;

This is a sub-element of both the `<Primary>` and `<Secondary>` elements, and is used to define a single input source from a device. Note that the value given inside the `<KEY>` tag is generated by the [Input Profile Editor](../../devmode/editors/input-editors/the-input-profile-editor/) and is essentially the numeric ID for the `Information` attribute input source, in a format that can be easily read by the simulation. You should not change this value or try to use your own.

 

This element has the following attribute:

 

{{< table-wrapper >}}

| Attribute                                   | Description                                                                                                                                                                     | Type   | Required |
|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|:--------:|
| `Information` | This is the name of the input source as returned by the device or as shown in the [Device Keys](../../devmode/editors/input-editors/the-input-profile-editor/#device_keys) window. | String |    Yes   |

{{< /table-wrapper >}}