FIGHTING BOX mini doesn't work

[shinriyo]

Describe the bug

FIGHTING BOX mini doesn't work.
Down and Up key of the controller detects as Down only.
And X,Y, A, B RB, RT key are detected as selection function.
But they can't be detected in Joystic Config page.
https://ja.aliexpress.com/item/1005006099279923.html

To Reproduce

Connecting the controller and and go to OPTION -> Input Settings -> Key Config and Joystic Config.

Expected behavior

Beging detects all of keys.

Screenshots / Video

Engine Version (or source code date)

v0.99.0-macos

Operating system

macOS

Extra context or search terms

If you tell me the source code is. I might be able to fix the Go code. Perhaps.

[Jesuszilla]

0.99.0 is really out of date. Have you tried the nightly? Also, it advertises Switch support so you may have better luck on macOS when it's plugged in Nintendo Switch mode.

[shinriyo]

@Jesuszilla

Thank you for replying.
I didn't realize the nightly version.
I will try it.
https://github.com/ikemen-engine/Ikemen-GO/releases/tag/nightly

[shinriyo]

I tried, but unfortunately, the same behavior was observed.

[Jesuszilla]

Can you run IKEMEN-Go from terminal please? Does it have any output when you go to joystick config?

[shinriyo]

@Jesuszilla

In JOYSTICK CONFIG screen, it happned.

[input_glfw.go][checkAxisForTrigger] 1.AXIS joy=0 i=2 s:-5 axes[i]=-1
[input_glfw.go][checkAxisForTrigger] 1.AXIS joy=0 i=2 s:-5 axes[i]=-1
[input_glfw.go][checkAxisForTrigger] 1.AXIS joy=0 i=2 s:-5 axes[i]=-1
[input_glfw.go][checkAxisForTrigger] 1.AXIS joy=0 i=2 s:-5 axes[i]=-1
[input_glfw.go][checkAxisForTrigger] 1.AXIS joy=0 i=2 s:-5 axes[i]=-1
[input_glfw.go][checkAxisForTrigger] 1.AXIS joy=0 i=2 s:-5 axes[i]=-1
[input_glfw.go][checkAxisForTrigger] 1.AXIS joy=0 i=2 s:-5 axes[i]=-1

I think it is not related but I appeared in the first.

[Jesuszilla]

Thank you. It didn't report any model, which is unfortunate, but it seems I never added that to input_glfw.go to assist in debugging. I'll try to get that in next nightly so that the problematic axes can hopefully be identified for the correct model.

The message you get in the window is not related but you can resolve that by disabling EnableModelShadows by setting it to false in save/config.json. Actually, it appears the build somehow reverted to GL 2.1 which may be the cause as I get the error on my MacBook M3 as well.