Finding the name of a gamepad when GDC doesn't work

Questions
1

I’m investigating a crash possibly caused by the name of a gamepad.

I asked the user with the gamepad in question to download gdc and run it to grab the name, but perhaps unsurprisingly that crashes too.

I’ve tried a few browser based gamepad testers, but the name they return isn’t what I see in Defold.

Is there another way I can get the gamepad name out of them?

Or put another way - what’s the API Defold uses? Maybe knowing that I can ask the user to download another utility based on the same thing?

2

This might not be helpful in terms of earning the user’s help, but it might work to run a Linux boot USB long enough to ask the terminal what the device calls itself, with no encumbrance on the user’s HDD.

2 Likes
3

Thank you, the user self-describes as non-technical though so I suspect it might be difficult to pull off. I wouldn’t even know where to begin myself!

4

The debug build of the game prints the name in the logs if the gamepad is not found in the list, like:
WARNING:INPUT: No gamepad map found for gamepad 0 (XBox 360 Controller). The raw gamepad map will be used.

But probably it doesn’t get that far and the game crashes earlier?..

I think you need to get a crash dump from the player, if possible, and then we’ll be able to figure out where and how the crash occurs.

5

Thanks! Yes, we have the crash dump. This is the issue in question:

1 Like