Drivers Roccat Input Devices

Windows may install drivers for select devices, say the graphics card, under certain circumstances. This happens by default for instance when the device is setup, but may also happen when Microsoft pushes driver updates through Windows Updates.
The Tyon includes a hardware which is also used in a gamepad. In some cases this may lead to bugs. In such cases it often helps to deactivate the joystick function of the Tyon in the Device Manager. You will find this in the Device Manager under Input Devices/Human Interface Devices and is called „Virtual XInput Device“.
INPUTDEVICES setting to build driver for Roccat Kone Pure Military input devices inputdevicesroccatkonepureoptical INPUTDEVICES setting to build driver for Roccat Kone Pure Optical input devices.

Get notified when we have new Windows 10 Videos available! - video is brought. Input Output Audio Driver Controller is an application designed to help you view the input and output drivers of the sound cards you have installed on your computer. Since you can check both types.

-->

XInput is an API that allows applications to receive input from the Xbox Controller for Windows. This document describes the differences between XInput and DirectInput implementations of the Xbox Controller and how you can support XInput devices and legacy DirectInput devices at the same time.

Note

Use of legacy DirectInput is not recommended, and DirectInput is not available for Windows Store apps.

The New Standard: XInput

XInput is now available for game development. This is the new input standard for both the Xbox and Windows. The APIs are available through the DirectX SDK, and the driver is available through Windows Update.

There are several advantages to using XInput over DirectInput:

XInput is easier to use and requires less setup than DirectInput
Both Xbox and Windows programming will use the same sets of core APIs, allowing programming to translate cross-platform much easier
There will be a large installed base of Xbox controllers
XInput devices (that is, the Xbox controllers) will have vibration functionality only when using XInput APIs
Future controllers released for the Xbox console (that is, steering wheels) will also work on Windows

Using the Xbox Controller with DirectInput

The Xbox Controller is properly enumerated on DirectInput, and can be used with the DirectInputAPIs. However, some functionality provided by XInput will be missing from the DirectInput implementation:

The left and right trigger buttons will act as a single button, not independently
The vibration effects will not be available
Querying for headset devices will not be available

The combination of the left and right triggers in DirectInput is by design. Games have always assumed that DirectInput device axes are centered when there is no user interaction with the device. However, the Xbox controller was designed to register minimum value, not center, when the triggers are not being held. Older games would therefore assume user interaction.

The solution was to combine the triggers, setting one trigger to a positive direction and the other to a negative direction, so no user interaction is indicative to DirectInput of the 'control' being at center.

In order to test the trigger values separately, you must use XInput.

XInput and DirectInput Side by Side

By supporting XInput only, your game will not work with legacy DirectInput devices. XInput will not recognize these devices.

If you want your game to support legacy DirectInput devices, you may use DirectInput and XInput side by side. When enumerating your DirectInput devices, all DirectInput devices will enumerate correctly. All XInput devices will show up as both XInput and DirectInput devices, but they should not be handled through DirectInput. You will need to determine which of your DirectInput devices are legacy devices, and which are XInput devices, and remove them from the enumeration of DirectInput devices.