Skip to content
Made in Poland
Global Shipping
Tutorials & Guides

Direct Input

Use a joystick or gamepad as a direct input device to control the motion platform.

1 Information

In order to use a motion platform with a game or simulation that does not produce any output telemetry for the motion platform to operate with - it is possible to program a gaming controller used to control an in-game vehicle as a input signal generating device. That way gaming device controls both the in-game vehicle and the motion platform or belt tensioner.

2 Setting a joystick/gamepad as an input device

1. Open ForceSeatPM. Scroll down to the bottom and click New profile.

ForceSeatPM profiles list scrolled to the bottom with the New profile button

2. Enter the name of the profile and click OK. Your new profile will appear at the top of the profiles list.

3. Configuration window will open (if it does not - find your profile, open it and click Configure).

ForceSeatPM profile configuration window opened for the new Direct Input profile

4. In the window make sure DirectInputPlugin is selected (1.). Click Configure.

5. From a first Game controller list (2.) select your input creating device and then Run mapping wizard (3.).

ForceSeatPM profile configuration with DirectInputPlugin selected and the Configure button

6. Select your intended game type and click Next.

DirectInput plugin configuration with the game controller selected and Run mapping wizard

7. Proceed with the mapping wizard instructions. After that, click Done.

DirectInput mapping wizard with the game type selected

8. All the programmed controller axes will appear. Offset and Factor are values you may need to adjust later to make the QS-BT1 or motion platform perform as desired. Click Save and close.

DirectInput mapped controller axes with the Offset and Factor values for each

9. Activate freshly created profile - the motion platform will activate and will be ready to operate by the controller.

ForceSeatPM with the new Direct Input profile activated and the platform ready to operate
Warning
Any sudden movement will be transferred to the platform immediately. If you are unsure of how to operate the platform or if your mapping and adjustments went correctly - test the platform standing outside of the cockpit in a safe distance.

10. You can test if the input controller is working correctly by clicking Input diag. in profile menu and looking for your input in the correct graphs.

ForceSeatPM Input diagnostic graphs showing the controller input arriving

11. You can see the platform reacting on the device's inputs on graph inside the Platform Diagnostics (ForceSeatPM, Tools and Diagnostic, Platform Diagnostic).

ForceSeatPM Platform Diagnostic graph showing the platform reacting to controller input

3 Tuning the profile

Tuning the profile can be done by clicking the Configure button inside the profile and increasing/decreasing the factor, offset or dead zone value, or range, smoothness slider under a given axis (2.). You can also change the acceleration or maximum speed general slider (1.). Keep in mind that they can be tested right away by using the controller (click Save to apply the changes).

Click Save and close not to lose your adjustments, after you are done (3.).

DirectInput axis tuning with Save and Save and close

Another way is to use the main sliders in a profile window. Changes are applied immediately.

ForceSeatPM profile window main sliders, applied immediately

4 Tips and guidelines

It is possible to add new axes outside of a standard set - click Add mapping and the new axis will appear at the bottom of mapping window. You can create a surge movement for example, to be controlled by a throttle. Set the factor similarly to other axis, smoothness halfway (since surge controlled by a throttle can be very fast) and save the changes.

DirectInput surge axis mapped to a throttle, with factor and smoothness set

One profile can control all your motion platforms and QS-BT1 together. If you wish to use only one of these devices - either delete them from a mapping list or pause the device using main QubicManager window buttons at the bottom (they will become active again after a QubicManager restart).

QubicManager bottom bar buttons used to pause an input device

Or disable the QS-BT1 using the icon at the bottom:

QubicManager bottom bar icon used to disable the QS-BT1

Beware of creating new axes (Add mapping button) that could create an axis conflicting with existing one and make the platform perform unpredictably. Never double any axis.