bevy-hid
| Crates.io | bevy-hid |
| lib.rs | bevy-hid |
| version | 0.1.3 |
| created_at | 2025-12-24 20:03:27.196276+00 |
| updated_at | 2026-01-16 16:11:44.854202+00 |
| description | A hid plugin for bevy |
| homepage | |
| repository | https://github.com/fishykins/bevy-hid/ |
| max_upload_size | |
| id | 2003786 |
| size | 150,332 |
Fishy (fishykins)
documentation
README
Bevy-hid
Support for the Windows HID device protocol in Bevy.
About The Project
Bevy-hid is an alternative to the the default bevy-gilrs crate, implimenting the Human Interface Device Windows protocol instead. This is a more involved approach to peripheral connectivity and allows for the use of less standard devices as game input, as well as providing a simple yet powerful mapping system for unknown devices. Because this approach takes advantage of the base bevy input system, it can seemlessly integrated into other input libraries (e.g. LIM) with no extra code required. You can absolutely run this layer in conjunction with bevy_gilrs, you just might end up with two coppies of the same device doing slightly different things.
If you have a device with lots of buttons and axes that simply wont map onto the standard "console controller", such as a flight stick or throttle, this is what you need!
Limitations
This crate is dependant on mappings being created, and as I only own two devices, building a map for your device is not something I can do! Currently there are no tools for doing so, but rest assured its very easy to do. I will add tooling for this soon. Things like force-feedback are not yet supported, but could be added later down the road.
Getting Started
Pop on over to crates.io and grab a copy of the latest release!
Optional features
License
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Contribution
Contributions are both welcome and appreciated!
Contributions in any form (issues, pull requests, etc.) to this project must adhere to Rust's Code of Conduct.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
If you are a device vendor and you want your gear to be natively supported, please get in touch. If you are not a device vendor but you want to send me a device for testing, also get in touch. If you are an AH-64 Appache helicopter, you are in the wrong place. try the War Thunder forums.
Contact
Caspar Green - caspar.m.green@gmail.com
Project Link: https://github.com/fishykins/sticky-joy