6 stable releases

Uses old Rust 2015

1.3.0 Dec 17, 2023
1.2.1 Oct 22, 2023
1.2.0 Apr 8, 2019
1.1.0 Mar 10, 2019
1.0.0 Feb 16, 2018

#112 in Hardware support

Download history 537/week @ 2024-01-01 1042/week @ 2024-01-08 1052/week @ 2024-01-15 771/week @ 2024-01-22 610/week @ 2024-01-29 1087/week @ 2024-02-05 1202/week @ 2024-02-12 1370/week @ 2024-02-19 1273/week @ 2024-02-26 1159/week @ 2024-03-04 993/week @ 2024-03-11 1176/week @ 2024-03-18 1455/week @ 2024-03-25 1677/week @ 2024-04-01 1040/week @ 2024-04-08 1258/week @ 2024-04-15

5,578 downloads per month
Used in 83 crates (5 directly)

Zlib OR Apache-2.0 OR MIT

45KB
722 lines

CratesIO DocsRS Appveyor

rusty-xinput

Dynamically loads an xinput dll and lets you safely call the functions.

If you want to use other controller types

If you have a controller that doesn't have an XInput driver it probably uses DirectInput instead. The DirectInput system isn't bound within the winapi crate because I'm too lazy to go make that PR and no one else cares.

Instead I can suggest you two options:

  • You can tell your users to try the Controller Emulator program. It lets you setup the device you want and then spits out an XInput DLL to use that will read the desired device. Place the generated DLL into the same directory as your executable under the name xinput9_1_0.dll and it'll get loaded instead of the system level version. See their site for more info.

  • You can use the multiinput crate, which uses the rawinput system, which will also include things like DirectInput devices. I don't know the guy that makes it and I haven't used it myself, I just found it on crates.io and it's the only other gamepad library that's even been updated in the past year.

Dependencies

~54–270KB