search

flightlessmango / MangoHud

A Vulkan and OpenGL overlay for monitoring FPS, temperatures, CPU/GPU load and more. Discord: https://discordapp.com/invite/Gj5YmBb
MIT License
6.52k stars 287 forks source link

MangoHud doesn't work properly when the "gamepad_battery" option is used with a 8BitDo controller #694

Open italoghost opened 2 years ago

italoghost commented 2 years ago

Hi!

I was trying to launch some games with the "gamepad_battery" option enabled while my 8BitDo Pro 2 was connected, but they would fail to launch or be very very slow - GOverlay wouldn't even open when my controller was connected and with this option active.

This behaviour doesn't happen with my DS4 controller. I can launch every game normally with the "gamepad_battery" turned ON.

System Information:

gort818 commented 2 years ago

Thanks for the report, I will look into this when I have some time.

italoghost commented 2 years ago

I don't know how to get log information about this issue but if it helps and you tell me how to get it I will happily provide!

rc345ct243tc commented 2 years ago

I am observing this issue too, after upgrading to Fedora 36. I do not have gamepad_battery enabled in the config file, but it still seems to appear on the HUD and causes games to basically run at 1fps and hang.

This wasn't happening on fedora 35. I didn't have gamepad_battery enabled and it didn't appear on screen either.

gort818 commented 2 years ago

I think at this point I will just remove the 8BitDo stuff as it hasn't really worked properly, all other controllers seem to work just fine

gort818 commented 2 years ago

Can you build the latest master, and see if it helps?

rc345ct243tc commented 2 years ago

Thanks. The fix works.

Any idea when we can expect a release (and a rebuild on the distro's end)?

gort818 commented 2 years ago

Just to clarify, you have an 8BitDo controller as well? Is gamepad_battery causing any issues when enabled?

We should be able to get a hotfix out. On distro's end I have no idea.

italoghost commented 2 years ago

@gort818 I tested here on Arch Linux and it is now working as well!

image

gort818 commented 2 years ago

@italoghost That is great news thank you for testing!

rc345ct243tc commented 2 years ago

Hmm, that's strange. I do not get the gamepad battery indicator, even after enabling it in the config. I'm using an SN30 Pro+ in xinput mode.

gort818 commented 2 years ago

How about in the other mode?

rc345ct243tc commented 2 years ago

Negative. I've tried the switch mode and the x-input mode. The battery indicator doesn't show up in both cases. @italoghost which mode is your controller in?

This isn't a big deal for me anyway. I just wanted the HUD to get working without the game being problematic, which is fixed nw.

italoghost commented 2 years ago

I tested with the xinput mode!

hajosattila commented 1 year ago

same problem here. The battery indicator doesn't show up

ReillyBrogan commented 1 year ago

I think this is an issue either in the firmware, the bluetooth stack, or the kernel driver. I've noticed that the battery indicator shows up in other upower-enabled applications (such as the Plasma powerdevil widget) only sometimes. When the controller shows up there the power indicator in mangohud works as expected, when it doesn't the mangohud indicator is not present as well. Has anyone looked into this as a potential kernel/bluetooth issue? I don't have Windows to check, but has anyone noticed the battery not being visible there when it should be?

hajosattila commented 1 year ago

For me, the 8BitDo Pro 2 controller is the only device that is not recognized by the system after it has been switched on. In each case I have to wait 15-20 seconds before Arch (Yuzu, Steam etc) recognizes it. All other Bluetooth devices that I have previously added using bluetoothctl are immediately recognized.