
FreakBane
Published
Game was crashing every 1-2 minutes or so but forcing Proton Experimental solved that
THIS REVIEW IS MEANT FOR THE DEMO.
It works fine on Proton Experimental, not default version
Works perfectly out the box!
No tinkering done whatsoever. Clicked installed, hit play, good to go!
Works fine!
I did get the messages telling me to upgrade to Windows 10 (lol) and that my amd drivers were outdated (using a RTX3070 Ti) (lolol). But you can just ignore these and the game laucnhes fine, everything else works fine
Slow to start with even an error message but does eventually starts and then works well!
Did not work for me
Tried all versions of Proton from experimental, 7, 6 until 5
Tried the launch command, nothing happens. Tried different Proton versions and all have the same result. After 5-10 seconds, I get a fullscreen black screen, then I get a message saying the game isn't responding. Waiting did nothing.
Horizons works fine, some tweaking needed for Odyssey
Horizons works fine but I'm getting 20 less fps on average on Odyssey
But then I launched the game using WINEDLLOVERRIDES=”xaudio2_7=n,b” PROTON_NO_ESYNC=1 %command% as launch option and it solved everything
Mouse pointer goes out of bounds into my other screens, so then when I would click to shoot, if the arrow was on another screen, the game would downscreen
The game would run fine until I moved my mouse. Then fps dropped hard and basically any moving would make the game unplayable. So as pointed out in the audio section, I used the following as launch option on Steam:
WINEDLLOVERRIDES=”xaudio2_7=n,b” PROTON_NO_ESYNC=1 %command%
First start was stuck in loading. I disabled Steam overlay for the game and it ran fine
The planet thing on the main screen flickers from time to time. Nothing big though
Works perfectly out of the box!
Mouse cursor goes out of screen to show up on side screens (left and right side) and is usable. So clicking to use things ingame also clicks on whatever is going on over the other screen
Works even better than on Windows!
Playing on both Windows 10 and 11, I would get very low fps most of the time, playable but barely. That was with heavily reduced graphics. Running with Proton, I had just about all the time 100+ fps with full graphics options!!
Works perfectly!
The game on its own worked perfectly for me. No sound issue like others have been having (although I did encounter these issues with Fallout4).
However, modding was tricky. Lutris would not work to install Vortex whatsoever. So, I had to go the old fashioned way and download/install mods manually. Which works!
IMPORTANT NOTE FOR NEWBIES TO LINUX: On Linux, folder names are case-sensitive. That means that "folder" and "Folder" are 2 different folders for your file system. This comes into play here as I had some issues installing some mods initially as that was impacted. So be careful at the file names. If you just extract blindly into your Data folder, there may be several folders created such as "meshes" and "Meshes" and "textures" and "Textures". The game didn't seem to care which you end up using, just use the same and merge everything into one of these and you'll be fine
Works perfectly out of the box
Didn't use any kind of launch command or anything, works like a charm!
Works better with default Proton than native
I was getting about 24 fps on native, flat 60 fps with Proton.
The game installed and started well but the Play button from the main menu is not selectable
I did a quick search on Steam and there is no message indicating something about the game needing an online server that would have been shut down.
Works well!
Although on first launch I accidentally clicked on my other screen during the game's loading screen and that just closed the game completely. Relaunching the game worked and it ran well!
None. Using the one recommended in the other reviews actually prevented my game to launch at all
Joined a game online and hunted for a while with a random stranger without an issue!
No tinkering involved. I tried using the command thing (which didn't work). But enabling/disabling Steam Overlay changed nothing. So I ran it perfectly out of the box!