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

Wireless controller not recognised #57

Open
flipflop97 opened this issue Apr 1, 2023 · 4 comments
Open

Wireless controller not recognised #57

flipflop97 opened this issue Apr 1, 2023 · 4 comments

Comments

@flipflop97
Copy link

flipflop97 commented Apr 1, 2023

I'm trying to play using my 'Xbox One Wireless Controller', but it doesn't seem to be recognised at all. Creating a gamepad file in ~/.var/app/io.mrarm.mcpelauncher/data/mcpelauncher/gamecontrollerdb.txt also doesn't change anything. The game and my controller work fine otherwise.

EDIT: The controller is detected and working properly using a cable, but not when connected via Bluetooth. The controller works fine via Bluetooth in all other Flatpak apps.

Flatpak launcher version: v0.8.5
Minecraft version: 1.19.71.02

@ChristopherHX
Copy link
Member

I also have a 'Xbox One Wireless Controller', I think you use the bluetooth connection otherwise the controller should work.

As far as I remember I have to use the usb cable in the flatpak build. I have no idea how make the bluetooth pass the flatpak sandbox.

The AppImage should detect your Controller by default, because it has no sandbox.

@flipflop97
Copy link
Author

Just tested it with cable, and that works indeed! The problem is in the handling of wireless controllers then probably, or a Flatpak packaging one.

@flipflop97 flipflop97 changed the title Controller not recognised Wireless controller not recognised Apr 2, 2023
@ChristopherHX
Copy link
Member

See this PR flathub/io.mrarm.mcpelauncher#107

This is an eglut build of the flatpak and should have the exact same features as the AppImage.

Based on my tests is my 'Xbox One Wireless Controller' working in that eglut build, after adding an env variable to switch to glfw this can land in the flatpak. Everyone who have issues with eglut can then switch back to glfw.

You can install the test build, if you also have the normal flatpak you might need to type flatpak run io.mrarm.mcpelauncher//test to start it.

@ChristopherHX
Copy link
Member

Creating a gamepad file in ~/.var/app/io.mrarm.mcpelauncher/data/mcpelauncher/gamecontrollerdb.txt also doesn't change anything. The game and my controller work fine otherwise.

This works if you put the correct line into it. Maybe I can reenable the controller warning via a setting option.

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

No branches or pull requests

2 participants