


Completed it with mods, HDR, and maxed out to the capabilities of hardware. Only problem, window boundaries fixable with launch command
HDR on && gamescope -f -w 3840 -h 2160 -r 60 --hdr-enabled --adaptive-sync --force-grab-cursor --hdr-debug-force-output -- %command% --launcher-skip --modded --intro-skip --skipstartScreen
Usage of mods: Path tracing, photo mode, weather, textures, RenoDX HDR, Reshade
Fixed with --force-grab-cursor until gamescope 3.16.2. New versions are borked
Works really well, tinkering makes it a better experience visually, but on basis works perfectly. Dogtown is the limit of what my graphic card can render, with Path Tracing mod falls under 60 with Intel Xess performance at 2k. FSR gave me worse performance and graphics.
Optiscaler and all the FSR 3.1 frame gen mods gave me problems and made the game unplayable.
The HDR command is a custom script to turn it on.
DXVK_FRAME_RATE=165 %command%

DXVK_HDR=1 --launcher-skip
DLSS Framegen buffer lags one frame behind, causing a severe stutter/blur that makes the game unplayable. Stutter is not always present, but once it appears it will never go away.
I updated to the beta drivers to try and resolve the stuttering issue, but they were still present there. Classic Nvidia... Anyway you can play the game fine with FSR frame gen, but it looks awful. Alternatively, you could also play it with no frame gen... at reduced settings... thus making it look awful... Long story short, if you're playing above 1440p with anything less than a 4080 you will need to wait until Nvidia stops dry humping their piles of AI money if you want to play this game and have it look good on Linux.

WINEDLLOVERRIDES="winmm,version=n,b" %command%
Sometimes crashes, but it might be just because of my hardware, mods work fine, can't say anything negative
gamemoderun %command%

%command% --intro-skip -skipStartScreen --launcher-skip
In the end, somehow magically reinstalling the MESA drivers helped, I ran these commands:
sudo apt-get remove mesa-utils
sudo apt-get remove libgl1-mesa-dri libgl1-mesa-glx libegl1-mesa libgbm1 mesa-utils
After this command, GNOME crashed for me
sudo apt-get install libgl1-mesa-dri libgl1-mesa-glx libegl1-mesa libgbm1 mesa-utils
It seems like I rebooted here or a little higher, I don't remember exactly
sudo apt install --reinstall gnome-shell
and I rebooted through the gnome login manager that started after this command This somehow triggered the first launch in which FSR was disabled
I spent about 2-3 days to get the game working. The main problem was that versions 9 and 8 of Proton, when resetting the settings to "default settings", included FSR, but with FSR enabled, the game hung on the CDPR logo on the loading screen, deleting UserSettings.Json, the game could not start in any case, because the default settings included FSR
When I accidentally enabled FSR for the 2nd time, it seems that reinstalling Mesa didn't help, but the game worked after reinstalling Nvidia drivers
It is worth saying that the very first time the game launched to the main menu with FSR disabled, I immediately turned it on out of curiosity to see what would happen and it killed 2 days of my time, neither reinstalling the game, nor reinstalling Steam and CompatData, the game continued to launch with default settings in which FSR was enabled

I ran it with GE since I run everything with GE.
Flashing lighting effects. Fixed when dynamic FSSR or similar is disabled.
Run on Medium graphics with FSSR3.0 + Frame generation on gives good framerate with okay visual fidelity.
When I searching through forums on other sites about my config, other users noted that this game only functions on Linux using Proton 7, later versions do not work with Nvidia's Pascal (10XX series) cards.
Runned perfectly out of the box

Slight performance decrease (around 15% less fps) in comparison to Windows with same settings
I have tested it with different proton versions, different windowing options, different launch options, and got different results. If something works worse than expected, i recommend trying to switch up some options and find what works best.
mangohud %command% -skipStartScreen --intro-skip --launcher-skip
Works flawless Surprised by its performance
WINEDLLOVERRIDES="winmm,version=n,b" %command% --launcher-skip --intro-skip -skipStartScreen
Works out of the box without any mods added. However, I haven't played throught all the game on this computer (few mission played old save)
mangohud %command% --launcher-skip -skipStartScreen

LD_PRELOAD="/usr/lib/libgamemodeauto.so.0" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 gamemoderun %COMMAND% --launcher-skip -skipStartScreen
Way worse performance than on native. Benchmark with optimized graphic settings from pcgamer Windows 10: 95fps Linux: 85fps Setting DLSS from quality to performance made the Proton version on par with windows in the benchmark only! In game however for example, I stood in the Delamain office. Windows: 120fps+ (was capped there, would have gone way higher) Linux: 75fps I also encountered a rare performance regression with no known reproduceable trigger, which led the game to not have more than 64fps no matter what. From inside the main menu: 120/144 -> 80fps Ingame: 90 -> ~50-60fps Graphics card won't went above 50-60% utilization, although it reached nearly 100% before (in this game only, every other game ran as expected). Also unstable frametime. Framerate looks choppier in the rare cases it matches up with the windows version.
May crash after two to five hours
Launch parameters explained: Prevents faulty steam recording library from loading, enables gamemode (which helped me with audio crackling), enables mangohud, disables launcher and breaching screen
works as well as windows would (the bugs are just cus this game is so riddled with bugs).

