Vroomstick
Published
Better performance, possible audio issues
Loud and noticeable popping/crackling in audio playing with Proton. Native version did not have this issue.
Running through Proton on max settings, I got about 20fps more on average than native version, but did experience frame drops when caching shaders, as expected. I would recommend the native version unless you really need the performance boost for more than 1080p@60.
Can't get past launcher
Launcher opens, but the text boxes are all empty. The launch window cannot be moved or interacted with, and must be killed via terminal. Enabling D9VK and disable Esync had no effect.
-oldgameui
Native version has lighting issues that make the game nearly unplayable in some sections, e.g. almost everything will turn pitch black and the flashlight will stop working. Proton version does not have this issue. Add %command% -oldgameui to the launch options, otherwise the main menu will be invisible.
Native version didn't work for me, returning an error about a missing executable. Forcing Proton worked perfectly.
Crashes shortly after launch
Crash is delayed slightly if game is opened on a workspace with no other windows. Using Wayland with XWayland enabled.
Opens a small black window, then immediately closes. Continues running in the background (plays music, Steam cannot stop it)
Using Wayland with XWayland enabled.
Cannot recommend due to the display issues. It's not fun when every load screen can break the game.
When health is low, the blood effect is heavily pixelated, obscuring vision almost completely.
Game will occasionally display only a black screen after loading, requiring a restart. Sometimes the main menu can't be interacted with, also requiring a restart.
Game window cannot be interacted with
Unplayable. Game opens and displays menu, but game window cannot be moved or interacted with. Must be killed from terminal.
Avoid if you want to play The Fruit
After exiting a game and re-entering the hub, the mouse would no longer remain bound to the window until I alt-tabbed twice.
The Fruit apparently crashed my graphics driver, requiring a full reboot. The same happened with Proton Experimental. This does not seem to be a Proton-specific issue, judging by the Steam discussion posts about it. There are no known causes or workarounds, it's just going to be luck of the draw whether the game works for you or not.
Proton 8.0-5
Running with default settings will open a fullscreen window that's either all black or covered in corruption artifacts. Sounds will play normally but the game is unplayable and the process must be killed via console.
Add 'PROTON_USE_D9VK=1 %command%' to the launch options and it will run perfectly. I got a consistent 120FPS on my system with high settings and 4x MSAA.
Note that if you use fullscreen mode, the game window will turn all black and become unplayable if you change window focus. However, changing workspaces works fine. Adding '-windowed -noborder' to your launch options may fix this, but I did not check.
When another window is focused, the game screen shrinks to a tiny part of the game window.
Game launches, but stuck on loading screen indefinitely
It's not hung, there's a little animation that the loading bar continues playing, but it never progresses. Tried with Proton 6.3-7 and Experimental. I recommend using RuneLite instead, since it has a native Linux build.
Frequently crashed during missions. Was unable to complete any missions. Could not even attempt to troubleshoot as these crashes did not create crash logs. -crashdump launch option did not create crash logs either.
One other player joined my lobby and was able to play with me, until I crashed.
Tried Proton versions 8.0-5, 9.0 beta, and Experimental.
Runs extremely well in Proton. 60fps at max settings, with maybe 2 or 3 dips during the 30 minute playtime (probably compiling shaders).
Only issue was some weird shadow flickering and clipping in the opening cutscene, fixed by changing to DX11 in the menu.
Native version requires beta branch opt-in, Proton works almost perfectly
If you install the native version without changing to the beta branch or forcing compatibility settings to use Proton, you'll get a 0B install that passes validation (the dev did this on purpose). The only issue I had with Proton was that there's a separate executable for modifying settings, and I couldn't interact with it. The defaults are sensible and I think there's an .ini file you can edit to change the settings anyways, so it wasn't a problem.
White screen with sounds after startup menu, unplayable
The main menu and settings work after launching. Clicking start fades out the screen, then fades in to a pure white screen with a typewriter clack sound playing in the background occasionally. Doesn't seem to react to any inputs.
Played through campaign twice and bonus missions once. Crashed exactly one time in 30 hours, after the gunship section in 5-4 on my first playthrough. Didn't crash on the second playthrough.
