ConnivingKhajiit
Published
PROTON_USE_WINED3D=1 %command%
Ran on Windows with 60 fps Medium, 11 fps with Proton at any setting
Sometimes crashed DE, forcing restart
Likely due to my card requiring opengl instead of vulkan, significant instability and artifacts. Sound worked, menus worked, could technically play but you just get a black screen instead of an engine/car in a room. Using mesa_glthread=true or other launch options made things worse.
Sometimes audio is a bit scuffed, its intermittent. Happens infrequently.
Dualshock PS3 Controller detected. Had it on and game tried using it but it didnt work properly.
Consistent CTD after X minutes. Disabling SMT fixed the issue.
For AMD users, you might need to disable SMT (Simultaneous Multi-Threading) if you are experiencing crashing. This solved my issue and made the game playable. I noticed no performance drop with it turned off, and it seemed to use all 16 threads anyways. If I had known about this from the start it would have saved me many hours of trial and error.
Runs really well performance-wise. Sort of. It gets HIGHER fps with ray tracing set to ultra than with it off. Its a bit goofy, especially since my cpu is not bottlenecking. It stays around 50% usage.
I am just running maxed out overdrive settings with FSR set to auto at 1080p. XeSS looks much better but has noticeably worse fps than FSR. I'll probably adjust the settings as time goes on but it runs pretty damn well. As it should of course, CDPR put effort into linux "compatibility".
No mouse capture or windowing issues on Wayland.
Mods were easy to set up with Vortex and worked perfectly. Too bad I purged them in vain during my attempts to fix the crashing.
PROTON_LOG=1 %command% --launcher-skip
Only encountered issues in gameplay:
game doesnt properly close after exiting, causes some window issues until clicking "close" in steam to close some sort of stray process? Really minor issue. Sound is also slightly crackly in some areas noteably those with lots of crowds, goes away after a few seconds. No artifacting whatsoever, except for maybe some lines that appear in fog(?) which might just be my Arc card because I get a similar issue in modded Skyrim. Its so small its negligible and was only noticeable in the Miltech tutorial map. Didnt play around to see what settings caused it, its ignorable.
Experience:
Performance is fantastic, still goofy with settings as before, but 50-60 nearly all the time with ray tracing ultra preset with XeSS Quality. Not always full 60 but more often than not. Frametimes are buttery smooth but zero stuttering which is all that really matters. Overall very impressed. Makes most native clients look like ass! Raytracing is clearly working well and its awesome seeing this tech for the first time.
My dualshock PS3 controller actually works perfectly. I just have to turn it on after the game is running and it understands and maps everything completely fine. Nice to have for driving which Im terrible at.
Dont know why it was crashing holy hell it took a long time to solve it without any understanding but now it works! It was NOT SMT, I did some stuff and broke it and had to figure it out again. I almost thought I had it working after doing some shenanigans with installing VC2022 and D3D Compiler 47... Spent maybe 10 hours total troubleshooting, not normal for me with linux. Guess what the issue was? IDK! But enabling logging through PROTON_LOG=1 solves the crashing! How and wHY? I thought it was SMT at first, then I thought it was the framework mods like CET or red4ext, but when i had a working prefix and game directory backed up and copied over to the steam directory expecting it to work and it doesnt, it all went out the window. New prefix and reinstall didnt work. I tried doing logging again as a last attempt and it fixes it. Might put in a bug report for this one. A good reason to not use linux tbh, hate when this happens. But I hate Bill Gates OS so much more.
Newest patch completely broken
Game no longer launches on current patch. Deleting the wine prefix gets it to work up through character creation (because my previous saves will not work, importing them to new prefix causes crash) until it crashes just before any gameplay. A second launch attempt freezes consistently just before the CD Projekt Red logo. No mods. Bummer. I'm done tinkering.
I just installed and launched. Worked perfectly. Game detected my PS3 controller immediately and I jumped right into my first race with it. Did pretty good until I flipped the car 50 meters before the finish line.
textures distant from spawn do not load, then game eventually crashes
40 fps regardless of graphical settings (except frame scaling)
crashed on certain inputs, like ~ for cheat menu (instant freeze)
same issues, restricted to spawn location
Utilizing AMDGPU driver Game worked perfectly ~1 month ago. I decided to play story again recently and it became unplayable. I tried Proton 5, 6, 7, 8, experimental, GE8-11, GE7-55, GE8-14 and they all had their own share of issues. Sometimes launcher would fail with "steam was not initialized" but if it did manage to launch it would always have the same significant issue of textures refusing to load, then crashing. Might be a memory leak of some sort, the game would often also crash claiming it ran out of memory, which was never actually true. Launch commands for fsync, esycn, radv_perftest, large_address_aware, and heap_delay all did nothing.
Attempts to load main menu, then window resizes, then black screen
Vanilla launches with no issues. Just enable any proton layer (Ive tested 6, 7, 8 and GE) and it just works, as Todd would say.
Sometimes ends up in a weird windowed borderless when launched through steam
Getting mods to work is a violent pain, although Joe McEntire has a great video on youtube about installing MO2. MO2 hates running through wine, although I have only tested using the GE prefix as the installer. However, after much work, I managed to get my old modlist from Windows with ~400 mods running without issues. But it took dozens of hours lol. Also I am running SE 1.5.97 instead of AE. I used the Depot Downloader to downgrade: https://github.com/SteamRE/DepotDownloader End result: Consistent 60 fps performance even with the mods. Actually runs better than my Windows machine did. Oh, and no issues with my hybrid graphics (Dell Laptop)
PROTON_USE_WINED3D=1 mesa_glthread=true %command%
Expected performance from an old card
random crashes upon loading cells. Occurs with mods, does not occur in vanilla.
Vanilla runs perfectly fine, medium graphics profile is about 50-60 fps. Using the same MO2 profile as my laptop (reported earlier) runs like dog from the graphical mods, but this is an old card. No stability issues with wined3d and the radeon driver. However, do NOT use the amdgpu if you have a tahiti card. Although the amdgpu driver supports vulkan, it is unstable and can cause system crashes in and out of games, and actually has worse performance. Worse performance overall due to no overclocking on the radeon driver, this card had good silicon and could go well above 1200 [MHz] on core and 1500 on mem, but is now stuck at 800 and 1250 respectively. Overall a decent experience. Note: Running SE version 1.5.97 Note 2: do not try launcing MO2.exe as a non-steam game with a compatibility tool forced, it will break things (no sounds, no animations, and/or broken saves). Create a shell script to launch it within the SSE prefix and add that .sh as a non steam game. All launch options applied to that non steam game will apply to SSE after MO2 launches it.
Incompatible with older hardware
PROTON_USE_WINED3D=1 mesa_glthread=true %command%
Crashes on load with native client. Vulkan is incompatible with this older card with the radeon driver. The AMDGPU driver is technically compatible but I will not be trying it because it is too unstable and causes system-wide crashes. Proton with vulkan is, naturally, incompatible as well and crashes similarly. Using wineD3D causes it to load into the hanger and run great, but randomly crash at the hanger or when trying to load gameplay. Tried multiple launch options. Sound works at least.
Snail makes excellent linux client
If you have a vulkan capable card, this game runs flawlessly with excellent performance. I run the game at 1080p with fully maxed settings (except no SSAA) with about 80fps. Modes that usually require anticheat on Windows dont on this client, I can play RB just fine.
Heavy artifacting is sincerely annoying. Multi-monitor requires gamescope. No XeSS. Otherwise its a fine client.
SDL_VIDEODRIVER=x11 gamescope -W 1920 -H 1080 -f --force-grab-cursor %command%
Every now and then textures get an awful reflective shimmering effect. Like everything is coated in silver. Randomly starts and stops.
On Multi-Monitor setups it will default to trying to display a stretched resolution across all monitors.
Only game I've experience where GameScope is required on Multi-Monitor setups.
Gamescope is required to play. Otherwise any mouse movement will totally f up the camera. mouse capture must be forced. SDL video driver must be set to x11 on wayland to get steam overlay working on gamescope.
Texture artifacting is heavy. I believe its due to a recent update. Happened on my old RX580 just before I built this new PC, so its not my system(s). It really interferes with gameplay when it happens, but its only maybe a minute max every 5-8 matches or so. The snail has taught me to tolerate pain.
There is an option for XeSS in the graphics settings that does nothing. I most certainly have a card that can do it, but the option is not available. Pretty unfortunate.
Latest version of gamescope does not launch
Game is unplayable on multi-monitor setups using Wayland, as I and many others stated before. Current version of gamescope (3.15.1) will not launch with this game regardless of gamescope options. Renders the game unplayable due to an unfixable mouse binding issue, unless you dont want to actually use the camera.
