DEVICEDB XML PROPERTIES

The *.devicedb file is created using the Input Application and is an XML formatted file used to create a hardware support file to be used in the simulation as part of an input profile. The purpose of these files is to store hardware information - identification, platform, etc... - as well as all the actions available for the input profile and their event mappings. There can be various versions of this file, where each one is a new mapping set. Note that generally you should never need to edit or create this file manually, and it should always be created through the Input Application.

The *.devicedb file has the following schematic structure:

<?xml version="1.0" encoding="utf-8"?>
<DeviceDefinition>
    <Device PrimaryMapping="1" Device_Type="4" GUID="00000000-0000-0000-0000-000000000000" ProductID="0000" CompositeID="0" HWVer="1.0.0.0" PlatformAvailability="PC, XBOX" ExportPath="InputProfiles\ALL\">
        <Name>MyDevice_01</Name>
        <Axes>
          <Axis AxisName="AXIS_A" AxisSensitivy="0" AxisSensitivyMinus="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisNeutral="0" AxisResponseRate="0"/>
        </Axes>
        <CompleteBind>
            <RefAction>KEY_MY_ACTION|MY_CONTEXT</RefAction>
            <Primary ReadableBind="BUTTON_1(+)BUTTON_2(+)BUTTON_3(+)AXIS_A" ValueEvent="1" ControlOverride="AXIS, MOD_VALUE">
                <Key ID="1" />
                <Key ID="2" />
                <Key ID="3" />
                <Key ID="5" />
            </Primary>
            <Secondary ReadableBind="BUTTON_4">
                <Key ID="4" />
            </Secondary>
        </CompleteBind>
    </Device>
</DeviceDefinition>

You can find a tutorial on how to create input profiles on the following page:

• Creating An Input Profile

<DeviceDefinition>

This is a container element for all the details of the different hardware device definitions for the profile. Should contain the following sub-element:

1. <Device>

<Device>

This is a child element of <DeviceDefinition> and is the top-level container for a single device definition. It can contain the following sub-elements:

1. <Name>
2. <Axes>
3. <CompleteBind>

It can have the following attributes:

<Name>

This is a child element of <Device> and is the "common" name of the device, as defined in the Input Application. This name is displayed in the simulation.

<Axes>

This is a child element of <Device> and is a container element used to define the different axes the device supports. It has no attributes and requires one or more <Axis /> sub-elements.

<Axis />

This is a self-closing element and is used inside the <Axes> container to define a single axis of movement for the controller. It can have the following attributes:

<CompleteBind>

This is a child element of <Device> and is used to define the mapping between an action and an input from the controller. In general, you should have one of these for every action in the project, even if there is no controller binding for that particular action (for example, if the hardware device the file refers to does not support axis movement, but the *.actiondb has actions for axis controllers, there should still be <CompleteBind> definitions for the actions, but they will be "empty").

This element has no attributes and is a container for the following:

1. <RefAction>
2. <Primary>
3. <Secondary>

<RefAction>

This is a child element of <CompleteBind> and is used to set the action and the context to bind (map) to a controller input. The element has no attributes, and takes a string with the following format:

<RefAction>ACTION_NAME|CONTEXT</RefAction>

For a list of the actions available please see the Key Events section, and for a list of contexts, please see the Available Contexts section.

<Primary>

This is a child element of <CompleteBind> and defines the primary input(s) assigned to the action. It can have the <Key> sub-element and requires the following attributes:

<Primary ReadableBind="LeftAlt(+)F8" ValueEvent="0" ControlOverride="DIGITAL">

<Primary ReadableBind="R" ValueEvent="0" ControlOverride="DIGITAL, MOD_PRESSED">

<Key />

This is a child element of <Primary> (and <Secondary>) element and is used to define one or more ID values for the inputs used in the ReadableBind attribute of the parent element. This is a self-closing element, and there should be one defined for every input used in the ReadableBind attribute of the parent element.

This element has the following attribute:

<Secondary>

This is a child element of <CompleteBind> and defines the secondary input(s) assigned to the action. It can have the <Key> sub-element and requires the following attribute (the secondary input will inherit the values for ValueEvent and ControlOverride from the <Primary> element):

<Secondary ReadableBind="LeftShift(+)Down">

Binding Tables

The tables below show the available bindings that can be used for each of the available input device types. The values in the tables are used in the <Primary> and <Secondary> element ReadableBind attribute. Note that the Generic Mouse and Tobii Eye Tracker types have no binding reference values.

Generic keyboard ("Keyboard" in the Input App)

NOTE: This list is not exhaustive. For any keys not listed here use the Input Application Mappings window.

XBox controller PC ("Xinput Gamepad" in the Input App)

Direct Input controller ("Controller XBox One For WIndows" in the Input App)

VR Gamepad Controller ("XR Controller Left / Right" in the Input App)

Xbox Series Joystick controller ("Xbox Series Stick" in the Input App)