Input Bindings device pass

[jukibom]

We've had a LOT of complains (and bad reviews) about device binding. Some devices are binding fine, some are not - this just needs generally investigating. There are a couple of options...

• Switch to paid Unity addon ReWired, which a lot of people seem to end up doing. While I'm not at all against spending the money, this sucks because it's another paid dependency which hurts the ability for people to easily build this repo and contribute fixes (especially as input is such a fundamental part of the game).

• Actually buy some of these failing devices and write a HID fallback for them - this sucks for obvious reasons! The more niche the device, the more expensive it is.

• Start a separate open repository with the aim to fix these issues in an open community way - provide a simple testbed for detecting devices, applying binds and allow people to contribute custom profiles for devices they have by generating some kind of document describing the device which I can then turn into a HID Fallback and re-submit to the repo for other developers. This would be an enormous undertaking :/

• Investigate the issue and see what's causing certain very specific devices (e.g. rudder pedals) to almost universally fail - it might be something dumb that Steam is doing or something dumb I'm doing with pairing devices, and the times at which they're paired. It may then be worth writing up an FAQ to point users to.

[Dthen]

Investigate the issue and see what's causing certain very specific devices (e.g. rudder pedals) to almost universally fail - it might be something dumb that Steam is doing or something dumb I'm doing with pairing devices, and the times at which they're paired. It may then be worth writing up a FAQ to point users to.

This seems like the approach to try first. I, as someone who (admittedly with no knowledge of coding, but I reckon I could learn the Unity editor), would be sad to see more obstacles in the way of community contribution, as I'd love to learn the editor enough to at least make custom races in custom environments.

Start a separate open repository with the aim to fix these issues in an open community way - provide a simple testbed for detecting devices, applying binds and allow people to contribute custom profiles for devices they have by generating some kind of document describing the device which I can then turn into a HID Fallback and re-submit to the repo for other developers. This would be an enormous undertaking :/

This is the best way forward, in an ideal world, but relies heavily on people noticing it and contributing to it. It will take forever.

Actually buy some of these failing devices and write a HID fallback for them - this sucks for obvious reasons!

This really does suck. I imagine the community would be willing to help with the financial burden of sourcing them. Is there a way you could write some kind of diagnostic thing for other people who already have those devices to run for you and send the results to you? That would be cheaper, but would you be able to get enough useful information that way?

The upside to this path is that other people would benefit from it and be able to use your hard work.

...The pedals thing and the yaw thing really are kind of strange, though.

PS: Reading through my reply again, I realise that I have basically suggested you do something somewhere in between idea 2 & 3.

[jukibom]

for future reference, maybe https://www.youtube.com/watch?v=YNNVGGulscc

https://forum.unity.com/threads/controller-wrongly-characterized-as-joystick-for-input-logitech-dual-action.879454/#post-8170850

[jukibom]

I've made a start on an actual tool to build device bindings which will live in a public community repository in the hope that this will resolve the issue for fly dangerous and all other unity games. I'll open the repo up once the tool is actually in a usable state.

https://github.com/jukibom/FlyDangerous/assets/5649179/0d37f713-e402-430a-a4c4-1a5383981736

[jukibom]

https://github.com/jukibom/unity-community-input-device-layouts

still very much a work in progress ...