
[HIDDEN]
Published
Just doesn't work.
Furthest I got was installed Origin, game launching, loading, and then silent crash before ever getting to the menu.
Tried Proton versions (in no particular order): 3.16-8 3.7-9 4.11-13 4.2-9 5.0-10 5.13-5 Experimental
Glorious Eggroll versions: 5.21-GE-1 5.9-GE-8-ST 6.0-GE-1
Tried changing WINE environment from Windows 10 to Windows 8.1, 8.0, 7. Tried installing dotnet472 via protontricks. Purged the prefix in between most of the tests. Disabling videos via -novideos launch option, loading a save from another user, playing with .ini file settings for the game such as vsync on/off, resolution, full screen/windowed, winecfg and changing to a desktop container... Possibly more things that I can't remember, been several hours over 2 days trying to get this to work.
Runs essentially flawlessly.
Occasionally a key would "stick" specifically 'a' and 's' when panning the camera. Pressing them again would "unstick" them and the camera would stop trying to pan. Also, sometimes the spacebar wouldn't pause the game.
Honestly not sure if these are issues due to Steam Play/Proton or the early access aspect of the game.
Also, the game wouldn't start when installed on an NTFS formatted drive. Moved it to my ext4 main drive and it started up without a problem. Worked running 4.11-8, but not 4.2-9.
Works perfectly
The demo is currently a ~2 year old state of the alpha game with the full release slated for later this year. The old version of Proton I was using now causes the game to fail to start at all, but switching to default version (7.0-4 at time of writing) works perfectly.
I did not purge my old prefix, but I don't remember doing any tweaks before, so that shouldn't be of significance.
9 watts and 40 fps limit low graphics
Tried playing with 4x bots, it lags every time I get near them. The more bots the worse it gets. It's rubberbanding like it's a bad network connection but it's just bots and it shouldn't matter but I have strong wifi and a fast internet connection
Avoid solo play with bots, it's unplayable with constant rubberbanding every time you get near a survivor. Everything else was flawless. Could play on High Graphics without limiting power, and setting to low worked perfectly limited to 9 W, 40 FPS as others have noted.
Completely broken
Used to run native, but since upgrading to Ubuntu 22.04 (I guess?) it doesn't run natively anymore. I tried various Proton and none of them worked, they all instantly crash. 7.0-2, GE 7-17, Experimental [bleeding-edge], 6.3-8, 5.13-6, and all resulted in the exact same instant crash. Guess it's time to try Dirt Rally 2.0.
protontricks 359320 -q dotnet40 win7
Had to clean the prefix out as others have mentioned. rm -rf ~/.steam/steam/steamapps/compatdata/359320/pfx
then launch game, wait for it to fail, then run the above protontricks command.
Turns out that for some reason I have to reboot to get the game to launch a second time when running full screen or boarderless. Windowed I can start it over and over without issues.
If I can figure out the issues with full screen, the game will be flawless. Running at Ultra with supersampling set to 1.25x and framerate capped at 90fps, I get full performance with barely any dips, and nothing below 60 fps. Works with Linuxtrack (https://github.com/uglyDwarf/linuxtrack) using TrackIR5 hardware.
Seems bugged on AMD gpus
vk_amdvlk %command%
Tried RADV, tried AMDVLK, tried 8.0-4, Experimental, GE 8-16. Tried on spouse's KUbuntu 22.04 with a 5700 (non-XT) on both RADV and AMDVLK, 8.0-4, and Experimental. RADV will crash the game after about 5 seconds. AMDVLK will work to create a character, but crash your DE to login whenever you try and play a game. Same case on my Arch and their KUbuntu.
Didn't start at all (instant close, no error message) when it was on a NTFS drive. I opened properties and told Steam to move the installation to a ext4 drive, same where Ubuntu is installed ( ~/.local/share/Steam/steamapps/common ) and it started up, let me play two short matches against the easy AI, and close the game, all with out any issues.
I did have to go into sound settings on Ubuntu and re-specify the output device but that's been a regular issue with Ubuntu for me and unrelated to Steam/Proton as far as I can tell.
Runs essentially flawlessly
I did notice in the multiplayer screen whenever it refreshes the list of available matches it freezes for maybe half a second. This is only an issue on that screen and didn't have any impact on actual game play, online or otherwise.
Works better than on Windows.
I had a major headache when trying to get the game working on Windows a few months ago. On Ubuntu, with Proton, it worked flawlessly right out of the box with no fiddling around.
Linux version doesn't support VR. Forced Proton and it worked great!
There's a native Linux version, but it doesn't support VR. If you force Proton, you can use VR. We played with HTC Vive and had zero problems with the game.
Proton version 5.13-4
Deck Performance framerate limiter set to 30 FPS, Watts set to 5. In game set FSR to 2x (I think it was called Performance)
There's no binding for sprint in the default scheme. There's also no binding for shoot in the starship by default, but you can change weapons. Looking around with the thumbstick on foot, or using the touch pads, it's got a weird almost rubber-banding effect. I'm pretty sure it's the way the game handles the input because my spouse reported similar issues using an Xbox contoller on Windows. We don't have this problem on Linux/Windows using a mouse.
Worked well with no tinkering required (demo)
Did have some jerky animations, but I think that might be part of the artistic style for the game. One point a sound (when gaining currency) kept playing for about 2-3 minutes before stopping. I also got stuck in a trade dialogue where I exited by alt-f4. I think these are bugs in the game and nothing to do with Proton. Overall good experience.
Launches, but unable to start or load a game.
Tried Proton 5.0-7, 4.11-13, 4.2-9 (gives error "Steam must be running to play this game (SteamAPI_Init failed)), 3.16-9 (same error), and Glorious Eggroll 5.5-1, and 5.6-2. Tried playing around with the graphic settings to see if that would help any and had no changes.
Items in inventory sometimes fail to render, or render a low poly model. This seems to correlate with how many items are in my inventory.
I needed to update to at least Mesa 23.1.6 (did so via Kisak launchpad) as Ubuntu 22.04.3 LTS was too old (Mesa 23.0.4). I also tried both Proton Experimental and GE8-14 and both worked.
Mouse clicks and scroll wheel make the camera spin around ~1/4 turn per click making it impossible to interact with objects. Rebinding "use left/right hand" to other keys (like z/x) gets around that, but you still have to scroll to change blueprints as far as I know. On Proton 4.2-9 the mouse will occasionally screw up and not be properly captured by the game and will cause you to go spinning even at the slightest movement (more rapidly the further your mouse is from center) but 4.11-5 doesn't seem to have this issue. Both have the spinning when clicking/scrolling however. Otherwise, game runs as good as on Windows. It was Platinum before the latest update which I think changed versions of Unity. Right now it perfectly fits the Bronze description "has issues preventing from playing comfortably" as it definitely runs well except for the discomfort of spinning when you use the scroll wheel or have to rebind mouse clicks to keyboard keys.
Using Proton 4.11-8 I had major shader issues, almost like I had color inversion but weirder. On 4.2-9 it worked fine.
After a couple hours of play, and probably due to alt-tabbing, the mouse would get some weird behavior like it wasn't being recentered on the screen and when the position updates the distance from center is how far/fast the camera would rotate. If the mouse was near the edge you're going to rotate fast. Alt-tabbing back and forth a couple times got it working right again and I played for a couple more hours without issue.
GPU was only about 40-45% utilization, CPU was around 80% and htop was showing it was mostly kernel time for the game. Was getting around 40-50 fps on maxed settings. Fairly sure I was getting 60+ on Windows with same/similar settings.
Until the fixes get pushed to the main branch, make sure you op in to the bleeding-edge "beta" of Proton Experimental.
Game does not appear well optimized yet, changing graphics settings had no significant effect on frame rates. Same on Windows.
Just a bit of awareness where your camera is and trying to keep combat out of the forests keeps frames high and the game enjoyable.
6.19-GE-2 GloriousEggroll
Glorious Eggroll 6.19-GE-2
Certain areas of almost all combat zones have SIGNIFICANT problems, frame rates down in the 2-7 range. Moving the camera can bring it back up to 50-100. There is something that the driver doesn't like or is poorly optimized, I think it has to do with the trees? The overworld and majority of the area when in combat works very well.