WINEDLLOVERRIDES="winmm,version=n,b" mangohud gamemoderun %command%
installed d3dcompiler for mods
mods require tinkering

gamemoderun %command% --launcher-skip
DLSS FrameGen causes ghosting/trailing/stuttering. Recommend using FSR3 frame gen as a stop-gap solution until Nvidia cares enough to do something about it.
I'm genuinely unsure what -skipStartScreen does since it absoutely does not skip the CDPR logos and warnings. As such, I wouldn't bother including it.

I have a script that launches MO2, sets proton variables, and MO2 nxm handler
I was able to bring my MO2 modded profile, with around 200 mods, from my Win11 setup straight into Arch Linux. Only had to modify the paths in ModOrganizer.ini and update how some of my core mods were installed as RootBuilder doesn't seem to work well in linux. The performance more or less about the same, maybe a few FPS faster in windows, but definitely worth it to be in Linux!

WINEDLLOVERRIDES="winmm,version=n,b" %command% --launcher-skip --intro-skip -skipStartScreen
Added d3dcompiler_47
and vcrun2022
to default wineprefix
Some minor GPU artifacts noticed during one particular sequence involving a lot of complex transparency effects; large, complex holograms exhibited some checkerboarding when viewed from specific/oblique angles. Otherwise appears flawless per the graphics settings used.
Proton 7.0-6 was playable but did not work with mods. Newer Proton versions (9.0-6, GE 9-25 and Experimental) would start and progress to the main menu fine (after starting the game with 7.0-6 and disabling frame generation in the settings), with mods such as Cyber Engine Tweaks working and accessible from there. However, the game would freeze on loading a save or starting a new game.
It took a near-total descent into madness to realise the reason: recent versions of Proton dropped Vulkan 1.2 support, which is the most recent version my GPU and/or drivers work with. Older versions of Proton (7.0-6) have Vulkan 1.2 support but as mentioned they don't work with mods. Proton-Sarek is a fork of ProtonGE with added support for older Vulkan versions, which runs the game fine and supports mods.
(The protontricks additions and WINEDLLOVERRIDES
launch option are necessary to run mods on any version of Proton, credit to this guide for that.)
mangohud %command% --launcher-skip -skipStartScreen

--launcher-skip
weird thing with dlss is it tanked performance unless raytracing was enabled, So if your hardware isnt well adapted to ray tracing i would just play natively

gamemoderun %command%
Perfecto

gamemoderun %command% --intro-skip -skipStartScreen --launcher-skip
The game started without tinkering but got stuck on the CDPR Logo. But with tinkering I'd say it works as good as it does on Windows 10.
%command% --intro-skip -skipStartScreen --launcher-skip

controller only detected if connected when starting the game
graphics stop for 0.5-1sec every 5-10 minutes
consistently segfaults on exit

Game would crash on initial load when trying to boot Win11 saves. Had to start a new game after switching to Bazzite.
Don't expect prior saves from Win11 to work.

mangohud WINEDLLOVERRIDES="version.dll,winmm.dll,RED4ext.dll=n,b" %command% --intro-skip -skipStartScreen --launcher-skip
Custom Proton: GE-Proton9-26, Set launch options
Did what the guy below me did.

mangohud WINEDLLOVERRIDES="version.dll,winmm.dll,RED4ext.dll=n,b" %command% --intro-skip -skipStartScreen --launcher-skip
Installed vcrun2022 & d3dcompiler_47
After using the browser in Steam overlay, graphics dropped to 20fps. Resetting graphics preset resolved the issue.
Did what the guy below me did.

mangohud WINEDLLOVERRIDES="version.dll,winmm.dll,RED4ext.dll=n,b" %command% --intro-skip -skipStartScreen --launcher-skip
Installed vcrun2022 & d3dcompiler_47
Minor audio crackling in cutscenes, mostly not an issue
Shaders occasionally flickering, unsure if it's a modded problem or vanilla

Unplayable; Game hangs on CD Projekt Red screen and crashes 1-2 minutes later
%command% --intro-skip -skipStartScreen --launcher-skip
Game worked perfectly when I was using Windows 10, but now runs into fatal issues on Kubuntu Linux. I tried every version of proton offered with Steam, as well as TKG proton and GE proton 9-26. I tried all three beta versions of the game too. All result in either not starting at all, or hanging on one of the opening screens and crashing a couple minutes later.
The only exception to this is that I got it to run once with Proton 7.0-6 and launch options specified above, but every attempt to launch the game since then has failed. Is this a new issue or has this been persisting for a while? And does anyone know a solution to this problem?

Simplesmente instalei, abri e rodei. A performance do jogo é maior e mais estável no Linux do que jogando pelo Windows 11, o fullscreen funciona sem erros no Hyprland, não há questões de latência nem nada. Perfeito apenas.

freezes in the main menu
Tried different versions of Proton

Runs out of the box on Steam
Aside of occasional crashes (which I had on Windows as well), I cannot think about any issue with the game. It runs perfect. I haveplayed it on my laptop both on Windows 11 and EndevourOS. I have not noticed any difference. The settings are the same, the performance is amazing

Just doesn't work anymore.
%command% --intro-skip -skipStartScreen --launcher-skip
Hangs after title splash, regardless of any tinkering with command options, config files, or different proton versions. Console output didn't reveal any clues, either.