| 4 Feb 2024 |
|  dusk changed their profile picture. | 13:10:14 |
 K900 | Updated Yuzu with the frame pacing fix: https://github.com/NixOS/nixpkgs/pull/286100 | 19:38:28 |
| K900 | Can someone else please test it so I can merge | 19:38:48 |
|  @ktn:the-apothecary.club left the room. | 21:48:18 |
| 5 Feb 2024 |
|  98765abc joined the room. | 04:45:11 |
| 98765abc joined the room. | 04:48:28 |
 ersei | I wonder why wine games refuse to run on my igpu and instead require my dgpu | 05:37:31 |
 @atemu12:matrix.org | Well, which GPU is the display connected to? | 05:40:10 |
| @atemu12:matrix.org | If it's the dGPU, you'd have to copy the frame buffer from iGPU to dGPU | 05:40:28 |
| @atemu12:matrix.org | There are ways to do this of course but isn't a trivial matter from a technical side | 05:40:57 |
| ersei | it's a laptop, so the igpu is connected to the display | 05:45:58 |
| ersei | native games work fine on the igpu, just stuff that runs through proton do not | 05:46:27 |
| @atemu12:matrix.org | Native OGL games I assume? | 05:46:56 |
| @atemu12:matrix.org | Or native Vulkan games aswell? | 05:47:10 |
| ersei | both work natively | 05:47:34 |
| ersei | * both work fine natively on the igpu | 05:48:28 |
| @atemu12:matrix.org | Huh. Laptop's aren't my domain but if native works but WINE doesn't, that smells like a WINE bug to me. There shouldn't be anything different about WINE using VK and a native app using VK. | 05:49:17 |
| @atemu12:matrix.org | Anything interesting in the logs? | 05:49:30 |
| ersei | nope. I should test out whether explicitly setting VK_ICD_FILENAMES will do anything | 05:50:06 |
| ersei | yep seems like explicitly setting that to the intel file works | 05:53:56 |
| @atemu12:matrix.org | Perhaps WINE might be doing some device selection thing where they try to not use iGPUs if a dGPU is present | 05:54:54 |
| @atemu12:matrix.org | I've heard of some cases where the opposite was the case | 05:55:13 |
| @atemu12:matrix.org | So that may be a workaround for that | 05:55:24 |
| ersei | seems like vkcube doesn't want to run either without that variable set too | 05:57:38 |
| ersei | actually it launches, but with a 20 second delay | 05:58:22 |
| ersei | seems like vkcube is blocking on opening a bunch of files in /sys/bus/pci/devices/*/config repeatedly | 06:01:52 |
| ersei | that doesn't explain the failure of proton, however, since the process seems to just stop | 06:03:36 |
| ersei | hm, seems like I was mistaken and the process does not stop (after disabling the steam overlay) | 06:07:04 |
| ersei | it takes a solid minute to launch (as opposed to near instant with the VK_ICD_FILENAMES set or with the nvidia gpu on) | 06:07:29 |
| ersei | seems like this is either a hardware or a nixos issue | 06:07:41 |
