Owlbear
Published
So, this won't directly from Steam using either any version of Proton (including GE) or Steam Linux Runtime 3.0 (Sniper). Vanilla Wine didn't work either.
However, if you install the native Linux version (was selected by default on our Pop!_OS install), browse local files, open a terminal in there and ./coinfactory it should work just fine. Alt + Enter fullscreens.
The long wait for launch is currently the most severe issue I've encountered, but once up and running, the game played nicely.
Requires a wait of 6 minutes to load game from splash screen. This is not limited to first launch.
The game complained that I was using too much VRAM, but this was because it thought I had 6GB rather than the 8GB my Vega 64 actually has. No problems resulted.
Alt-tabbing out and back can result in a black screen
On one attempt it froze while connecting to Bethesda.net (I have rural internet backed up by 4G, so I'm going to assume networking issues here)
The game only works stably on Proton 5.x - I currently have it running on 5.0-10.
It also requires the following launch options to prevent crashes and audio crackling:
PULSE_LATENCY_MSEC=60 PROTON_NO_ESYNC=1 %command%
With this in place, the experience is flawless.
Proton 6 and Experimental (as of 5 Jul 21) crash at main menu load.
Works perfectly out of the box on Steam Deck. I was puzzled to find that I had no sound when I installed it on my Pop!_OS 22.04 desktop.
In my specific case, this was because I'd forced all OpenAL audio through PulseAudio to fix a problem with a different game (Minecraft). This fix clashed with Proton's audio routing.
Anyway, I'm almost certainly a minority of one here, but just in case I'm not, if you experience no sound, any you've already tried swapping out the included version of OpenAL, double-check your ~/.profile file to make sure it doesn't include anything like this:
export ALSOFT_DRIVERS=pulse
If there is something along those lines in there, comment it out, reboot, and try relaunching Moonring.
Works correctly on Proton 8.0-4
I was experiencing identical issues to the previous report with Proton 7.x, but the game now correctly recognises that it's connected to steam and allows play.
Played past the first couple of cutscenes and everything works fine so far. Minor tearing was resolved by enabling vsync.
The Good Life and its demo have some unusual cutscene loading behaviour that not only causes it to fail with a black screen when you start a new game on stock versions of Proton (due to lack of relevant video codecs) but also on the normal build of Proton-6.19-GE-2 (due to http-based cutscene loading).
However the fix created by popsUlfr at https://github.com/ValveSoftware/Proton/issues/5195 works. Copying their customised mfplat.dll over ~/.steam/root/compatibilitytools.d/Proton-6.19-GE-2/files/lib64/wine/x86_64-windows/mfplat.dll resulted in a working game for me.
I've played past the first couple of cutscenes and everything works fine so far.
Works perfectly, online multiplayer with three Linux users was great!
Works perfectly at default Proton setup on both desktop and Steam Deck. Note that Blueprints and save games are not saved to the Steam Cloud or otherwise sync'd or backed up by default, so you'll have to do this manually.
On an Ubuntu-derived OS like Pop_OS!, you'll find them at: ~/steam/steamapps/compatdata/585420/pfx/drive_c/users/steamuser/Documents/TrailMakers/
(This path may differ slightly on other distros, but you get the gist.)
