protonscr

Stars Reach Playtest

protonclosed appid 3361750Game compatibility - Unofficial
ValveSoftware/Proton#8487 · opened 2025-02-28 by ChrisClems · updated 2025-03-11 · 3 comments · github · game page · search this game
CChrisClems 2025-02-28 github

Compatibility Report

  • Name of the game with compatibility issues: Stars Reach Playtest
  • Steam AppID of the game: 3361750

System Information

I confirm:

  • [ X ] that I haven't found an existing compatibility report for this game.
  • [ X ] that I have checked whether there are updates for my system available.

steam-3361750.log

Symptoms

On Proton 9, game crashes to desktop as soon as the game world loads. There is what appears to be a Unity crash report dialog that pops up momentarily until the game closes. Proton <9 hangs at "Logging in..." and never loads the character select menu.

Reproduction

Happens predictably on Proton 9, Proton GE 9, and Proton Experimental. Happens on both the Dx and Vulcan renderers.

In the game Discord I managed to find a report from someone who is running it with no issues. They claim to have not forced any specific Proton version. They were running CachyOS with the current kernel. Open source AMD drivers. Running under Wayland and KDE Plasma.

Kkisak-valve maintainer 2025-02-28 github

Hello @ChrisClems, wine: Unhandled illegal instruction at address 00006FFFFB0962FC (thread 018c), starting debugger... hints that the game is trying to use a CPU feature that your Sandy Bridge generation does not have, but it's not immediately clear what specific feature that is.

CChrisClems 2025-02-28 github

Hello @ChrisClems, wine: Unhandled illegal instruction at address 00006FFFFB0962FC (thread 018c), starting debugger... hints that the game is trying to use a CPU feature that your Sandy Bridge generation does not have, but it's not immediately clear what specific feature that is.

Interesting. I don't think I ever would have thought of that. Can you recommend any ways in which I might be able to investigate further?

CChrisClems 2025-03-10 github

It looks like this was an unintended AVX2 dependency which has since been patched out. Game is running fine via Proton9+ currently.

Proton versions