Kif you are manually installing hhd, that could be the source of your issue
FOkey, i reinstall the os
Hyo
HI can't get the keyboard to work on the Bazzite install
Hcan I just go rootless
Hand enable root later
Hwait shit that doesn't help with
Hmaking a user account
Hokay how do I convince a keyboard to work when it doesn't want to
Kyou plugged one in?
Kno touch keyboard in the installer (yet)
Hyup
Kif this is with a deck it may be that your keyboard needs more power than it has on offer, try a powered USB hub or a dock
Hboard is Akko World Tour Tokyo through USB-C
HI did, still didn't work
Konly other option then is to try a stock fedora kinoite/silverblue installer and see if it works any better for you
Kyou can rebase to bazzite from there
A@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..
Ahrm, i have never had it happen before, but I can test in a bit. is this mGBA standalone? or mGBA retroarch core?
AI believe mGBA standalone/(whatever emudeck installed)
Aemudeck defaults to retroarch, i think
Aunless you explicitly enabled standalone
Aanyways, retroarch is kinda odd because it actually ships it's own separate controller configs
Ait could be related to the issue you're seeing
Alet me try testing gba in a bit
M@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.
M—force-external-panel or whatever the exact syntax for that is didn’t seem to make a difference
MIf 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.
Ahrm, so on the LGO i can use multitouch with waydroid in gamescope-session
Atouch seems to be working fine there
Aperhaps waydroid is different somehow
Mhttps://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
GitHub
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'...
AAfter 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
AI 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
MI even tried settings an Always On Command for Touchscreen Native Support via steam input on the ally but that didn’t seem to help
MI thought maybe it was game-specific because civ v has a Linux port but both had issues with touch input on my ally
AOk yeah it looks like mGBA only wants to take input from the hhd dualsense edge controller while in desktop mode
Amake sure you're running the emulators through steam on desktop mode, that way it's seeing controllers through steam input
Afunky
AGotcha, adding the emulator as a non steam game and running it that way does that, correct?
Ayep, exactly
AGitHub
Adds the the Dualsense Edge Controller config, the linux version of which is missing.
Adds the Handheld Daemon Controller config, which is a controller created by the Handheld Daemon to perform rem...
Adds the Handheld Daemon Controller config, which is a controller created by the Handheld Daemon to perform rem...
Aantheas did add hhd support to retroarch controller configs
Aso it should theoretically just work if retroarch is updated
Abut let me try to replicate the issue now
Ahrm, so gba worked no problem for me w/ dualsense edge emulation
Awas able to boot into the game + use the d-pad right away
AIm looking into updating retroarch (it should already be up to date b/c I installed everything like 2 days ago) and it gave me an interesting error message "was not able to configure dualsense controller, using fallback" or something similar when opening the program
AExcuse the scuffed screenshot
Awell, i guess it at least recognizes it as a dualsense edge controller
