Sender | Message | Time |
---|---|---|
8 Feb 2025 | ||
terrorjack set a profile picture. | 02:24:18 | |
terrorjack removed their profile picture. | 02:24:54 | |
9 Feb 2025 | ||
AssertInequality joined the room. | 18:37:30 | |
AssertInequality | Hi Everyone I recently got my hands on a relatively recent (5600 series) AMD gpu and decided to include a gaming section in my system flake. Everything runs flawlessly except for a very weird issue Non-steam games in gamescope get no controller input at all. Steam games work flawlessly. I tried doing research, but it seems many people have this issue without a solution or even pointer as to what's causing this | 18:41:24 |
AssertInequality | Observations: Gamescope: no controller in non-steam games whether steam input is enabled or not. Steam big picture on X: no controller with steam input enabled. Controller detected and working when steam input is disabled. This behavior persists with gamescope regardless of running it on top of i3+picom or launching it from a new tty | 18:43:59 |
AssertInequality | Gamemode doesn't make a difference | 18:44:33 |
qubitnano joined the room. | 19:29:50 | |
proactivecritter | In reply to @assert-inequality:matrix.orgI remember i stumbled in using a controller with gamescope a year ago with honkai starrail in lutris, but it was easy and fast enough to solve, so i don't remember what i did. I just checked and there doesn't seem to be any special settings or envs for it. Shell history is empry of suspicious config edits too. The only thing i can think of is using lutris built-in gamemode switch vs custom cmdline with explicit gamemode wrap. So, the order at which gamemode and the rest of the wrappers apply. | 19:55:51 |
AssertInequality | Hmm, well I know that at least it's not gamemode because the behavior is the same. And the same workflow works flawlessly on the steamdeck (stock steamOS stable) including gyro, so it's most probably not Heroic either | 20:20:16 |
AssertInequality | It's between gamescope and steam-input, but I have no idea how to debug. Nothing of particular interest is popping in the gamescope logs, and steam logs are very hard to parse but a quick once-over doesn't immediately point to a culprit | 20:22:28 |
AssertInequality | I'm going to throw bazzite on a spare SSD to at least determine if it's a magic sauce on steamOS's part or if somehow something is going on with my config | 20:23:36 |
AssertInequality | In the mean time, I'll share the gaming section of the config here. I hope I'm doing something wrong somewhere because dual-booting can get boring pretty fast | 20:25:03 |
AssertInequality |
All the imports are irrelevant to the topic. | 20:32:46 |
@tired:fairydust.space left the room. | 22:52:43 | |
kuruczgy | I have quite a few games playable on X1E. (Which is slightly easier compared to AS because no need for muvm.) I basically just run the bwrap based x86 steam fhsenv using FEX. (No need for FEX's RootFS.) The only extra trick needed is symlinking the x86 mesa drivers inside the fhsenv. I cross-compile the steam fhsenv from aarch64 to x86 which is a bit troublesome and still requires at least one non-upstreamed workaround, but it is perfectly doable. (If you want to save a bit of trouble you can just set up an x86 remote builder and not do cross.) Here is my setup, might be useful to take a look if you are considering this route: https://codeberg.org/kuruczgy/aarch64-gaming | 23:56:51 |
proactivecritter | * I remember i stumbled in using a controller with gamescope a year ago with honkai starrail in lutris, but it was easy and fast enough to solve, so i don't remember what i did. I just checked and there doesn't seem to be any special settings or envs for it. Shell history is empry of suspicious config edits too. The only thing i can think of is using lutris built-in | 22:59:27 |
10 Feb 2025 | ||
kuruczgy | Ah yeah one more thing is that you probably have to enable your drivers for the x86 mesa build, since obviously by default nixpkgs does not enable asahi or freedreno drivers on x86. (Alternative would be to set up thunking with FEX but I think that's even more complicated.) | 00:08:54 |
9 Feb 2025 | ||
proactivecritter | In reply to @assert-inequality:matrix.orgSorry, i meant "gamescope" everywhere i wrote "gamemode". I am not sure what gamemode even is, and haven't used it | 23:01:22 |
proactivecritter | And as a way of debugging i suggest trying different orders of gamescope/heroic/wine/mangohud wrappers. And do it imperative style:heroic gamescope mangohud wine game.exe or mangohud gamescope heroic wine game.exe something like that | 23:09:44 |
proactivecritter | I also run everything inside systemd user-scope, i think, maybe that added some interference too. | 23:11:40 |
10 Feb 2025 | ||
spacekitteh joined the room. | 03:54:24 | |
parrvx joined the room. | 18:24:34 | |
srestegosaurio (on tchncs.de) | Uhhh, why is Balatro using 90% of my CPU? | 22:49:36 |
SigmaSquadron | observatory + perkeo will do that to you. | 22:50:22 |
srestegosaurio (on tchncs.de) | If I run it with the dGPU I get 15fps. | 23:03:04 |
srestegosaurio (on tchncs.de) | With the iGPU I get resonable performance in exchange of all my system resuorces. | 23:03:25 |
srestegosaurio (on tchncs.de) | Oh, and I have to launch it with love Balatro.exe; echo %command% . | 23:04:01 |
11 Feb 2025 | ||
Atemu | Which GPU is your display hooked up to? | 10:06:24 |
srestegosaurio (on tchncs.de) | In reply to @atemu12:matrix.orgMy Wayland compositor is running on the iGPU. | 12:15:50 |
Atemu | That means framebuffer copies | 12:16:21 |