the wrapper is to load extest, which enables steam input on wayland desktop
the wrapper is to load extest, which enables steam input on wayland desktop
FThanks. I don't think the VR issue applies to me as I don't use VR, and I've been using Flatpak version just fine. What package name should I provide in my recipe to remove it? It's a good addition for non-tweakers, but I prefer to keep my autostart/script/etc consistent in all my images and I use Bazzite for PC but Kinoite for laptop...
Kalso applies -steamdeck, which is needed on steam deck hardware
FOh, is that an issue with flatpak version as well? I admit I haven't played a lot lately, so I might have missed it (though the latest Flatpak pre-release has support for
--devive=input permission and they're currently working on a usb permission)
Kyeah, steam uses xtest exclusively
Kso it affects every copy
FHm, does that effect controller? Or are we talking about Steam Input in the context remote play?
Kdesktop
Klike, using a controller to browse your gnome/kde desktop
FOh, that one. Does it effect playing games though?
FI guess there's also this https://github.com/Supreeeme/extest but I might as well just adapt Bazzite's wrapper I guess
FWell, I guess I could also just change the flatpak .desktop application name - that was my main annoyance really, it's not a big deal
Kthat's what the wrapper applies
MSo much issues , games are taking too long to load
MScreen rotation
MLegion button not working
HLegion L+ X/A and legion Y are the only buttons that currently work in linux. Screen rotation is a non issue if you use nested desktop and even then you can just rotate it. It can be annoying though. I don't know anything about the slow load times. Are you running from internal or SD card?
Pwill the fix for this be in bazzite? I think it's the same issue I've had. https://github.com/ublue-os/bluefin/issues/663
GitHub
Issue Monitor is unresponsive after logging on. A hard reset (unplug power) brings me back to the desktop. Machine Minisform HM80 AMD Ryzen 7 4800U with inbuilt Radeon Graphics (Renoir) base ostree...
ZPoor Kyle, everyone wanting his help D;
MGames takes too long to load, during gameplay I was unable to lunch the Steam menu.
AYou need to configure legion_L + X to open the steam menu, by default it's mapped to the OSK
MHow do you configure it?
AUpdate the
/etc/handygccs/handygccs.conf file. Change button 4 to MODE, save and rebootMThe other button on top right also doesn't work.
M
AThe legion_L and legion_R buttons? Yeah, they currently don't work on Linux. A driver needs to be made for them.
MI clicked on Legion L and nothing happens
RThey don't work, since they don't generate events.
RIt's missing the handler in the kernel, from what I've read above.
RRNot yet recognized:
- start, select
- 4 rear paddle buttons (Y1, Y2, Y3, M3)
- gyroscope
RI lied.
RYeah, there is not a patch in kernel yet.
ALegion L does not work, only
Legion_L + X and Legion_L + AABy itself, it does not work
AUnless you enable steam patch, then they "should" work.
ABut I don't really use steam patch, it could break whenever steam updates
Mlegion- Left + x?
ZAnyone else experience slowness after enabling fleek?
JThanks
R@KyleGospo The Valve committer has opened a bug report on red hat tracker for the missing dwc3 module https://bugzilla.redhat.com/show_bug.cgi?id=2250955
RLet's see which is first at fixing this /s
VShould I try Jovian NixOS?
VI have some experience with Nix
VI am by no means very good though
VBut I think the installer is in KDE/GNOME, so I can use an OSK
VEhhh nevermind, doesn't look like what I'm after for a steam deck
KShould be fixed in unstable on our end
KBut if this is merged that's great since we won't need to drop secure boot support
KWill be in the next build
