There are no Android mappings for this Controller in the list. I’ve tried to copy the entries from Windows, but without luck. Is there an Android tool to create the mapping string?
I’m not sure how to best do that easily at this moment.
Asking internet, they mention building the SDL controllermap as a test app an running that on the device. I haven’t looked into that currently.
Please create a Github ticket with this information so that we can keep a track of it.
LTRIGGER and RTRIGGER have -1 on NOT PRESSED state on axis 5 and axis 6 for my 8Bit Ultimate Wireless 2C. 1 on PRESSED. So the tool does not work, without an extra fix.
I’m not sure if I get mapped or raw mapping data. On Windows I get “Gamepad 0 ‘8BitDo Ultimate 2C Wireless Controller’ guid=0300f57bc82d00000a31000000007200 using automatic mapping.”
I’ve tried to us and empty gamepad and gamescontrollerdb.txt, but still the “automatic mapping” message. Is in this case mapping hardcoded in defold engine? How can I force to get raw input data?
To clarify, this is still on Android?
Yeah, the automatic part was intended to help with the XInput devices, but we also want to make sure it’s possible to get raw input if all mappings fail
This requires some more though imho
No, I develop and test the tool under Windows. So if it is a hardcoded mapping I think the values for LTRIGGER and RTRIGGER are not right. Should be 0 when unpressed and not -1 for this 8Bit Ultimate 2C.
Will try now under Android, to see what data I get back here for the Trigger Buttons and if can map with the tool.
Well, the “automatic” fallback is trying to replicate how the SDL Gamepad Tool does the mapping.
In short, using a default XInput mapping.
Yeah, this works
Did the controller not work for you on windows?
It works for me here
How can I force to get raw input data?
Or, are you explicitly talking about what the GAMEPAD_RAW returns?
See the example-gamepad test app does, it includes the GAMEPAD_RAW input event, which allows you to look at the raw data.
The idea of the raw data is that we pass it on as-is, and let the developer handle the input.
OK, I got GitHub - j-h-a/defold-gamepad-mapper · GitHub to run on Android after some fixes and can map the 8bit 2C and create an old gamepad structure. Claude converted it so the new SDL format, I’ve created an Android app of the GamePadTester and it works. There is just one problem caused by Android. Some buttons like LPAD_CLICK, RPAD_CLICK and HOME (or is it Guide?) fires two events. One A Button following the real button event. You can see this also in the GamePadTester on Android. This is an Android problem. I’m not sure if this is still a problem in Android 16. Will test this tomorrow. It would be great if this can somehow fixed/filtered in the engine.