DeviceConfig XML Properties

The DeviceConfig.xml file is used to determine how different device profiles will be displayed within the UI. Each device input package should only ever have one of these files, and it must always be named “DeviceConfig” for the simulation to recognize it.

This file is created automatically for you when you use The Input Device 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 page for more information on how to do this:

• Device Profiles

The DeviceConfig.xml file has the following schematic structure:

<?xml version= "1.0" encoding= "utf-8" ?>
<DeviceConfig>
    
    <Device [attributes] />
    <Device [attributes] />
    ...
    
    <Device [attributes] >
        <MergeIcons [attibutes]/>
        <MergeIcons [attibutes]/>
        ...
        
        <ButtonTT [attibutes]/>
        <ButtonTT [attibutes]/>
        ...
    </Device>
    ...
</DeviceConfig>

<DeviceConfig>#

This is a container element where you will place one or more <Device> sub-elements. This element has no attributes.

<Device>#

This element is a sub-element of <DeviceConfig> and is used to setup a specific device definition for use in the simulation UI. If the device has no icons then the element is self-closing, otherwise it will have one or more <MergeIcons> sub-elements. Note that if the device is Keyboard or Mouse then you cannot use the <MergeIcons> sub-element as these inputs will always use the default UI icons.

It can have the following attributes:

ProductID="0x02FF"

<MergeIcons>#

This is a sub-element of <Device> and is used to define one or more icons that can be used to represent a button, axis or slider on the device being defined. The icons to be used should be placed within the folder defined in the <Device> attributes. It is recommended that you have a merge icon tag for every input on the controller, although it is assumed that you will assign the same icon to multiple inputs (for example, a single “Left Stick” icon can be assigned to the left stick +X, -X, +Y and -Y inputs).

This element can have the following attributes:

SourceIcons="R-STICK LEFT&R-STICK RIGHT"

TargetIcon="R-STICK_1"

TargetTT="TT:INPUT.GAMEPAD.ANALOGLEFT"

TargetTT="Analogue Left Stick"

<ButtonTT>#

This is a sub-element of <Device> and is used to define one or more localisable strings that represent a button, axis or slider on the device being used. These strings are used in the simulation when an icon is not appropriate or hasn’t been defined, and there should be one <ButtonTT> for every input on the device. For example, if the device has a joystick, you should have 4 <ButtonTT> for up / down / left / right, or if there is a slider, there should be two <ButtonTT> for slider up and slider down, etc…

It can have the following attributes:

SourceIcons Keys#

There are a number of predefined keys available to you to use to bind one or more inputs to a given icon. The tables below show the keys for the different input devices, along with the hardware string they are associated with. Note that there are no tables for mouse or Keyboard input, as those devices will use the default UI icons.

Controller (XBox One for Windows)#

SourceIcons Key	Information Key	Controller Input
A	Button1
B	Button2
X	Button3
Y	Button4
LB	Button5
RB	Button6
LT	Axis Z Axis Z+
RT	Axis Z Axis Z-
L-STICK	Button9
R-STICK	Button10
BACK	Button7
START	Button8
D-PAD LEFT	POV1 POV1_LEFT
D-PAD RIGHT	POV1 POV1_RIGHT
D-PAD UP	POV1 POV1_UP
D-PAD DOWN	POV1 POV1_DOWN
L-STICK LEFT	Axis X-
L-STICK RIGHT	Axis X+
L-STICK UP	Axis Y-
L-STICK DOWN	Axis Y+
R-STICK LEFT	Rotation X-
R-STICK RIGHT	Rotation X+
R-STICK UP	Rotation Y-
R-STICK DOWN	Rotation Y+
L-STICK X	Axis X
L-STICK Y	Axis Y
R-STICK X	Rotation X
R-STICK Y	Rotation Y

Xinput Controller / XBox Series Gamepad#

XBox Series Stick#

XR Controller Left / XR Controller Right#