Hello @Koli0842, System WINEDEBUG: -all makes the Proton log effectively unusable for troubleshooting purposes.
Thanks for pointing out! I recently moved to Linux and fumble occasionally, turns out Lutris has a dropdown that sets log level per game. I wanted to try full/trace levels, but that complains of permission denied without telling me to what exactly, so that's for another day. I am still at somewhat of a loss why can't I start from steam too.
I've updated my original post with logs from proton 10 and 7 regardless
WINEDEBUGx1 2025-11
Compatibility Report
System Information
I confirm:
Probably not the most usable logs, because they look mostly empty for me, when running from Lutris (Proton 10 runtime). The game doesn't start, added as a non-steam game when running from Steam with Proton 10 for some reason, logs don't really give a clue, besides complaining for a missing appid and gameoverlayrenderer.so. Proton 7 doesn't seem to log either, so I don't have a frame of reference for when it works right. I have attached it regardless
steam-starshine-proton-7.log
steam-starshine-proton-10.log
Symptoms
So, this is going to be an exotic one. A tiny, ancient, niche horse game. Crashing upon loading into a specific level 6 of 7 or 8. But only on some hardware! I played through it with wine-staging and experienced a crash when reaching level 6, after the loading screen. Tried proton, it behaved the same (after I figured out I'd need lib32-nvidia-utils). Tried llvmpipe vulkan driver, Wine3D instead DXVK, fresh prefixes to no avail. Then I stumbled upon Proton 7 which seems to be working just fine. What's interesting, on a machine of a friend of mine, HP Laptop from around 2018 with both an Intel and AMD gpu, upstream latest upstream wine in wow64 works just fine. I have no clue where the regression might be coming from. It's a DX9 title.
Reproduction
SaveSlot4.sac.zip
Logs complain about failing to read some memory address.
backtrace.txt