The table below lists the values that are needed to map a button. The following sections explain the contents of each of the subkeys under the Gamepad, RacingWheel, ArcadeStick, FlightStick, and UINavigation keys. The table below lists the required and optional subkeys under UINavigation subkey: Subkeyįor more information about UI navigation controllers and the above commands, see UI navigation controller. The table below lists the required and optional subkeys under the FlightStick subkey: Subkey The table below lists the required and optional subkeys under the ArcadeStick subkey: Subkey The table below lists the required and optional subkeys under the RacingWheel subkey: Subkey If you add your game controller as a supported Gamepad, we highly recommend that you also add it as a supported UINavigationController. The table below lists the required and optional subkeys under the Gamepad subkey: Subkey Subkeys under the device root location are detailed in the following sections.

Your device installer should add this data to the registry (either via setup or an INF file). Indicates that this particular device should be disabled. The table below explains the expected values under the device root location: Name

Mappings for a device with Vendor ID (VID) VVVV, Product ID (PID) PPPP, Usage Page UUUU, and Usage ID XXXX, will be read out from this location in the registry: By doing this, all UWP games (and any desktop games that use the WinRT API) will be able to support your game controller. All IHVs should add this data for their compatible controllers. The namespace allows independent hardware vendors (IHVs) to add data to the PC's registry, enabling their devices to appear as Gamepads, RacingWheels, ArcadeSticks, FlightSticks, and UINavigationControllers as appropriate. This topic is meant for manufacturers of Windows 10-compatible game controllers, and doesn't apply to the majority of developers.

Registry tweaks for gaming