Skip to content

Xb2XInput v1.41
Compare
Choose a tag to compare
@emoose emoose released this 08 Jul 23:26
· 5 commits to master since this release
v1.41
60cddbf

Read the Setup/Usage sections of the README to learn how to set it all up, really it only takes a minute or two.

A list of supported controllers can be found at the top of XboxController.cpp

If you have a controller that isn't on this list, or a controller that is on the list but won't work, feel free to make an issue about it on the issue tracker (please include the hardware ID of the controller though - see "Support" section in the readme)

Changes from v1.3

  • (v1.41) Allow button remapping via INI settings - the included Xb2XInput.ini file should explain how this works.

  • (v1.41) Default settings for new controllers can now be customized, see the [Default] section inside Xb2XInput.ini

  • (v1.41) "Enable guide combination" choice is now respected (previously the value was ignored, and guide combo was always enabled)

  • (#15) Improved Multi-Controller Reliability - thanks to skajacore!

  • (#16) Added Deadzone Functionality - thanks to skajacore!
    Deadzone can be configured either via INI file or through button-combinations (right-click the systray icon to see the combinations)
    Any changes made to the deadzone will be saved back to the INI & loaded in next time XB2X is launched.

  • Added per-controller submenus to configure vibration/guide-button & view deadzones.

  • Now reads/writes config from a INI file with the same name as the EXE.
    This INI stores any desired guide-button combination along with per-controller config: whether vibration/guide-button combination is enabled for this controller, and any chosen deadzones for the sticks & triggers.
    (unfortunately some controllers can't be uniquely identified via a serial number, so for those INI will store & apply settings based on the controllers VID/PID instead)

  • Added an example Xb2XInput.ini file with all the config options included & described - note that the INI isn't required for Xb2XInput to run though, as the EXE will create a new INI if needed.

Todo

  • Find a way to uniquely ID controllers without needing a serial number?
    I think Windows must be creating some kind of identifier for them, since IIRC it seems to remember the installed driver no matter which USB port is used...

  • Allow customizing deadzone combination in the INI file.

  • Update README with info about submenus/INI/deadzones

  • Replace wdi-simple, or at least add a wrapper which detects attached devices and only runs wdi-simple for those ones...

Assets 3
Loading