*=0=1=4=*
Published
env OBS_VKCAPTURE=1 gamemoderun %command%
This game runs perfectly, however do not use zen kernel 6.10.5. The game repeatedly crashed after about 5-10 minutes of playing. I was hosting a 2-player game; unsure if related. When using the mainline kernel, we were able to play a session for multiple hours with zero problems.
env OBS_VKCAPTURE=1 gamemoderun %command%
I tried the zen kernel after the next version, and it worked fine. I played a session for 2-3 hours with no issues.
Force Proton If You Have Multiple Monitors
As others have stated, you will want to force Proton if you have multiple monitors, otherwise the game attempts to stretch across both screens. What actually happens is I see half the game on one monitor, and my desktop wallpaper on the other.
The game asks if you want to run DX11 or OpenGL. I chose OpenGL. I haven't tried DX11 yet.
My PS5 DualSense controller worked using the in-game controller settings and selecting Steam Input as an option. From there, an official controller layout was available. My vertical look motion is not inverted when I want it to be even though Steam Input settings says it's inverted, so I might have to tinker with that.
I had to increase brightness within the game menu because it was too dark to see the truck's dashboard.
Other than that, smooth sailing.
Problem Free
I have not tried playing with friends yet, but everything else so far has worked smoothly. Zero errors or troubleshooting as of yet.
Perfect First Impressions
So far, so good on launch day! I chose Vulkan within the launcher settings. I've only played an hour or so thus far, but everything is working great "out of the box." I am getting 70 FPS or better in the opening area on Ultra settings with 1080p monitor.
Must Use DX11 Now
After patch #4, Vulkan no longer works.
As of patch #4, even after hotfix #10, Vulkan no longer works. You must use DX11. If you try to use Vulkan, after the intro videos, you will get two Assertion failed! errors. Both are for loader_thunks.c, lines 2657 and 2827: Expression: "!status && "vkCreateComputePipelines""
By the way, --skip-launcher --vulkan as posted here several times does not actually set Vulkan. You must use the launcher once to set the graphics API, and then it will save and you can skip launcher afterwards.
--skip-launcher
Vulkan doesn't work
Vulkan does not work still, but DX11 does.
A lot of people use --skip-launcher --vulkan in their launch options. It's misinformation. --vulkan does nothing. You have to use the launcher to set the graphics API at least once, then you can skip the launcher after that. Everyone using --vulkan probably thinks Vulkan works but it's actually using DX11.
Nearly Perfect
The game did not recognize my PS5 controller until I went into Steam settings to enable Steam Input. Then it worked! Before I did that, the wired Xbox 360 controller worked OOTB, but I didn't want to use that one as it's a bit old and mushy.
Worked OK
I had to turn on Steam Input to get my PS5 controller to work.
I am not sure if it's just the game or using Steam Input to get the PS5 controller to work, but the car did not respond very well at all. And button presses to activate boosts were quite unreliable. If you pressed and held, it would act like you tapped. But other times, it would work correctly. I don't plan to play again for these reasons and I don't want to try a different controller.
After initial logo screen, game presents a fatal error.
Tried Proton GE as well.
"Steam Client Error. Please quite the game, restart the Steam client and launch the game again."
This is for the demo. I tried regular Steam Proton and Proton GE. Same result.
Demo Launched on Second Attempt
The game crashed immediately upon first launch, however I didn't experience any problems afte the second try. It looks and feels nice.
Demo Worked Just Fine
The demo worked great and was fun. I used a PS5 controller.
During one of the early loading screens, I think there was supposed to be a cut scene or something. It looked like the game was frozen. What you have to do is press and hold X on your controller to skip.
Overall, I would wait until (if) audio gets fixed. 40 FPS most of the time and sometimes down to 30 in the club. Good enough considering.
Some environment (like club music and random NPC's talking) and distant gun shot audio are missing. Main NPC dialog audio is fine as others have posted. This is a killer though.
People's faces have a minor, wavy distortion when they're not up close to you sometimes. Kinda like heat waves.
I installed mesa-git and vulkan-git specifically to get this game working. I would rather stick with the official Arch repo, so I categorize this game as Tinker since I had to change something that affects my entire system.
If you're on Arch and want to install mesa-git, I recommend watching this guide video: https://manerosss.wordpress.com/2017/04/28/install-mesa-git-arch-linux/
Requires mesa 20.3.1 for AMD users and Proton Experimental
Recently, the game would only work properly with mesa-git, but I tested the new release of mesa 20.3.1 today and it worked!
This is a great relief for folks that don't want to run mesa-git system wide. Proton currently has a bug that prevents you from running mesa stable on your system and only using mesa-git for specific games. So it's great that mesa-git is no longer required for Cyberpunk and you can run stable mesa.
AFAIK, Proton Experimental is still required to fix audio crackling. That is just a drop-down in Steam properties of the game, so I don't consider this a "tinker" report anymore!
gamemoderun %command% --launcher-skip
Maybe almost year ago now, I used to have to use a Pulse latency override in the Steam launch options to prevent audio crackling and distortion. I also had to run Proton Experimental. I am happy to report that neither of those are necessary! In fact, today I needed to remove the old latency override in order to get rid of the crackling.
Using the benchmark within the game, the 6600 XT averaged 60 FPS with the Ultra preset @ 1080p.
As an aside, here are the customized options I use in the ~/.config/pulse/daemon.conf file on my system. These are preferences and shouldn't "fix" anything, but thought I could share since I mentioned previous audio issues.
resample-method = speex-float-10
remixing-produce-lfe = yes
remixing-consume-lfe = yes
default-sample-format = s32le
default-sample-rate = 48000
alternate-sample-rate = 192000
Works OOTB w/ Max Graphical Settings
This report is from Alpha playtest #4.
The Launcher Works
But that's it. The game itself does not start from the launcher. It closes itself.
Doesn't Launch
It will take some troubleshooting and debugging to see what the errors are. For initial impressions, it simply doesn't work.
Doesn't Start At All
I tried the public playtest, and the game will not even launch.
It's Essentially Perfect These Days
Playing EVE Online on Linux has been possible for many years, but it has never been this easy before. No effort at all.
FWIW, my Steam playtime for this game is not accurate since I played many hours outside of Steam.
Works w/o Tinkering
I haven't tried multiplayer yet, however everything else works and runs perfectly. Looks great.
The window to log in with my Xbox account took a really long time to load. I just sat and waited, and it all worked eventually.
Native Doesn't Detect PS5 DualSense Controller
PS5 controller was not detected. Keyboard controls are bad!
The A and Z keys are used for throttle and braking. Yikes! I will follow up with a forced Proton report.
Force Proton for PS5 DualSense Controller
I can't tell if the game has any matchmaking or not. I can create a private lobby and invite Steam friends or a public one, but I didn't see an option to join someone else's lobby. Nobody joined my lobby.
My PS5 controller worked great after forcing Proton and enabling Steam Input (mine is always on). When playing the native version, the controller was not detected even with Steam Input enabled.
I will assume that inviting a Steam friend to join your lobby will work. Steamdb.info charts show estimated player counts in the single digits at times, so plan on solo or with Steam friends only.
Game is fun!
Works well enough
The Windows host (not me) would crash every hour or so, and we'd have to reload the saved game.
Be prepared to reload every hour or two if playing co-op online.
env OBS_VKCAPTURE=1 gamemoderun %command%
Today is the first day I tried playing, and have not had any problems. I did not have any issues some others reported. I am using Proton 8.
Running the game on Medium graphics settings with native 1080p resolution and getting 65-85 FPS.
Quite Good
Even without a controller connected, the game acted like one was fighting my keyboard and mouse. It was unplayable until I enabled Steam Input, which made my keyboard and mouse work.
Perhaps the game detected my keyboard or mouse as a controller...? I am using a Razer Naga Pro which has buttons on the side. It was not possible to use the keyboard, mouse, nor controller until I force enabled Steam Input. Then, all of those accessories worked.
I got great framerates using High graphic settings at 1440p.
Keyboard + Mouse Don't Work
Enabling Steam Input oddly solved this problem a while ago, but it no longer does the trick. I cannot use keyboard and mouse because the game acts like I'm using a controller. I do not have any wired or wireless or Bluetooth controller connected.
I uninstalled the game and may retry with Proton instead of native.
I forced Proton 9 instead of native.
When the native version was installed, I was not able to play because the game acted liked I had a controller connected and holding leftwards. It fought my keyboard. I couldn't even navigate menus and had to Alt+TAB and then force quit via Steam.
Launches but doesn't get to main menu
The game launches, shows a logo animation, and then gets to what look like an animated loading screen. Around this point, the game crashes and disappears.
Can't get to main menu
Even using GE 7-29, I have the same behavior as vanilla and Experimental Proton. The game crashes during or right after the animated loading screen.
I previously reported this game broken, but it started working later on
You have to use GE-Proton7-51 now.
If you install Proton-5.21-GE-1, the game works perfectly and you can play co-op with your Steam friends.
Proton-5.21-GE-1 GloriousEggroll
Start the game with -windowed in Steam launch parameters and then change to fullscreen-windowed within the game.
I used to be able to play the campaign online with a Windows friend, but it stopped working which makes the game worthless to me.
If you want to play by yourself, it should work.
Only if you want to play by yourself.
Cannot play multiplayer whether I launch with or without EAC. What is Halo without multplayer or co-op?
Co-op used to work a year or so ago. Then it broke while a friend and I were in the middle of campaign. I decided to try it again since there are good reports, but it doesn't work for me still. SUCKS.
Experienced nearly constant desync problems at checkpoints when playing co-op campaign until I changed two things: I switched to GE-Proton and locked vsync to 60 FPS to match my friend's vsync. I don't know which thing was key, but we never had the desync problem again.
Once we got past the desync problem, there were no other issues. Pretty cool to play this game 20-25 years after it came out at a modern resolution, and on Linux.
gamemoderun %command%
I only tried the firing range so far, but everything was smooth. 70+ FPS on Epic settings and 2K resolution.
Works Out of the Box
I had to configure settings to Near distance because certain objects, I think the asteroids, brought my FPS down to around 15. Units on screen did not have this negative effect.
I think they need to optimize the asteroid rendering performance, otherwise everything else worked well and looked good.
It stopped launching. During the game splash screen, there is an error that says the anti-cheat did not load.
gamemoderun mangohud %command%
It's broken! Impossible to play.
gamemoderun mangohud %command% -nominidumps
I can't use the Steam overlay with this game, which is the only reason I use MangoHud.
About a week ago, there was an anti-cheat error that prevented me from playing. The game wouldn't launch. Today, it's back to working again! Runs great and looks great.
mangohud %command%
Every few months, you might not be able to join a server due to an anti-cheat error. When this happens, close the game, validate integrity of files (which ends up updating EAC on your computer), and then it should work again.
The only reason I use MangoHUD in this game is because the Steam overlay does not work. Not required.
EAC Unexpected Error #1
I have over 200 hours in the game, but have not been able to play for about a month.
Installed Steam from Flatpak
For users of cutting edge distributions, Sandstorm does not work. You either have to run a customized C library to re-enable deprecated hash algorithms (not something I would do), or you can install a secondary Steam instance via Flatpak. So, now Sandstorm is the only game I have installed in my Flatpak instance of Steam. I use the normal version for everything else.
Maybe Flatpak will be the normal version someday, but it's not yet.
Anti-cheat Broken
Anti-cheat doesn't work again.
You used to be able to trigger an update to EAC by validating local files, but that trick doesn't work now. I already went through the hassle to run this game by installing Steam in Flatpak. That worked for a while to solve a different problem. I am just torturing myself at this point trying to play it. I have 217 hours. It was fun for years. It's been aggravating and unreliable for many months now. I'm mad.
It Works Again
This game broke for several months (very aggravating), but is playable again with no tinkering. I still have the Steam overlay turned off for this game, but I don't know if it's still necessary.
WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%
WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%
If you want the cut scenes to work in between campaign missions, you need to use the launch parameter.
Besides that, no issues! I've been playing co-op with a friend on Windows. Just add them to your party before you start a campaign mission.
No issues
I thought I had an audio problem with the game, but it turned out the game application was muted in my system settings even though nothing else was muted. Not sure what did that. Not something I ever do.
Worked Fine
Everything seemed fine. I did not link any accounts, so didn't have any problems there.
Perfect Out of the Box
I only tried "instant action" in single player so far, and it was problem-free.
Just Hit Play
May not be specific to Linux, but there is overlaying text in the main menu UI, causing a couple things to be illegible.
Install and play; nothing else needed.
No Problems
Everything worked. Smooth experience. I did not purchase anything in-game, so that experience is unknown.
Hit some buttons to get past initial black screens
Intro videos do not play.
Solo Play is OK at Least
I played a local game for a while without any issues. I have not tried joining or creating a public server at this point.
ProtonDB apparently doesn't ask if you've tried multiplayer anymore.
I had to use the Easy AntiCheat file from Apex Legends.
After dropping in the EAC file from Apex Legends, the game worked pretty much flawlessly. I am not using any launch parameters. I ran DX12. I played through the entire campaign with some buddies. They were both on Windows and Linux.
Performance was unplayable until switching to Proton 7.0-6
Before switching to Proton 7.0-6, movement and combat were too laggy to be any fun once you get past the intro areas and finally get to the real world. After switching to 7.0-6, it's much smoother and feels pretty good.
Plays Great
My DualSense controller over Bluetooth was not detected until I enabled Steam Input. Then it worked fine but had Xbox glyphs. I've heard Playstation controllers are detected when using a wire, but I didn't want to use one, so didn't try.
If you are using a Bluetooth controller (not wired), you might have to turn on Steam Input. But this is very easy.
Demo Worked Great
I have only tried the demo thus far, and it worked great. PS5 controller worked, too.
The Demo Won't Load the Map
It crashes after saying Loading complete.
Add "game_client.debug.override_processor_architecture": "AMD64", to SteamLibrary/steamapps/compatdata/1575940/pfx/drive_c/users/steamuser/AppData/Local/sins2/settings/settings.json
Crackling during the intro scenes of the game, but it goes away.
The only thing I had to do to get past the multiplayer join problem was add a single line to the settings.json file. This overrides the CPU architecture so it doesn't have "wine" appended to it, thus allowing you to play with others on the same AMD64 architecture. Everything else was standard Proton and standard settings.
If you have never played the game and are trying to find the settings.json file, it won't be there. You have to launch one time first, then it will be created.
PS5 and Xbox 360 Controllers Didn't Work
The game starts up just fine. But I just couldn't get my wired controllers to work. I tried using the Steam config tool and Proton GE, but nothing helped.
I've used these controllers in many other games, for example Outriders yesterday. Pretty odd that this game doesn't work. I requested a refund. It's a shame.
Worked Great
I played one Team vs. Team multiplayer match from beginning to end without problems.
When the game launcher opened, I went into the settings and selected full-screen windowed, Vulkan instead of DX12, and High graphics preset minus motion blur. I enabled Easy Anti-Cheat. Once I clicked Play, it asked if I wanted to install Easy Anti-Cheat, and I said yes. It all worked just fine, and performance and visuals were good.
Close to perfect
Getting your friends connected is unreliable and takes a few tries. The host might have to restart their session. I don't think it's a Linux issue. Once your buddies are in your session or you're in theirs, no problems. Very stable.
Wired Xbox 360 and PS5 controllers worked for me.
To get PS5 controller to work, you have to enable Steam Input. The 360 controller buttons will display in the game UI, so you have to translate that to PS5 buttons in your head. Becomes second nature to true gamers. ;)
Works
I didn't get the time during the free weekend to try DX11 or lower graphic settings, but DX12 and High performed too poorly to play competitively. Also couldn't confirm if it was server lag or not.
No Troubles
Played a co-op match flawlessly.
I did not experience anything that felt like a bug.
Demo Worked Fine
I don't think this demo has a save ability. No technical issues with the game. Ran fine.
Seamless
There was a little slowdown in the demo compared to what I'd exect, but it didn't go lower than 65 FPS, so not what I'd call a problem.
Download and play. It worked perfectly.
The game would not launch on regular Proton version, but everything seemed just great with GE-Proton8-14.
Initial shader processing took a long time, close to 15 minutes! Subsequent launches are much quicker.
Slow to Load the First Time
No tinkering required. You may have to relaunch once after the Ubisoft Connect application updates itself. The game actually worked! I haven't tried playing online with a friend yet, but everything else worked just fine.
The game is taxing on your system.
Cannot Get Native to Work on Arch
I tried the various LD_PRELOAD commands in other reports, but simply cannot get the game to run on my system in Steam or GOG.
There are other Arch based systems in the house where it works. It works in two of my VM's.
I've spent hours trying to get it to work on my system. The launch error is useless. Worth a bork report IMO (when native).
Forced Proton
I could not get the game to work natively. I tried messing with library files for hours. Forcing Proton makes the game work.
Demo Worked Great
The demo took a long time on the initial load and felt a little slow considering the graphic style, however everything worked as it should. The game not released yet, so keep that in mind.
Essentially Perfect (demo)
The first-person perspective and roundy (chunky?) art style remind me of the feeling of Bioshock Infinite. The narrator adds a lot to the momentum.
Disabled Steam overlay.
I could not get past the logo screens until I disabled the Steam overlay. Once I did, everything else was great. I used a DualSense controller over Bluetooth.
Also, when closing the game, it chokes up. After it sits for a long time, it eventually closes with two errors. One is the original error, and the second is failure to write the error to a storage path. This does not have any effect on the game though.
Disabled Steam overlay.
AVF error prohibits online play.
Due to AVF error, Linux players cannot connect online anymore. This is a shame, as previously, my friend and I completed the whole campaign together and we could not think of a single bug. The recent patch from a couple days ago added some great features, but caused this network problem for Linux players. I can only play solo now.
One person on a Steam forum said that Saber Interactive support was aware of this problem and was working to fix it.
SteamDeck=1 %command%
After patch 3.1, the AVF error preventing online play has gone away only if you use the SteamDeck launch parameter.
Vanilla: Game would not launch at all.
Force Proton: Wouldn't get past splash screen.
Alternate Mod Launcher: That was janky since I didn't have any mods or DLC, but it got the game launched. I played a few missions until the game would freeze on the flight home.
Proton-GE7-49: Seems like everything works with this.
Demo Worked Great
I am not sure what the difference is between the demo and the prologue, but I played the demo before the full game was released. No problems that I can think of.
