CrazyKristi
Published
Everything works except for the intro and any videos. Press esc or click anywhere to skip those. Gameplay proceeded in a stable fashion.
The game freezes sometimes, ie once per 2-3 hours.
Used VCRedist 2017 and then winecfg -> set to windows 10 on the prefix. It ran fine then.
Game runs fluid and fine. Loading a new game or savegame can take a bit due to caching and having to load scene files.
Game runs fine, outside of occasional crashes during combat. The worst part is the tinkering honestly.
Did a manual install of dx10 (june 2010 redist). Installed msxml3, msxml6, xact_x64, wininet, corefonts.
I went into sots2/bin/x86/sots2.exe.config. Edited contents to desired values (all values false except windowed and windowed fullscreen. Set resolution to 1920x1080). Copied all contents after editing. PROTON_PREFIX/users/steamuser/local settings/application data/kerberos productions/sots2_exeLots of semirandom characters/user.config. Pasted contents there. Then set the user.config file to be able to be executed and all perms to readonly.
Only windowed fullscreen worked for me.
During combat mostly.
Editing the config through the launcher is nonfunctional.
Optional: Go to winetricks, winecfg. Set all DX10 and DX11 related dll's to builtin, then native.
It took me quite some experimentation to find exactly what was causing issues, as I was getting both DX10 and xml related errors. So I took a bit of a bruteforce and whackjob approach, and started flipping values on whatever could be related.
My earlier report was on arch with vastly outdated deps and libraries. This is now on Fedora 34, so should be a bit more applicable to other people.
OPTIONAL EXTRA DEBUGGING OF ISSUES: PROTON_PREFIX/users/steamuser/local settings/application/SOTS2/log can contain some info, but I found it to be utterly useless. Alternatively: Load the sots2.exe or mars.exe (if you edited the config accordingly) into lutris, and set it's wine prefix to the proton prefix being used for SOTS2 (steamapps/compatdata/42990/pfx). Then enable debug output on lutris. That is what partially enabled me to tackle the issues.
This enables you to reach the main menu without it crashing on the splash screen.
Did a manual install of dx10 (june 2010 redist). Installed msxml3, msxml6, xact_x64, wininet, corefonts.
I went into sots2/bin/x86/sots2.exe.config. Edited contents to desired values (all values false except windowed and windowed fullscreen. Set resolution to 1920x1080). Copied all contents after editing. PROTON_PREFIX/users/steamuser/local settings/application data/kerberos productions/sots2_exeLots of semirandom characters/user.config. Pasted contents there. Then set the user.config file to be able to be executed and all perms to readonly.
Occasional crashes during combat.
Game config can not be adjusted using the launcher.
Optional: Go to winetricks, winecfg. Set all DX10 and DX11 related dll's to builtin, then native.
It took me quite some experimentation to find exactly what was causing issues, as I was getting both DX10 and xml related errors. So I took a bit of a bruteforce and whackjob approach, and started flipping values on whatever could be related.
My earlier report was on arch with vastly outdated deps and libraries. This is now on Fedora 34, so should be a bit more applicable to other people.
OPTIONAL EXTRA DEBUGGING OF ISSUES: PROTON_PREFIX/users/steamuser/local settings/application/SOTS2/log can contain some info, but I found it to be utterly useless. Alternatively: Load the sots2.exe or mars.exe (if you edited the config accordingly) into lutris, and set it's wine prefix to the proton prefix being used for SOTS2 (steamapps/compatdata/42990/pfx). Then enable debug output on lutris. That is what partially enabled me to tackle the issues.
