odo
Published
Was able to load to pre-main menu loading screen, no further.
Using Proton 5.13-4 I was able to reach the first loading screen, however it froze after a few seconds and did not reach the main menu. Attempting to use PROTON_USE_WINED3D=1 %command% allowed me to continue past the loading screen, however it only resulted in a black screen.
Despite occasional FPS drops, the game runs perfectly fine as far as I can tell.
FPS slowdowns during cutscenes and open areas
Using the Next- beta branch of Proton 5.0 (5.0-10)
Works perfectly in 6.3-6
Crashed only once in my playthrough at a save point in Chapter 2. This may or may not have been caused by Proton.
Works absolutely perfect in 5.13-4
Alt-tabbing will sometimes eat up all of the system's memory, adding -RequireFocusToUpdate=false to the launch options fixes this.
It required zero effort on my part, the game runs indistinguishably from playing on Windows.
Game either crashes upon loading the game world or simply fails to.
The main menu loads fine, however upon starting a new park or loading into a save, the game with either crash to desktop or simply not load the world, leaving it a blue void. I attempted to play the game using Proton 5.13-4, 5.0-10, 4.2-9, and GloriousEggroll 5.9-GE-6-ST. All had the same result.
If I tabbed out while using fullscreen mode, I would not be able to tab back in. Borderless windowed works perfectly fine, however.
Disabling V-Sync in the display settings was necessary to achieve expected performance. FPS went from 50-60 to 170+ with V-Sync disabled.
Most cutscenes seem to be broken in Proton 6.3-6, appearing as a color bar screen with no audio. Using GloriousEggroll 6.15-GE-2 completes fixes this issue.
Disabled Esync in the game's launch options and ran Steam via the command line with the command "env STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0 steam". Works flawlessly after this.
Very poor performance
Tabbing in and out was spotty. It would frequently minimize itself when tabbing.
The framerate was unplayably slow no matter what settings were changed. There were short periods of smooth framerate, but it quickly changed back.
