| 27 Jan 2024 |
 x10an14 | I reset the launch option to just %command%, and yes the launcher launched now. Will see and report if game launches. | 13:50:37 |
| x10an14 | In reply to @x10an14:matrix.org
sent an image. Game crashed with this same error as here | 13:51:01 |
| x10an14 | In reply to @x10an14:matrix.org
Okay, just executed rm -rf ~/Games/SteamLibrary/steamapps/compatdata/435150 w/steam's proton 8.0.5 and this launch option: eval $(echo "%command%" | sed "s#bin/SupportTool.exe#DefEd/bin/EoCApp.exe#") Game crashes identically (but skips launcher) with this aforementioned launch option | 13:52:51 |
 @atemu12:matrix.org | Next step is to set PROTON_LOG=1 and then probably open a bug report because you probably won't fix this. | 13:57:31 |
| x10an14 | In reply to @atemu12:matrix.org
Next step is to set PROTON_LOG=1 and then probably open a bug report because you probably won't fix this. Before starting steam or in front of %command% (or any of its equivalents)? | 13:58:40 |
| @atemu12:matrix.org | In front of %command%. | 14:05:21 |
| x10an14 | In reply to @atemu12:matrix.org
In front of %command%. PROTON_LOG=1 %command% gave no more output than previously. | 14:10:42 |
| @atemu12:matrix.org | You will now have a proton log with the app id delivered your home | 14:11:53 |
| @atemu12:matrix.org | * You will now have a proton log with the app id delivered to your home | 14:12:22 |
| x10an14 | In reply to @atemu12:matrix.org
You will now have a proton log with the app id delivered to your home Ahhh, gotcha. Thanks. ~/steam-<steam app id>.log. This is for nixpkgs/issues, right? | 14:13:07 |
| @atemu12:matrix.org | No, for Proton issues | 14:15:14 |
| @atemu12:matrix.org | This does not look like a Nixpkgs issue. | 14:15:25 |
| x10an14 | So you're telling me that this should go "straight" to Valve's proton Github issues repo, bypassing any issue creation on nixos/nixpkgs? | 14:19:30 |
| @atemu12:matrix.org | I see nothing indicating a Nixpkgs-specific issue | 14:25:34 |
 K900 | OK amazing | 14:48:16 |
| K900 | Fixed the Yuzu crash | 14:48:18 |
| K900 | That was caused by build system fuckery | 14:48:27 |
| K900 | And immediately hit another crash | 14:48:33 |
| K900 | This time caused by just basic C++ bullshittery | 14:48:44 |
| K900 | So now I've fixed THAT | 14:48:49 |
| K900 | And I think it's good | 14:48:52 |
| x10an14 | Anyone struggled with "Failed to collect displays" when it comes to NixOS and BG3? | 15:08:00 |
| K900 | I feel like you're definitely doing something weird with the drivers at this point | 15:08:17 |
| K900 | Because you have games crashing that work just fine for most people | 15:08:27 |
| K900 | And drivers are literally the only ambient thing Proton generally uses | 15:08:49 |
| x10an14 | That could be I suppose, but no idea how to verify/check that. | 15:08:56 |
|  @zumorica:matrix.org joined the room. | 15:09:43 |
| K900 | Do you have anything weird in your config? | 15:09:59 |
| K900 | Especially driver related | 15:10:05 |
| K900 | mesa-git? Multiple versions of nixpkgs? | 15:10:12 |
