[NcK]MasterShake|CM
Published
Everything Runs Fine
I had to switch from Proton Experimental to Proton 6.3-8, but that's probably my fault rather than Proton's, if we're being honest about it. I haven't played an incredible amount of time, so I can't really list crashes, bugs, etc. But it installed, played, could input company name, build tracks and place trains.
Save frequently.
I'm not sure what qualifies as frequent versus regular-- but let's say I played for 4 hours and had at least 4 crashes. I'd qualify that as regular.
There is an ongoing project called OpenLoco, in the same vein as OpenTTD which hopefully resolves most of these issues and provides some much needed QoL love for this game.
Crashes on Tutorial
Starts generating a map and then locks up.
It ran as well or better than it does on my windows machine, though I would stress: the hardware in the linux machine is far, far newer.
Did not attempt resizing, minimizing, etc. So, not YES... but also not NO.
This was the first time in a long time that I've attempted trying to run windows games on linux... was blown away.
Runs great, plays great.
Audio only seems to come out of a center channel speaker.
Didn't try anything with regards to resizing, minimizing, etc. It opened full screen, it stayed open full screen.
No Joy
The autorun launcher pops up, but attempting to launch the game with it does nothing. Attempting to directly run the executable instead of the autorun crashes with something that I believe is related to .NET 4.
Fun knock-off Fire Emblem
Retaining the volume level settings between games seems a bit off. It can be quite loud, even if the sliders are set very low. Subwoofer owners, be advised.
Seriously though, if you have subwoofers: the SFX for blunt weapons is going to rattle your house.
Final Cut is disco, baby.
In certain menus at certain positions on the screen the lower half of button-text could become slightly blurred. Nothing in the game itself and not so blurry so as to be illegible. Simply, noticeable.
This was the Final Cut update that was played.
Works on My Machine™
Using a Steam controller and if you wander off for a while and the controller auto-disconnects due to being idle and you turn it back on, it's not detected/doesn't function... it will also hang on shutting down.
I would say the FPS are lower than they should be. It's completely playable and smooth-- but lower than where it should be for what it is. VSYNC also doesn't seem to function.
I can't speak for autoplay movies-- they do not seem to play with the default settings that are being used-- so: no opening movie or presumably any other movies as it may or may not apply.
Recent update completely borked Foxhole
It's broken across essentially the entire Linux community /including/ Steamdeck users. So, if you are using Linux and hoping to play Foxhole... at the current juncture, to the best of my knowledge, it is not possible. The fix may come tomorrow, the fix may come never... but presenting the game as currently playable "Gold" status to people on protondb is utterly inaccurate. It is completely broken, and until you read reviews more recent than this one saying otherwise, it is best to assume it remains broken.
Demo ran fine
I didn't play for long or try numerous different things-- such as resizing windows, saving/loading etc... so take this summary with a large grain of salt. It did install and run just fine, performance seemed okay, but I have nothing to really compare it with.
Native version broken, Proton worked just fine
Less than 1 fps on the "native" version, it didn't work at all. Swapped to Proton version and everything worked just great. Good sound, good performance. I can't speak to long term stability because I didn't play for that long. Did not attempt multiplayer, but the odds are better for MP on the Proton version anyhow given my understanding that the Linux native client can only play with other Linux native clients.
It will occasionally just dump on you. I've never run it under Windows, so I cannot say if this is unique to Proton. Played ten hours, had two crashes. Given the frequency of save spots, it shouldn't be a huge issue... but save when able just in case.
I didn't have an audio desync or crackling problem. As others below have noted, certain [media foundation?] dlls need to be installed and there is a nice easy github script that Worked For Me™
Without it, you won't be able to continue once you get on the boat... or perhaps any time a movie file needs to play.
