Documentation

• Overview
• Release Notes

1. Installation
2. Quick Start
3. Basic Usage
4. Deployment
5. Best Practices
6. Rewired Editor
7. API Reference

• Input Manager
• Players
• Actions
• Input Behaviors
• Controllers
• Controller Maps
• Controller Templates
• Map Categories
• Layouts
• Layout Manager
• Map Enabler
• Custom Controllers

• Control Mapper
• Glyphs
• Touch Controls
• Unity Input Override

• Rewired Standalone Input Module
• Component Controls
• Player Controllers
• Input Mapper
• User Data Store
• Custom Platforms
• Localization

• See all topics...

• Supported Controllers
• Tested Platforms
• Troubleshooting
• Known Issues
• Special Platform Support
• Examples
• Integrations
• Updating Rewired

• See all topics...

• Unity Manual
• Unity Script Reference
• Unity Tutorials

• Rewired Website
• Web Documentation

Supported Controllers

Rewired supports most USB and Bluetooth controllers available, many with extended support.[1]

Controllers with Extended Support

Controllers with hardware definitions are recognized on each platform and are fully mappable by element name, have standardized axis directions, and may be compatible with aController Template for easy mapping. For all other controllers that do not appear in the following tables,please see this important note.

Rewired currently includes extended support for the following game controllers as of version 1.1.60.0:

All other controllers not listed above

Any controller which does not have a hardware definition will be usable only through user mapping or by mapping actions to numbered axes and buttons in theUnknown Controller map. These unrecognized controllers can only be supported if you provide your users a way to remap their controls, such as by using the includedControl Mapper or by creating acustom control remapping screen. If you do not provide users with a way to map their controls, only the above listed recognized controllers will be usable. If you do provide your users a way to map their controls, virtually any controller will be usable.

You can also create your own controller definitions to add extended support for more controllers, but the process can be involved, especially if you want to support all platforms. (SeeCreating new controller definitions for more information.) However, be advised that not all controllers are candidates for controller recognition. (SeeCan I add support for this controller? for more information.)

Controllers that map to the keyboard

Controllers such as the X-Arcade Tankstick that map to keyboard keys are supported only through keyboard maps at this time. The process for mapping one of these controllers is identical to mapping keyboard keys. You have to identify which keyboard key each controller element maps to (see the documentation for your controller), then assign actions to those keys in the keyboard map. If you have a user control mapping screen, users can map their controls directly.

Controllers not directly supported (yet)

• Controllers that map as additional keyboards
• Controllers that map as additional mice

Certain controllers may appear as an additional keyboard or mouse. These controllers currently may not work correctly. If the controller allows you to map its inputs to the primary keyboard, then it will work through the use of a keyboard map. If they show up as a second keyboard or mouse, they will likely not work.

Adding support for additional keyboards and mice is possible, and the feature may be added in the future if there is enough demand.

Controllers not supported at all

• Serial port or game port controllers.
• Controllers not supported by Raw Input, Direct Input, or XInput on Windows, I/O Kit on MacOS, udev on Linux, or the input API(s) in use on the particular platform in question.
• Controllers not supported by Unity on fallback platforms.
• Controllers that require a special SDK.
• Some very exotic controllers.

Some of the above controllers may be indirectly supported through the use ofCustom Controllers.

Steam Controller

The Steam Controller automatically emulates an XInput gampad (XBox 360) on Windows, MacOS, and Linux and is supported as an XInput gamepad. No direct support of the controller's special features is available at this time.

For more information on using the Steam Controller, seeTroubleshooting - Steam Controller andBest Practices - Steam.

Android unknown gamepad support

In addition to the devices shown in the table above, Rewired has an option to attempt to support all unknown gamepads. On theRewired Input Manager - Settings page, enable the option "Support Unknown Gamepads."More information about how this option works and caveats can be found here.

Oculus Touch and Oculus Remote support

Oculus Touch is only supported through Unity's input wrapper for the Oculus Touch API. Unity exposes the devices as 3 joysticks through UnityEngine.Input. They have exposed the controllers as joysticks with most functionality excluding positional/rotational information.See this page for more information.

In order to use these devices with Rewired, you must disable native input in Windowsby setting the Primary Input Source to "Unity." Be aware that by disabling native input in Rewired, you lose many important features for other devicesas described here. In addition, you cannot use XInput together with Unity input so you lose several important features of XInput (universal XInput device support, vibration, etc.)

An alternate way to support these controllers is by accessing the API directly and using that information to drive aCustom Controller. Using this method, you can leave native input enabled and retain access to all the important features that native input provides.

OpenVR Controller support

HTC Vive is only supported through Unity's input wrapper for the OpenVR API. Unity exposes the devices as 2 joysticks through UnityEngine.Input. They have exposed the controllers as joysticks with most functionality excluding positional/rotational information.See this page for more information.

In order to use these devices with Rewired, you must disable native input in Windowsby setting the Primary Input Source to "Unity." Be aware that by disabling native input in Rewired, you lose many important features for other devicesas described here. In addition, you cannot use XInput together with Unity input so you lose several important features of XInput (universal XInput device support, vibration, etc.)

An alternate way to support these controllers is by accessing the API directly and using that information to drive aCustom Controller. Using this method, you can leave native input enabled and retain access to all the important features that native input provides.

WebGL platform controller support

At this time, most controllers on WebGL are only supported via manual user mapping of controls at runtime through the use of a system likeControl Mapper. Please seethis for important information on the state of controllers support in web browsers.

The information in the following table shows which controllers have been mapped for the different browsers running on different operating systems. The operating system and browser versions shown are the versions that have been tested. For gamepads that do not use the Standard Gamepad mapping mode, because at any time the browser manufacturer may decide to create a Standard Gamepad mapping for a controller causing the mapping layout to change, extended support cannot be guaranteed for any browser versions but the ones shown.

SDL2 Gamepad Support

SDL2 is an optional input source for Rewired on Windows Standalone, MacOS Standalone, and Linux Standalone builds. Below are the current SDL2 mappings included with Rewired. Note: Controller support through SDL2 is not as robust as with Rewired's custom native support.