Works great save for bug in WS
Rarely the game just completely loses the ability to use Fn keys as a quick shortcut to run actions on an object, might be a game bug
Game locks up in White Stars if too many ally ships are bunched together such as during preparation when usually at least 15 ally ships sit at home JG. The game seems to lock up the entire system for a few moments before everything else returns to normal, and it seems to keep running but won't push any more frames, as I can interact with UI and hear them being invoked, but not see anything.
It just work, in every aspects, tested on like, every proton version (and GE ones) from Proton 4.x to the last, works everytime
Tried "PROTON_USE_WINED3D=1". On some versions it immediately crashes, other ones show the Unity Crash screen.
The music had some crackling sometimes, other sounds were fine.
Pinch zooming with touchscreen doesn't work.
turn based mmorpg with have ssp elements in a dynamic persistent universe
some dialogs on the screen smear the textures to the side of them.
Unknown(> 10 hours with Proton)Font looks a little small but doesn't affect playability
Unknown(> 10 hours with Proton)Unknown(an hour with Proton)The games seems to run perfectly. I also linked it with my existing Google Play game without any problem.
Unknown(an hour with Proton)Unknown(2+ hours with Proton)It just worked.
Unknown(2+ hours with Proton)
I have tried all three main tweaks (D3d11, Wine D3d11 and Esync), both separately and together, it still keeps crashing. It doesn't even crash properly and stays as "Running". One can't uninstall running games so I had to close and reopen the whole Steam first.
Unknown(< 1 hour with Proton)Worked fine out of the box. I didn't have anything left to do for now, but I'll update this if things go south.
Unknown(< 1 hour with Proton)
Workaround is simple, set your launch option like this: PROTON_USE_WINED3D=1 %command%
Appears to run flawlessly, exhibiting no issues related to platform compatibility (so far, only UI bugs that also exist on the mobile version). Forcing the use of Wine D3D was all that was necessary to get this game running at ~60 FPS even on Intel integrated graphics.
Under Proton 3.7-8 Beta, the game would not even get far enough along to generate its own crash log. A stack overflow in ~/steam-755800.log was the closest thing to an error message that I could get.
Unknown(> 10 hours with Proton)No tweaks needed and has the same functionality as reported by Windows users.
Unknown(> 10 hours with Proton)
