@Aru out of curiousity, if youve messed with game emulation on legion go and bazzite, have you ever had an emulate refuse to map D pad inputs for you? I am in dualsense edge mode and specifically the dpad doesnt work for mGBA etc..
@Kyle Gospo got a cross-distro bug to flag for you. Seems like touchscreen input is not being interpreted correctly on non-deck handhelds on both nobara and bazzite right now. It seems like the first touch input after launching a game works correctly, but after that point tapping the screen basically no longer acts like a touchscreen at all. Pulling out the steam menus from gamescope-session remain working, so it’s only in-game input.
If I pull up Hades on both my OLED Deck and my ROG Ally, I can navigate the UI without issues on the Deck but touch input is only good for the first tap on Ally.
https://github.com/hhd-dev/hhd/issues/38 I’m just following up on this after antheas tagged me thinking it was nobara-exclusive, but I’ve come to find my ally performs exactly the same on both nobara and bazzite
in many games when i need to use the touch screen (miniMetro, Civilisation 5, VRChat) it doesn't work sometime a cursor appears but no always i can't click when a game is runing. i don'...
After messing around a bit, it seems that mGBA doesnt have an option to take input from the "dualsense" controller for me, it defaults to xbox 360 and the drop down menu shows no other controller option, and when I turn on fps mode and refresh available inputs it just becomes blank
I swapped to mGBA standalone to see if it has different behavior and it seems like it does "see" dualsense in desktop mode, but let me see if i can reproduce that