GPU: Radeon 680M (integrated on Ryzen 7 PRO 6850U) - AMD Radeon Graphics (radeonsi, rembrandt, ACO, DRM 3.64, 6.19.11-300.fc44.x86_64)
Desktop: KDE Plasma Desktop 6.6.3, kwin 6.6.3, sddm 0.21
Issue:
With shader pre-caching in Steam enabled, the game (The Sims 2 Legacy Collection) takes upwards of a whole minute to even start and pretty much 9 out of 10 times immediately crashes; interestingly, there doesn't seem to be any issue with the game once it manages to actually start once. Game starts quickly and loads correctly pretty much always with pre-caching disabled.
Nothing other than disabling the shader pre-caching fixes the issue; I've tried dropping gamescope (unrelated to the current issue but the game ran on its own also has this problem of constantly grabbing focus at a frequency at least more than every second, which has been for a few months but the game started off okay; not fixed by going back to older version of Proton either), dropping the Wine DLL overrides for the ASI loader, and just a variety of random Proton/DXVK configurations with the exception of switching to WineD3D.
Judging by the logging, the point of failure seems to be in Mesa's Vulkan drivers; could it be that Steam is getting invalid compiled shaders for the configuration somehow? There are several reports on ProtonDB suggesting that WineD3D should be used instead of DXVK, and I also wonder if that would be related to this.
Not quite sure if this should go to Steam's issues or Proton so I'm creating it here as it seems to be more relevant.
System Information:
Issue:
With shader pre-caching in Steam enabled, the game (The Sims 2 Legacy Collection) takes upwards of a whole minute to even start and pretty much 9 out of 10 times immediately crashes; interestingly, there doesn't seem to be any issue with the game once it manages to actually start once. Game starts quickly and loads correctly pretty much always with pre-caching disabled.
Nothing other than disabling the shader pre-caching fixes the issue; I've tried dropping gamescope (unrelated to the current issue but the game ran on its own also has this problem of constantly grabbing focus at a frequency at least more than every second, which has been for a few months but the game started off okay; not fixed by going back to older version of Proton either), dropping the Wine DLL overrides for the ASI loader, and just a variety of random Proton/DXVK configurations with the exception of switching to WineD3D.
Judging by the logging, the point of failure seems to be in Mesa's Vulkan drivers; could it be that Steam is getting invalid compiled shaders for the configuration somehow? There are several reports on ProtonDB suggesting that WineD3D should be used instead of DXVK, and I also wonder if that would be related to this.
Relevant bit of log: