Open

This section describes how to make the link between your devices and your mechanisms.

In Vortex, the control of a mechanism is facilitated through its Control Interface. This interface can be operated using a device, a script, or programmatically.

Devices are typically integrated into Vortex using a setup file. Vortex provides a variety of device extensions, including:

• CANopen devices

• USB Devices

• Keyboard

Moreover, Vortex Studio users have the option to create their own device extensions.

Control Presets

The setup file includes Device extensions, which are specifically associated with the hardware on a simulator. This setup can be efficiently utilized across various mechanisms.

In this context, a mechanism represents a machine, while the Control Interface serves as the method to control the mechanism, regardless of the connected device. The fundamental principle guiding this design is the separation of concerns, emphasizing modularity and reusability.

When the simulator is running, Control presets act as the bridge between a Control Interface and device Extensions.

To establish this connection, two tools are available: Device Mapping and Device Mapping Scripts (tech preview), both accessible from the Control Presets tab.

Device Mapping

A device mapping is created through the Control Preset page. Each Control Preset provides the option to link a Control Interface to one or more Device Extensions. Every aspect of the Control Interface can be associated with one or multiple fields from a Device.

The user interface includes features like calibration/remapping, enabling users to define a dead band and set the minimum/maximum values of a device. It allows for remapping to a desired range using piecewise linear transfer functions.

Moreover, the user interface provides several methods to address the absence of suitable buttons. This includes the use of the toBool transfer function to convert an axis-based control into a button-like control, the toNumeric transfer function to change a button press into a numeric value, and an adding modifier. The adding modifier permits the transmission of a control element's signal to a different field in the Control Interface when another button is pressed. This functionality effectively allows a button to fulfill various functions based on the state of another button.

Device Mapping Script (Technical preview)

Another method of making a control mapping involves utilizing the Device Mapping script. This script provides an alternative route for control mapping. Mapping a specific field from a device or Control interface can only be achieved through either a Device Mapping or a Device Mapping script, but not both at the same time.

Unlike the straightforward user interface of the device mapping, a device mapping script sacrifices simplicity to grant users complete control over the mapping process. The script is incorporated through the Control preset page, allowing users to choose the field they wish to interface with and then supply a Python script to manipulate the data according to their requirements.

This approach offers users greater flexibility in terms of customization. All functionalities of the Device Mapping can be replicated through the script.

Known limitations

The device mapping script does not support Control Interface within roles. This can lead to undesired behavior, and it will be fixed in a later release.

See also

Vortex Studio SDK - Device Mapping