The Sims 2 Legacy Collection
Game launches perfectly fine for me, everything seems to run okay.
However, no matter what I try, the game is always using my integrated GPU instead of the dedicated one (confirmed via nvidia-smi) - so performance is abysmal at anything higher than 800p resolution. I don't have this issue with other games. I'm not sure if this is a proton issue or a game issue, but I imagine others will run across the same problem.
I'm on a Lenovo Legion 5 Pro 16ITH6 (11th gen i5, 3050Ti mobile) on Ubuntu 24.04 using proprietary 550 drivers. Default DE settings (i.e. using Wayland). Steam installed via snap. Have tried Proton 9.0.4, GE9-23, and Experimental.
I've tried:
- prime-run: doesn't do anything
DRI_PRIME: doesn't do anythingDXVK_FILTER_DEVICE_NAMElaunches but then errors saying there is no Direct X 9 compatible driverPROTON_USE_WINED3Dshows a different error about a bad callMESA_VK_DEVICE_SELECTalso does nothing.- Setting the Nvidia prime profile to use the GPU for everything (and then rebooted). This makes my whole system performance horrible and then the game just immediately closes without any errors.
EDIT: Hmm, I'm still not sure about this particular issue, but after accidentally getting Cyberpunk 2077 to also run at a smooth 60 frames on this machine, I thought I'd tinker with the graphics settings on this even more. Turning antialiasing all the way down improves performance drastically.
by "other games" do you mean Steam games too? most likely Nvidia Vulkan layer is not registered and detected (from within snap).
Snap steam has a bad reputation, try native or flatpak steam with flatpak nvidia drivers and flatpak Proton-GE
Speaking of GE Proton, I tried the latest version of that and the unspecified error when attempting to record a video still occurs.
by "other games" do you mean Steam games too? most likely Nvidia Vulkan layer is not registered and detected (from within snap). Snap steam has a bad reputation, try native or flatpak steam with flatpak nvidia drivers and flatpak Proton-GE
Yes, I haven't had this issue with other games on Steam.
Migrating off snap is on my todo list for sure, but I'm not sure why using the snap would affect just one game here.
The Sims 2 Legacy Collection: enabling shader pre-caching in Steam leads to long starting time, random crashes on start
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9644.
@aleatoricLilac posted on 2026-04-05T00:32:55:
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:
- AppID: 3314070
- Proton: 1774341903 experimental-10.0-20260324 (switching to Proton 10 or 9 had no effect on the issue)
- System: Fedora 44, kernel 6.19.11-300.fc44.x86_64, Mesa 26.0.3
- 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.
Relevant bit of log:
info: Found device: AMD Radeon Graphics (RADV REMBRANDT) (radv 26.0.3)
info: Found device: llvmpipe (LLVM 22.1.0, 256 bits) (llvmpipe 26.0.3)
info: Skipping: Software driver
80794.524:0130:0134:trace:seh:handle_syscall_fault code=c0000005 flags=0 addr=0xdf6085a0 ip=df6085a0
80794.524:0130:0134:trace:seh:handle_syscall_fault info[0]=00000000
80794.524:0130:0134:trace:seh:handle_syscall_fault info[1]=deaab02c
80794.524:0130:0134:trace:seh:handle_syscall_fault eax=000d3344 ebx=e04523a0 ecx=000d4000 edx=0001199b esi=deaab028 edi=f2df6148
80794.524:0130:0134:trace:seh:handle_syscall_fault ebp=e04523a0 esp=0143f8e0 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00210216
80794.524:0130:0134:warn:seh:handle_syscall_fault backtrace: --- Exception 0xc0000005 at 0xdf6085a0: /run/host/usr/lib/dri-freeworld/libvulkan_radeon.so + 0x32f5a0.
80794.524:0130:0134:trace:seh:handle_syscall_fault returning to user mode ip=77b3ff53 ret=c0000005
80794.524:0130:0134:err:msvcrt:_wassert (L"!status",L"../src-wine/dlls/winevulkan/loader.c",392)
Hello @aleatoricLilac, it might be worthwhile to also mention your findings to your video driver vendor if it hasn't been already.
Hello @aleatoricLilac, it might be worthwhile to also mention your findings to your video driver vendor if it hasn't been already.
Oh didn't know that it's supposed to go into this thread ><
OK, will open an issue with drm/amd (or Mesa?) later.
Hello, can someone look into the outdoor shadow issue in Sims 2 Legacy Collection in Proton-Experimental and Proton 11? Something broke the outdoor shadows in one of the newer proton 11 updates. I had to revert back to Proton 10.0 to get shadows back.
Hello @thedreadpirates, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
Do you happen to have an exact Proton 11 version or date you know for sure behaved better?
Hi @kisak-valve, narrowed it down to a DXVK issue. Already filed a bug report here https://github.com/doitsujin/dxvk/issues/5666
Proton versions
proton 10.0x1 2026-05proton experimentalx1 2026-05proton 9.0x1 2025-02
Launch options
PROTON_LOG=1x1 2026-05DXVK_FILTER_DEVICE_NAMEx1 2025-02MESA_VK_DEVICE_SELECTx1 2025-02PROTON_USE_WINED3Dx1 2025-02
Upstream links
- doitsujin/dxvk/issues/5666x1 2026-05
- ValveSoftware/Proton/issues/9644x1 2026-04
Error codes
0xc0000005x1 2026-04
Compatibility Report
System Information
I confirm:
The game appears to work fine on Steam Deck, but there is an issue regarding in-game video captures, and I haven’t found any issues from anyone else with this. Simply press V or select the cam recorder icon on the GUI and you should get an “unspecified error” popup. Sometimes you may get an error with Smooth Edges, but changing this value doesn’t seem to fix the issue.
steam-3314070.log