Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

examples/gamepad: PS4 (Dualshock) bluetooth controller inputs not detected on Windows #2967

Open
1 of 11 tasks
Hatchibombotar opened this issue Apr 24, 2024 · 8 comments
Open
1 of 11 tasks

Comments

@Hatchibombotar
Copy link

Hatchibombotar commented Apr 24, 2024

Ebitengine Version

2.7.2

Operating System

  • Windows
  • macOS
  • Linux
  • FreeBSD
  • OpenBSD
  • Android
  • iOS
  • Nintendo Switch
  • PlayStation 5
  • Xbox
  • Web Browsers

Go Version (go version)

go1.22.0 windows/amd64

What steps will reproduce the problem?

What is the expected result?

Button inputs are recognised

What happens instead?

image
No other output appears after these lines.

Anything else you feel useful to add?

Using a ps4 dualshock controller, but may not be exclusive to this one. I don't have another one to test with.
Windows 11 Home, 23H2
Example works in the web browser

@hajimehoshi
Copy link
Owner

Which USB or bluetooth was the controller connected? Thanks,

@hajimehoshi hajimehoshi added this to the v2.8.0 milestone Apr 24, 2024
@Hatchibombotar
Copy link
Author

It was connected by bluetooth. Just tested now and connecting by USB does work

@hajimehoshi
Copy link
Owner

OK, this doesn't work only when connecting it via bluetooth. Another question: does this work with Ebitengine v2.6.7?

@Hatchibombotar
Copy link
Author

It does not.

@hajimehoshi
Copy link
Owner

Sure, so this is not a regression. TBH I'm not sure I can fix this, but I'll tackle this tomorrow. Thank you for reporting this!

@hajimehoshi hajimehoshi changed the title PS4 (Dualshock) controller inputs not detected examples/gamepad: PS4 (Dualshock) bluetooth controller inputs not detected on Windows Apr 24, 2024
@SolarLune
Copy link

@Hatchibombotar - Hello, just to double-check, did you iterate through other gamepad ID's, just to see if it's reported as ID 1 or 2, by chance?

@hajimehoshi
Copy link
Owner

I failed to reproduce this issue on my Windows (Parallels):

PS Microsoft.PowerShell.Core\FileSystem::\\Mac\Home\ebiten> go run .\examples\gamepad
2024/04/26 00:29:04 gamepad connected: id: 0, SDL ID: 78696e70757401000000000000000000
2024/04/26 00:29:08 button pressed: id: 0, button: 1
2024/04/26 00:29:08 standard button pressed: id: 0, button: 1
2024/04/26 00:29:08 button pressed: id: 0, button: 0
2024/04/26 00:29:08 standard button pressed: id: 0, button: 0
2024/04/26 00:29:08 button released: id: 0, button: 1
2024/04/26 00:29:08 standard button released: id: 0, button: 1
2024/04/26 00:29:08 button released: id: 0, button: 0
2024/04/26 00:29:08 standard button released: id: 0, button: 0

@hajimehoshi
Copy link
Owner

Your ID was 030000004c050000c405000000000000 (PS4 Controller) while mine was 78696e70757401000000000000000000 (XInput Gamepad (GLFW)). I'm not 100% sure but upgrading or installing DirectX might resolve the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants