Methods for having any connected gamepad device be interpreted the "same" by games/emulators(?)
This is a difficult question to phrase. My situation is that I have a living room game system running Bazzite. I have my system boot into desktop and boot up ES-DE as the front-end. I have four Bluetooth gamepads. Sometimes I play directly on the system itself, other times I stream into it from my bedroom PC via Sunshine/Moonlight.
The problem I'm having is that the controllers are assigned completely differently when connecting directly via Bluetooth vs. when streaming from another PC. Moonlight seems to have a built-in way of dealing with controller mappings and IDs, where everything is interpreted by the "server" system as an Xbox 360 controller. This is at odds with how the controllers are picked up when connecting them directly. Some games and emulators have no issues at all with the difference, and seem to just know which input is which. Others have jumbled controls - the "axes" especially (analog sticks and triggers) tend to get completely juggled around. And others (probably due to some ID being different) can't recognise the controller at all, and need to be completely re-mapped each time I switch from normal play to streaming or vice-versa.
I'm trying to find an actively maintained program or tool that can do something similar to what Moonlight does, but which also works when directly connecting controllers. I essentially need any connected controller device, whether it be real or connected virtually by Sunshine/Moonlight, to be "mapped" to the same ID and have all the buttons and axes match up. The goal is that regardless of what controller I connect or whether it is real or virtual, the controller devices and mappings I have set in my emulators and games will work right away.
Any pointers in the right direction are appreciated!
0 Replies