Matyt-Mamut
Published
Looks nice enough for me on `low` graphical settings + `high` textures :).
Well, the default graphical settings were High, including high anti-aliasing, despite my 4K resolution, so even the menu was laggy at the 1st start. Since I changed the graphical settings to Low (on Medium, Discord's audio had been quite choppy >w<), I have not experienced any problems with playing and streaming on Discord at once. Later I even tweaked some settings (e.g., those texture- or water-related) to high and did not experience any drawbacks and I will continue to try tuning my settings further up.
An error pop-up appeared when choosing some of the Info overlays for the 1st time. But it was dismissable (Continue) and was only some graphical-related NullPointerException; it seems not to have impacted my game further.
(For clarification, the Proton version at the time was 8.0-4.)
When I first opened the options, the controller/keyboard mapping icons were shifted to the right and cut off by the canvas (a book page), but I guess it was more related to the game being in Early Access than it being run via Proton.
So far tried the online matchmaking once and it was successful.
(Played on keyboard; one-player couch)
While installing and running, a window called "Steam Client Service" appeared and told me that a Steam executable could not be found.
Both out-of-the-box and forced Proton Experimental.
Seems to be hardly enjoyable, but might be sufficiently playable for those patient and determined. Might be worth tinkering more with.
Occasional lag, like a ≥1-second screen freeze (in both single-player Prolog and a co-op play).
I have run it two times. The 1st run crashed on Prolog ending screen/menu (still got the progress achievement and stats, though). The 2nd run froze on one of my shots (maybe it was a killcam, going to start, causing this) in 2-player multiplayer (I joined a friend's game through steam).
