motion axis on handheld daemon plug-in just says default with an option to switch to override, check
motion axis on handheld daemon plug-in just says default with an option to switch to override, checking hhd.dev now
Dbazzite
Tyeah same thing
C
Apress override
Tokay now it says manufacturer: gpd
product: g1618-04
product: g1618-04
Acapital G right?
Tyes
Ahttps://github.com/hhd-dev/hhd#-finding-the-correct-axis-for-your-device follow this and when youre done tell me the axis
Dim curious to learn more about this, kinda always assumed launchers like lutris and heroic were okay: Unable to Run Scripts
how exactly do they break best practices? isnt it the case that they make separate prefixes per game?
how exactly do they break best practices? isnt it the case that they make separate prefixes per game?
Dor am i missing something
Di guess for heroic games launcher, i dont like that it offers to use proton/proton-ge OUTSIDE of steam… pretty sure Glorious Eggroll is tired of telling people this
FThis is going to be a non-issue once ULWGL becomes fully utilized by every store, including Heroic Games Launcher
Dlets hope it gets widely adopted
Kdefinitely will, lutris, bottles, heroic, and others are all collaborating on it
Kcan't wait
FGreatest thing for me is that non-launcher versions will get the benefit too
Malso finally introduces a better system for games that are not on any of the major typical storefronts
Kreal shame the itch.io flatpak is so bad
Kwas real potential there
FAlso wine works on better Direct Music support for old games
I play old PES & Winning Eleven which either have no sound, or have huge audio latency when installing proprietary Direct Music libs
I play old PES & Winning Eleven which either have no sound, or have huge audio latency when installing proprietary Direct Music libs
C@Kyle Gospo Is the version number in rpm-ostree status output the Bazzite version? I have three deployments of 39.20240116.0 (bazzite-gnome-nvidia:testing) from 01/26, 02/03, and 02/05, where the 01/26 image is dramatically more stable in a few ways, and I'm wondering if anything notable changed after 01/26
Twhile I can't tell you the specific differences, you can see the
Diff line indicate just the number of package differences between 02-05 and 02-03. sometimes things don't play nice with other things
©I had to do a search to find what
https://github.com/Open-Wine-Components/ULWGL-launcher
ULWGL was, so for others also:https://github.com/Open-Wine-Components/ULWGL-launcher
GitHub
Contribute to Open-Wine-Components/ULWGL-launcher development by creating an account on GitHub.
Kquite a lot has changed since 01/26, mostly versions of things
Kand not new features
Kwhat sort of instability are you having?
CWayland session crashing on/after suspend, games freezing/crashing semi-randomly and especially if the window loses focus
Tit will be adopted by Lutris and Heroic
TWayland crashing could just be wayland being wayland. plus I have always found that suspend in Linux is always a risk
CWarframe in particular would crash within seconds to minutes
CYeah, the 01/26 -> 02/03 jump was because the 01/26 image very uniquely did not crash for about a week of nightly or more often suspend/wake cycles, unlike images from both earlier and later
Ti feel your pain
TI straight up jumped to GNOME for a few months because of sleep issues. for a while on KDE, waking up showed only one color across the screen until I logged in for 30 seconds, but I had to do so blindly
©In relation to sleep/resume:
Isn't this service supposed to be running?
Isn't this service supposed to be running?
©Will change to my Kubuntu system real quick to check...
©Yup just checked and it IS running by default in Kubuntu...
©So there might be a problem with the nVidia driver install in Bazzite in this respect...
KAutomatic leep/Resume just doesn't work on my desktop. Displays shut off, and then come back on, over the course of about 10 mins each time. I haven't really worried about it though. If I do it manually it works, but it's 50/50 if my USB peripherals (Logitech kbd/mouse via unifying reciever dongle) work again after waking up
©That could be related to the USB device not being reinitialized properly after a resume. I mean your dongle not the USB "port" 
KProbably, I really haven't done much trouble shooting because whenever it happens I have to do a forced reboot, so I just quit using sleep (and it's a desktop so I'm not worried about battery life or anything)
©Does the same happen when you hybernate?
Which is supposed to store the memory in current state to disk
Which is supposed to store the memory in current state to disk
KHibernation isn't supported in fedora atomic
©ahh ok
Knormal sleep only
KSpace Bar
©Kyle, pls check what i said 
wrt to that service...
wrt to that service...©Cause i also noticed sleep/resume problems in Bazzite-nVidia
Knvidia-smi | fpasteKnvidia-smi - q | fpaste