You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After 6552ae1, the order of the init
function calls changed, and then the platform was not initialized
correctly.
This change fixes this issue by not relying on an init function to
get the platform.
Closes#2964
hajimehoshi
changed the title
internal/gamepad: PS5 Dual Sense bluetooth controller's standard mapping doesn't work on Windows
internal/gamepad: gamepad standard mappings don't work
Apr 18, 2024
Ebitengine Version
v2.7.1
Operating System
Go Version (
go version
)go version go1.22.0 windows/arm64
What steps will reproduce the problem?
examples/gamepad
What is the expected result?
The gamepad is mapped as
XInput Controller (GLFW)
with a standard mappingWhat happens instead?
The gamepad is mapped as
Xbox Controller
without a standard mappingAnything else you feel useful to add?
This works with Ebitengine v2.6.7
The text was updated successfully, but these errors were encountered: