Kolya Konstantin
Published
A few artifacts in some surfaces, very noticible on a shield.
Screen would flash black for a split-second sometimes. This became far more infrequent with extended play time.
The "upgrades" menu had an example video, which would flicker a lot.
As soon as I boot up the game there was a black stripe on top of the screen, which was resolved by switching to windowed mode and then fullscreen again.
Mouse would sometimes escape to second monitor from fullscreen. The way I fixed it was to click out of the fullscreen, then click back in. Pressing escape would sometimes fix the issue.
Framerate stayed through 60fps for most of the game, but would drop to as low as 15fps in crowded areas (mostly town squares and markets, the huge amount of rats were not a problem though). Sometimes the low framerate issues would go away with a restart.
Closing the game would not close it right away, and cause a crash on wine64-preloader.
It runs, but has a few issues
Input felt a bit off, and mouse sensitivity was very inconsistent
Significant stuttering issues, that go away after some play time for the most part
Zombies would not launch at all (black ops server was off?) and campaing showed some issues in gameplay, overral not a good experience.
When alt-tabbing from fullscreen, the mouse inputs won't work outside the game screen when it's standing still (?) not sure how to explain it better than this, but switching to borderless windows fixes the issue.
It was crashing exactly at chapter two of the campaign whenever the gameplay switched to a cutscene with some robots and a glitch effect on the charachter. It resolved when I switched to the most recent ProtonGE, at time of review. Overral I recommend using ProtonGE to run this.
Was able to join a multiplayer match and also play online zombies with friends.
Game worked fine on Proton Experimental and Proton 7 without any tinkering, but ProtonGE made the campaign not crash on cutscenes.
Worked OOTB without tinkering
PLayed almost 100 hours worth of multiplayer without issues.
Works OOTB without tinkering
A few stutters when first launching the game, ran perfectly afterwards
Worked OOTB no tinkering on max settings
Glass effects inside a helicopter, near the end of the game were a bit off. Unsure if it's a proton issue or badly implemented reflections.
--launcher-skip -skipStartScreen
alt tabbing crashes the game and had to use the command key to minimize
Ran worse than windows (50ish fps on windows/ 20-30ish fps on linux)
The CDPR launcher wouldn't start, making the launch option to skip it necessary
My hardware is not really that good and it didn't run cyberpunk very well on windows either, but I just can't tolerate anything less than 50fps. I tried running ProtonGE as well, same performance. It ran worse on linux than on windows without much tinkering but it is still playable if you don't mind the 30ish fps mark.
DXVK_FILTER_DEVICE_NAME="NAVI21" %command%
Might be an issue on my system, but I often have to specify the GPU, game ran without any issues. Had a crash once or twice, but that's on the game from what I've read.
Worked OOTB no tinkering
Online play is not directly done with other players, but it did connect and seemed to work as intended.
Ran OOTB no tinkering
The windowing is a bit strange, it seems to change on itself and go back to normal every time you change levels, but i doesn't really affect gameplay, you'll just see a bit of your desktop for a split second.
Game ran fine on highest settings OOTB.
Works out of the box, played through the DLC with no issues
Didn't even feel slowness that some windows users reported at launch.
Worked OOTB without proton
The game runs natively, no proton required
Works very well OOTB no tinkering
Had to turn down some graphics settings for some more fps, but it isn't significant, the game works very well OOTB
mangohud %command%
Sometimes keyboard input would simply freeze, might not be related to proton though, I couldn't really point out the source of the problem
I had a few performance issues when using Xorg, mangohud would say it was running on 60fps but it would surely feel like 30. Was 100% smooth on 60fps on wayland though
Worked OOTB no tinkering
Hosted a session with two other players without problems
Worked OOTB, no issues
Played a few sessions with friends and had no issues.
Runs OOTB with a few issues
Game runs at 30 FPS at all times and goes down to low 20s sometimes when doing executions.
Game sometimes freezes, which is fixed by alt+tabbing and going back to the game.
Game was opening for a splitsecond in a blackscreen and immediatly closing, so I put up the logs in the launch options with PROTON_LOG=1 %command% and found out that I was getting a DVLK error from having installed the wrong packages with packman, since the default installation is with lib32-amdvlk after removing them and installing the nvidia utils, and I got the game working by running sudo pacman -S lib32-nvidia-utils && sudo pacman -Rn lib32-amdvlk. TLDR: it wasn't working because it was trying to run amd stuff with nvidia GPU, intalling the right stuff and removing the old one fixed it.
At startup both sticks were moving at some random direction, and simply moving them yourself fixed it.
Game runs pretty well, the issue I had was that the game would quickly open and close itself, and inspecting the logs with PROTON_LOG=1 %command% I found a vulkan error due to amdvlk being installed instead of nvidia utils, so if you are having problems with an nvidia GPU, check if your default steam installation hasn't gotten amdvlk instead of nvidia-utils, if it has, at least on arch you can run sudo pacman -S lib32-nvidia-utils && sudo pacman -Rn lib32-amdvlk to remove amdvlk without breaking your steam installation.
env LD_PRELOAD="$LD_PRELOAD ./libsuperblt_loader.so" %command%
I tried both native and proton, both with UI mods installed. Both worked, but the proton version got very unstable, specially when playing multiplayer. I tried because I've seen people saying that it worked better for them, so I gave it a try. When it comes to modding, it's done differently for each build of the game and I found steam guides on it:
- Native: https://steamcommunity.com/sharedfiles/filedetails/?id=801187233
- Proton: https://steamcommunity.com/sharedfiles/filedetails/?id=1906996593
Both builds were tested using HUD mods. The native build was just a better experience for me. The launch option provided is required to get BLT to work on Linux.
Works great OOTB with very minimal issues
Sometimes mouse input would not work properly after alt-tabbing, fixed by restarting.
Worked better on windows, still very much playable.
Works OOTB but needs in-game graphics settings tinkering to run at 60FPS
Regular settings would get the game into the low 30s FPS mark. After turning down most of the graphic settings it ran smooth in the 60s with occasional drops. It's a lot worse in the first levels, which are more expansive and open.
Runs great OOTB, few issues here and there
Game needs to be paused in order to alt-tab properly when using borderless window. when alt-tabbed the game still does not stay in the background, right clicking unpauses the game even when not in focus. Also, the screen that has the game running can't be used, since it does not properly go into background.
When you click exit game it crashes and needs to be force stopped. Not the worst thing, but it happens.
Ran flawlessly with proton
Had a 6 hour session without any issues.
I went with proton because I read reports that the native port was bad. Proton did not disappoint.
DRI_PRIME="GPU_ID" %command%
The game was initally launching with 10ish fps, until I found out it was using the integrated GPU instead of the dedicated one. I restarted the game with DRI_PRIME=1 but it was still having performance issues, the way I fixed it was by listing all my graphical devices and their IDs with lspci -nn | grep "VGA" and grabbing the right ID, then adding it to the launch option DRI_PRIME="GPU_ID" with the string being my GPU id.
GPU id should look like 1000:124d. I don't know if all of this is necessary , but it's the way I found to fix it.
If it selects the correct hardware from the get go (which it should, idk why this issue was happening to me) it runsjust as smooth as it does on windows, if it happens to get your integrated graphics instead of the dedicated one, it's quite easy to fix (even though it took me more than I'd like to admit to figure out how)
Works OOTB no tinkering
Played long sessions with friends without issue
Framerate stays in the 30s, but it's running just as bad on windows, so I believe it's more of a general performance issue
Worked fine OOTB
Worked without any tinkering, with slight stuttering at first, but it went away afterwards. On initial setup it asked to install a dependency, which I just accepted and it worked.
Runs Great OOTB without tinkering
Few FPS drops here and there, but never to an unplayable framerate
Worked OOTB no tinkering
Played with friends most of the time without issues.
Runs fairly well OOTB, with a few tweaks
Alt-Tabbing out of fullscreen made the screen black, putting the game on windowed fullscreen solves the issue.
After turning down the graphics I have stutters and general performance issues when looking at the ship, during the introductory quests, such as discord lagging voice transmission.
SDL_VIDEODRIVER=x11 gamescope -W 1920 -H 1080 -f -- %command%
Game would crash completely in opening titles without running gamescope. Had severe screen tearing in X11.
Game works well, I was able to play a few campaing levels and also multiplayer
Worked OOTB with almost no issues
alt-tabbing while loading sometimes crashes the game
After a few raids game gets suddenly slow, but seems to be a problem with the game's engine AFAIK
