updated my PR to 1.3.1 instead of 1.2.1 👍
updated my PR to 1.3.1 instead of 1.2.1 
Agonna push another minor hotfix now
Aits going to be on copr in 15min
Msounds good
Afixes the loki gyro axis and my oopsie where hhd would start by default on unsupported devices, has to be enabled now by the user
Ai dont want it to happen that its enabled on an unsupported device and starts grabbing the controller and crashing
Mmakes sense
Ayou should be able to replace handycon fully now
Mvery nice. I’ll add a note for the next iso refresh.
Mnew installs already get swapped successfully to hhd on the first system update in my own testing
Aoh crap, forgot to mention one thing; hhd can't map the optical mouse to the emulated dualsense
Aso if you wanted to use the trackpad/mouse in steam input, it won't work
Ashould add it to the readme
TThat should be fine, does it work in desktop mode?
Ait works fine as a regular mouse, no problems there. just can't use it in steam input for anything
Aomg @matt_schwartz wild plot twist, P3 reload works on the LGO when hooked up to an external monitor on gamescope-session
Aand it continues working when i disconnect the display
TSo it’s something with the internal display settings/driver in game scope?
Abut now if i close it and relaunch on internal screen, it crashes
A
wildAso i need to launch on external screen, disconnect, and then i can continue playing it
TThat’s good to know tho so I can actually play it on bazzite
TDoes it still work after sleep
Alet me check real quick
Ayep, worked fine
Athis is the weirdest bug i've ever seen, lol
TOkay Ty for giving me a work around lmao
TNow I can go back to bazzite
Ai find it hilarious that this even works
Anote that reportedly performance is better on windows for p3 reload
Aso you might want to stay on windows for p3reload
KHUH?
KMaybe it's time I do that patch to make sure it can't set an invalid refresh rate for the legion
Ai get the feeling it might be an issue with the game
https://github.com/ValveSoftware/Proton/issues/7472#issuecomment-1924139590
https://github.com/ValveSoftware/Proton/issues/7472#issuecomment-1924139590
Ait might have some bugs related to monitors
Ait'd also explain some of the reports on protonDB, where they're seeing immediate crashes
TDo you think it's the resolution that's causing the issue?
Mmy guess would be the ray tracing that’s still enabled by default on non-Deck devices
Msomething that breaks the pipeline
TJust did the display trick, changed resolution after disconnecting the screen and it crashed
Ahrm, i was able to readjust resolution after disconnecting the screen, and it worked.
TWhat res did you use
Afirst disabled reflections in graphics settings
Athen window 1080p vsync off
Abut 1080p was a bit laggy, so bumped down to 720p
Abut note that i'm running at 12w tdp
Aso the lagginess might've been due to the tdp
TI did have it off but I just loaded again on the monitor and it kept the res so now it's fine?
Aalso swapped governor to performance
Mdefinitely RTX. if you disable reflections you’ll notice it spike up in a couple game areas
