![]() To make an informed choice read the "Windows Input Source" section in Rewired Editor Settings documentation.Īlso read the sections above about SDL2 and the limitations of DirectInput and XBox controllers above. Use the Native Input Module [and disable XInput This is because the SteamInput feature presents the controllers as emulated XBox controllers to the XInput API and filters out the controllers for other APIs to avoid ghosting. If controllers are configured to use the SteamInput feature in Steam, but a game doesn't use the Steam Input API, the number of SteamInput configured controllers is capped to 4. The game needs to call the SteamInput API to access the controllers in order to make use of this. * If this is the only or primary API for accessing the controllers make it so that SteamInput is enabled by default for your game. * Dependency to the Steam Client? (Not sure if there is a standalone thing so the SteamInput can be used without Steam.) * Up to 16 XBox controllers when the user has activated XBox Extended Feature Support in Steam. * At least 16 controllers, possibly limitless? SteamInput API (not the same as the SteamInput feature) ![]() If it's not working make sure the hints SDL_HINT_JOYSTICK_RAWINPUT and SDL_HINT_JOYSTICK_HIDAPI_CORRELATE_XINPUT are set. (Thanks to some innovation in SDL2 this will hopefully this will change.) Why is that? Because there is no easy way for the frameworks to know which of the XBox controllers have been enumerated via XInput so they often just filter away all of XBox controllers so they aren't enumerated by the other APIs which would result in ghost controllers. They often support several input APIs but most by default don't support more than 4 XBox controllers. Input Frameworks:Input frameworks are often used in order to support a wide range of controllers, add configurable controller layouts and support hot plugging. * Not sure if only XBox Controllers are supported. * Can control the extra 2 rumble motors on XBox One controllers. * XBox controllers have rumble and triggers on separate axes. * Supports more than 8 controllers on Windows 10. ![]() * Used for the Universal Windows Platform (Windows 10, XboxOne, etc.) * Use an input framework if you want to support several underlying APIs in order to support non XBox controllers or other older Windows OS or more conveniently also support Mac/Linux. * XBox360 and XBox One controllers don't have rumble and both triggers are on the same axis so you can't detect if both are pressed at the same time. * Use an input framework so you don't have to deal with Raw Input directly, especially if you want to support a wide range of controllers. * XBox360 and XBox One controllers don't have rumble and both triggers are on the same axis so you can't detect if both are pressed at the same time, this is because of the XBox controller driver implementation. Use an input framework so you don't have to deal with DirectInput directly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |