| 28 May 2025 |
 @normalcea:matrix.org | At least when I tested Hitman: WOA on my 1650 card. | 21:33:15 |
| @normalcea:matrix.org | * At least when I tested Hitman: WOA on my 1650 super card. | 21:35:18 |
 K900 | 1650 Super is probably the worst case for NVK | 21:37:18 |
| K900 | It's the lowest end thing they support | 21:37:23 |
 olivia | yeah, at least last time I was looking nvk is faster on some cpu-bound tasks, but generally slower on gpu-bound | 21:49:25 |
| olivia | (and much slower on ~everything pre-turing because no reclocking) | 21:49:41 |
| K900 | I think it's also faster on newer hardware because more of it is reverse engineered by now? | 21:51:49 |
| olivia | hmm, possible I don't know specifics. Everything newer than turing is all very similar in the shader ISA at least | 22:27:47 |
| @normalcea:matrix.org | In reply to @olivia:computer.surgery
yeah, at least last time I was looking nvk is faster on some cpu-bound tasks, but generally slower on gpu-bound This tracks with my testing | 22:28:34 |
| 29 May 2025 |
|  Nila The Dragon joined the room. | 02:43:23 |
 aidalgol | Heroic Games Launcher update ready to merge: https://github.com/NixOS/nixpkgs/pull/410216 | 06:02:48 |
| Nila The Dragon changed their profile picture. | 12:13:45 |
| Nila The Dragon | Anyone have the issue with running gamescope from within steam on gnome? Works fine if I start steam through gamescope but same game will fail to launch if I put gamescope in its launch params... | 14:32:07 |
| K900 | What's in the logs? | 14:41:13 |
| Nila The Dragon | In reply to @k900:0upti.me
What's in the logs? With the current configuration (programs.gamescope.enable = true) and launch options (gamescope --backend sdl -h 720 -H 1080 -f %command%) the relevant game launch logs are https://pastebin.com/wWLGAmtS | 15:01:24 |
| K900 | That just looks like the game itself is crashing | 15:07:27 |
| K900 | What nixos version are you on? | 15:07:27 |
| Nila The Dragon | NixOS 25.11 (Xantusia) x86_64 (Unstable) | 15:08:00 |
| Nila The Dragon | The game will launch fine without gamescope + it will launch if I launch the entire steam client through gamescope as well | 15:08:15 |
| K900 | Try removing --backend sdl | 15:08:19 |
| K900 | Actually | 15:08:21 |
| Nila The Dragon | That will not work on GNOME currently due to https://github.com/ValveSoftware/gamescope/issues/1825 | 15:08:38 |
| K900 | Honestly no idea then, you'll want to attach a debugger to the game or something | 15:10:07 |
| 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 |
