| 29 May 2025 |
 K900 | Or just don't run Gamescope because all the HDR bits should be working out of the box now | 15:10:22 |
 Nila The Dragon | The reason I'd like to use it is that on Gnome my mouse is not being properly locked to the game window. So if I do fast movements towards my second monitor and click, the mouse will actually escape the game. | 15:12:41 |
| Nila The Dragon | Otherwise I'd be more than pleased to not use another in-between layer. But the only solution I found to the mouse capturing issue is to use gamescope with the --force-grab... option | 15:13:19 |
| K900 | Does the game just not grab the cursor? | 15:15:38 |
| K900 | Or is this a Wine issue of some sort? | 15:15:45 |
| Nila The Dragon | So the game does "grab" it. It stays locked to the game during motion and I can spin around infinitely. The problem occurs specifically when I do a fast, longer motion towards the second screen, the cursor then (invisibly) actually moves over whatever windows I have there and as soon as I click (while still moving, it does not happen when i stop moving and then click) the mouse will actually activate whatever window it was over. Really really weird bug. | 15:18:38 |
| K900 | Maybe try latest Proton with wine-wayland? | 15:31:19 |
| Nila The Dragon | I assume I need Proton-GE for that? | 15:56:34 |
| K900 | No | 16:07:51 |
| K900 | Proton 10 should have it | 16:07:56 |
 Marie | I'm pretty sure vanilla Proton still has it disabled | 16:46:48 |
 matejc | @Nila The Dragon I "had" a similar issues with certain games, where mouse just escapes the game at some ocasions... But I have found a workaround: I have both screens with a gap in between (left monitor (1920x1080): pos 0,0 and the gaming monitor on the right with pos: 2000,0), that way the mouse just does not pass to the other monitor (at least on Niri... I have zero clue how this works on Gnome) - I have a keybinding for passing the cursor/focus around. The reason that I written had in quotes is that I havent tried without this workaround for quite some time. | 17:33:30 |
| matejc | I am running games without any gamescope or any other layer in between | 17:35:02 |
| matejc | * I am running games without gamescope or any other layer in between | 17:35:12 |
| Nila The Dragon | In reply to @matejc:matrix.matejc.com
@Nila The Dragon I "had" a similar issues with certain games, where mouse just escapes the game at some ocasions... But I have found a workaround: I have both screens with a gap in between (left monitor (1920x1080): pos 0,0 and the gaming monitor on the right with pos: 2000,0), that way the mouse just does not pass to the other monitor (at least on Niri... I have zero clue how this works on Gnome) - I have a keybinding for passing the cursor/focus around. The reason that I written had in quotes is that I havent tried without this workaround for quite some time. is that possible with wayland? I searched for a similar idea but only got xorg results... | 19:33:06 |
| matejc | @Nila The Dragon yeah, just checked, Niri itself (is an wayland only window manager) has the option to set position of the output in its config, also, maybe using kanshi could help (kanshi is declarative output configuration, its packaged in nix home manager). | 19:41:48 |
| matejc | I am sure Gnome has some option to offset one monitor... or maybe one of its extensions could do it | 19:44:05 |
| matejc | But then again... maybe just running games with wine-wayland could work | 19:45:10 |
| matejc | I have no clue on how to do it with official Proton 10, but with Proton GE 10, you can just set PROTONENABLEWAYLAND=1 before launching a game | 19:46:24 |
| matejc | I have no clue on how to do it with official Proton 10, but with Proton GE 10, you can just set PROTON_ENABLE_WAYLAND=1 before launching a game | 19:46:38 |
| matejc | @Nila The Dragon yeah, just checked, Niri itself (is an wayland only window manager) has the option to set position of the output in its config, also, maybe using kanshi could help (kanshi is declarative output configuration, it has a module in nix home manager). | 19:48:41 |
| matejc | * But then again... maybe just running games with wine-wayland could work, like previously stated | 19:49:38 |
| Nila The Dragon | In reply to @matejc:matrix.matejc.com
I have no clue on how to do it with official Proton 10, but with Proton GE 10, you can just set PROTONENABLEWAYLAND=1 before launching a game I tried wayland and it seems to work. But I could not use GE as the game would open on the wrong monitor lol. But Proton-EM seems to have a fix where I can specify which monitor I want to use and with that it works. | 19:59:33 |
| Nila The Dragon | Well thank you everyone for offering some fixes! :) Time to battle-test proton wayland :P | 20:06:19 |
| 30 May 2025 |
|  George joined the room. | 12:36:53 |
|  Martin Lindbüchl joined the room. | 18:12:09 |
|  DerivationDingus set a profile picture. | 19:55:26 |
| 31 May 2025 |
 codebam | I enabled this https://jovian-experiments.github.io/Jovian-NixOS/options.html#jovian.devices.steamdeck.enableSoundSupport
sound isn't working after enabling it, so I booted into plasma and enabled the sound card that was disabled in sound settings, but still no sound from the speakers | 19:31:40 |
| K900 | Are you on a Steam Deck? If not, you should not set that option | 19:36:08 |
| codebam | I'll paste my config right after it boots. it takes forever to boot as well. like 2 mins+. is that normal? it gets past the nixos part quickly and then takes like 2-3 mins to start the steamos ui | 19:38:19 |
