https://bugs.winehq.org/show_bug.cgi?id=45984
Bug ID: 45984 Summary: Skyrim Special Edition does not get past loading screen on high core count or high memory systems Product: Wine Version: 3.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: tom@r.je Distribution: ---
Skyrim SE gets stuck at the loading screen on certain hardware configurations. It doesn't freeze as keeps displaying different loading screen tips but does so forever.
I posted on the Steam forums about this: https://steamcommunity.com/app/221410/discussions/8/1734336452599497070/
With a blank wineprefix (no savegames, no mods, just a fresh install from steam) click "New game". It sits at the loading screen forever.
Almost everyone affected has:
AMD Threadripper 1950x
= 32gb RAM
### Software information
Skyrim Special Edition (Steam) (With or without DXVK)
### System information - GPU: nvidia 980ti - Driver: 410 (396.54 also affected) - Wine version: 3.18
There are several systems listed in the steam thread:
///// Arch Linux AMD Threadripper 1950x 32gb RAM nvidia 980ti with 396.54 driver ///// Ubuntu 18.04 AMD Threadripper 1950x 64gb RAM Nvidia Titan XP /// Arch Linux AMD Threadripper 1950x 32gb RAM AMD Vega 64 ////
Both AMD and nVidia GPUs are affected so it's unlikely to be a driver issue. The common elements are:
32gb or more of RAM AMD Threadripper 1950x
### What I've tried
Knowing that it only affects high CPU core systems or high RAM systems I have tried the following:
- taskset -c 0-7 wine steam.exe I wasn't sure whether this would limit just steam.exe, when steam.exe spawns SkyrimSE.exe does this have all 32 cores enabled?
- Disabling SMT in the bios. This effectively disables half the cores so there are only 16 available. This would be similar to someone playing on a Ryzen 7 (8 cores + smt) and I haven't seen any reports with 16 thread CPUs
- It seems like it might be a memory issue. I've tried enabling/disabling NUMA in the bios to no effect
- With NUMA enabled I've tried using `numactl -m 0 -t wine Steam.exe` to force WINE to only use one bank of memory (effectively limiting it to 16gb in the process)
- Running off a SSD rather than NVME driver (It could be a scheduler issue??)
None of this made any difference. How else can I debug this?
Looking around, posts regarding similar issues on windows suggests it's a memory problem. Perhaps it's something to do with having 32gb RAM in the system?
Please let me know if you need any kind of trace/log. WINEDEBUG=all makes steam take so long to start it eventually crashes, so I couldn't provide that, I can try with requested debug options though.