giantplaceholder
Published
Runs almost flawlessly. Most of the issues I've seen were related to the game itself, not the Proton\Steam.
PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 VKD3D_FEATURE_LEVEL=12_1 gamemoderun %command%
Very rare crashes due to loss of Vulkan device. Probably thrice in 100+ hours.
Running GOG version as a non-Steam game.
Runs perfectly fine as it is. The only tinkering that required is an exposure of NVAPI to allow the game usage of DLSS. Otherwise, zero tweaks were made, apart from my "default" usage of Feral's gamemoderun -- but please note that it is NOT REQUIRED, just my own snake oil of config.
Performance is on par with Windows -- at least in case of using Vulkan renderer. Haven't tested what's going on with DX11 version, couldn't care less to be honest.
Finally works out of the box. EA app is still a pile of steaming shit, but it manages to launch now and not break everything.
Drops from fullscreen to MATE desktop every time there's a native MATE notification
Choppy frametimes, but otherwise, no slowness
Tried connecting to random open lobby and play a few challenges. Just works, nothing to add.
Works fine, but EA App is once again breaks stuff OOtB. You'll have to edit config file, otherwise you won't be able to launch the game.
EA App's overlay always crashes the game during game's launch
This is a second report from me.
EA's launcher app still sucks balls. This borked piece of software is breaking the games again: previously it was working OOtB (April 2024), and now (July 2024) it's effed again, because the launcher's overlay manages to crash the game every single time.
You won't be able to disable the overlay in GUI of the launcher, so you'll have to:
- Launch the game as is and let it crash
- Locate the .ini config file (for default configurations, it's located at ~/.steam/steam/steamapps/compatdata/1238080/pfx/drive_c/users/steamuser/AppData/Local/Electronic Arts/EA Desktop) - file's name starts with "user_".
- Append "user.igoenabled=0" (without quotes) entry at the bottom of the file
- Run the game again
Otherwise, the game is fully playable without any issues, recognizes the Xbox-like controllers and online is working too. It's just EA launcher that breaks stuff.
Everything above is applicable to the Steam Deck as well - the only extra step is that you'll have to switch to desktop mode in order to edit the file.
Runs quite nicely: ~50-55 FPS @ UWHD with highest settings and RT enabled, DLSS on quality preset (highest internal render res available)
6.19-GE-2 GloriousEggroll
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/6.19-GE-2
Had to manually remove game's Proton prefix due to Proton-GE update, but otherwise, launched without a hitch. DLSS and raytracing should be available in the game's settings once the following launch options are used: PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr %command% -dx12
Played through the initial few chapters, plays quite normally -- didn't see any specific graphical or sound glitches. Never ran this game under Windows, so can't compare the performance I'm getting against it, but I'm okay with what I've ended up with.
50 to 55 FPS @ 2560x1080 b\w DLSS, with decent frame latency, most of the settings set to Ultra. Raytracing is broken as of now.
6.21-GE-2 GloriousEggroll
Got DLSS working with Proton-6.21-GE-2.
Proton-7.0rc3-GE-1 is a no-go: DLSS option in graphics settings stays grayed out.
Running along with MangoHud like this:
mangohud VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command% --launcher-skip -skipStartScreen
The last two options allow to skip launcher and one of the two videos before the main menu.
Don't bother trying to tinker around enabling raytracing, as DXR is not able to support the game yet. Will either crash or run as dogshit.
Very slight stutters with raytracing's enabled and a lot of light-casting objects quickly move into the frame. Even with FSR on "Balanced" and UWFHD, these are unexpected with that GPU.
Given an appropriate hardware, in rasterized mode in runs just as good as in Windows.
Raytracing may introduce the aforementioned hiccups at times, and path tracing is a no go even with my GPU and FSR, even though on Windows it runs decent.
Played the game mostly on Linux, all 400+ hrs of it, had a few random crashes throughout the years, but overall, pretty good experience, no game-breaking stuff at all.
Proton-6.19-GE-2 -- runs perfectly fine: UWHD @ 75 FPS capped with DLSS on quality preset and raytracing.
6.19-GE-2 GloriousEggroll
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/6.19-GE-2
Sometimes I had to change resolution to non-native and back to get rid of black bars on the sides of the screen. Can't really determine whether it's one-off thing tied to changing Proton version, or something systemic.
Nothing to add, really. Runs buttery smooth, without any crashes, stability issues or anything else, besides aforementioned screen crop. Nothing major or game-breaking. DLSS and RT are working without any issues as well: I've just installed latest stable proprietary drivers, and swapped the Proton version in favor to GE instead of Valve's experimental.
30 FPS cap, 5 watts cap
Works absolutely brilliantly out of the box, with zero tweaks, both on Deck and my Arch desktop.
Performance on the Deck is passable, 30 FPS locked with 5 W power. No stutters, artifacts or anything of this sort. Settings are set to medium with native res.
Works better than native versions of DiRT4 and DiRT Rally
Performance-wise, it runs almost buttery smooth on hybrid preset (somewhere between medium and high). Can't play in modes other than custom championship, Dirtfish skidpad and time attack. Career mode is blocked due to the fact that Codemasters' custom CA is required to make a TLS connection to their RaceNet system.
A lot of people here suggest to just install CA into the system and they even provide the snippets and CA file itself.
Well, don't do that. Ever. Certificate source is questionable at best, and you don't want god-knows-sourced-where CA in your system -- it is a huge security breach.
It just works OOtB.
Works out of the box, with default Proton.
The only two things are cosmetic ones and look odd:
- Launcher's sound might be borked at times (or a separate window might appear, trying to play a .wma file containing sound)
- The game DLC activation is effed: the game will try to ask you for the DLC CD key, and Steam no longer provides CD keys for this DLC. Just ignore this, close the installer and the game will launch.
Works OK I guess, mods can be installed and managed relatively simple, but tinkering is required
bash -c 'exec "${@/Fallout4Launcher.exe/'MO2/ModOrganizer.exe'}"' -- %command%
Had to uise protontricks-launch in order to install Mod Organizer 2 (details are below)
Noticeable stutters in busy areas like Diamond City's Market
I have a 21:9 display (i.e., 2560x1080), so I had to install an ultra-wide mod to allow support for such aspect ratio. Since the easiest way to install it is Mod Organizer application, I had to install it as well.
Here's what I did:
- Installed the game as usual, ran it once and closed
- Launched the Mod Organizer setup file via protontricks-launch:
protontricks-launch --appid ModOrganizerSetup.exe - Configured the installation in a way so Mod Organizer would be installed WITHIN the directory of the game in a subfolder (i.e.,
[...]/steamapps/common/Fallout 4/MO2) - Then I installed F4SE as usual as well as some other native code mods (namely, achievement enabler)
- After that, you need to adjust the launch command in the same fashion as mentioned above
- Now you can launch the game as usual via button in Steam library, and MO2 will launch normally. Now you can install the mods that you need.
You can select whether you want to launch the game itself via default launcher, F4SE or what have you. Achievements and overlay will work normally.
Ultra-widescreen resolutions are not working properly (horizontal stretching, HUD issues, etc)
Had to use SteamTinkerLaunch to run FlawlessWidescreen before the game itself (see this page on how to set it up). Without it, 21:9 resolutions are borked: subtitles, HUD, controls and pop-ups are cropped.
Game is to 30 FPS by default (Xbox 360 legacy), but there's an option to switch to 60 FPS lock. Note: you'll have to access game's settings menu once you've already loaded a level, this option is NOT accessible from the main menu.
Occasional stutters when entering\leaving new areas (i.e. exiting or entering buildings, fast driving, etc)
Custom launch parameters: PROTON_USE_WINED3D=1 %command% -nomemrestrict -norestrictions -percentvidmem 100 -availablevidmem 3072 -noprecache -novblank (where 3072 is amount of VRAM on my video card).
Thankfully, it now launches on Ryzen II CPUs at all. Otherwise, the same experience I had with GFWL version. Old saves from GFWL were imported by Rockstar Launcher on the first run.
Proton-6.19-GE-2: UWHD caped @ 75 FPS, FXAA+4xMSAA, "soft" shadows and "medium" tesselation, all other settings @ highest available preset
6.19-GE-2 GloriousEggroll
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/6.19-GE-2
No stability or performance tweaks were applied, except for switching to Proton-GE. Frame rate is more or less stable (65 to 75 FPS with vsync enabled), but not perfect, with occasional stutter here and there. Honestly, for all I know, they might be caused by a storage device -- I'm launching the game off the HDD.
--
Rockstar's bloatw^W Launcher seems to be calm at the moment, and not causing any extra issues, like it used to. Online is playable, performance hit is around 10-15% -- not great, but salvageable. Might have to lower the graphical settings, though.
--
All in all, playable and enjoyable. You may have to fine-tune game's settings to find that performance sweet spot.
Refuses to display anything unless D9VK is enforced. Was unable to get gamepad working. XLiveless (https://github.com/AccountOneOff/lutris_files/raw/master/xlive.dll) is a must. Generally is playable, with a bit of stuttering occurring while shaders are being built: was able to get around 40-45 fps with everything maxed out.
Borked as in "won't even run the launcher" on all of the Zen 2 chips (Ryzen 3xxx).
Currently opened issue for Proton: https://github.com/ValveSoftware/Proton/issues/350
MANGOHUD=1 MANGOHUD_CONFIG=cpu_temp,cpu_power,gpu_name,gpu_temp,gpu_core_clock,gpu_power,ram,vram,swap,histogram PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr gamemoderun %command%
Stutters and streaming issues
Please note: I'm running an EGS version as a non-Steam game.
Had to adjust VRAM streaming settings to avoid constant stutters due to VKD3D constantly running into OoM issues (see this Reddit post for details). I guess 8 gigs of VRAM is not enough these days for a HP game these days (sarcasm).
Game absolutely HAD to be moved to the SSD: performance is horrible when it was located on SMR hard drive, and initial load time was over three minutes.
With that taken care of, performance with "High" preset, DLSS Quality and 2560x1080 is passable: anywhere from 45-55 FPS up to 120+ FPS, depending on the scene, amount of characters within your view, effects and so on. Not an ideal case, but I can live with that. Comined with that tweak from Reddit, VRAM consumption stabilizes around 7.2-7.5 gigs, with no noticeable stutters.
Just for the context: I have this game running on the second computer in my house (FX-8350, RTX 2060 Super, 16 gigs of DDR3, runs off a 10 y.o. CMR Toshiba HDD), but under Windows 10. On that config, with "Medium" preset, DLSS quality and 1080p, it spews out stable 50-60 FPS, depending on the scene. Make of that what you will.
TLDR: runs more or less fine, with some tweaks applied. High-end rig with more than 8 gigs of VRAM is required for high quality presets and anything higher than 1080p. SSD is a must.
Moderate crackling during unskippable intros. No crackling in-game.
Missing textures with RADV on Mesa OOtB. "Sort of" fix: https://gitlab.freedesktop.org/mesa/mesa/-/commit/c2f8f20ef75a00917a652e32d4caa48029c68681
Mouse pointer is buggy after alt-tabbing and is not going away, sticking to the center of the screen.
The game does not run on RADV right now without manual tweaking (see above). After that it runs correctly, sans the issue with the pointer (which is most likely caused by KDE rather than driver), but the performance is average at best. NOTE: this manual fix is not required at the time of writing this if you're running mesa-git.
In contrast, the game runs wonderfully via AMDVLK (Arch packages: amdvlk & lib32-amdvlk), but it has to be invoked manually through env variables like this:
DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 %command%
Performance overall is very good: 110-120 FPS on "Supreme" preset without any upscaling using 2560x1080 resolution. Apart from that mouse pointer issue there are no graphical artifacts when using amdvlk.
Game is very stable: I've yet to see a single crash after 8+ hours of playing it. YMMV with NVIDIA though, as I've heard that performance and stability right now are abysmal over at the green camp.
Runs somewhat decent, but plaugued with random stutters and frame drops. 2K Launcher is borked, so you'll to use launch option to bypass it
eval $(echo "%command%" | sed "s/2KLauncher\/LauncherPatcher.exe'.*/pc\/Mafia II Definitive Edition.exe'/")
Occassional stutters, sometimes framerate drops down to 18-25 FPS during intense action scenes with lots of particles (i.e., debris from firing, shells, chunks of the walls, etc)
Launch option should be used to bypass borked 2K Launcher. Without it, chances are you won't be able to run the game. Performance is suprisingly rough, given the hardware and the age of the game.
No noticeable performance issues, but the fullscreen is borked. The only viable option is to play in window, which is less than ideal
eval $(echo "WINE_FULLSCREEN_FSR=0 DXVK_ASYNC=1 mangohud %command%" | sed "s/2KLauncher\/LauncherPatcher.exe'.*/Mafia3DefinitiveEdition.exe'/")
Won't go back to fullscreen after Alt-Tab, had to kill off the Proton process. After re-launch, won't go back to the fullscreen properly -- will display black screen instead.
2K Launcher is broken, once again, and won't start after its initial launch and update. You'll have either remove it every time you launch the game or use the launch options above to bypass it altogether.
The game itself runs more or less fine, but fullscreen is broken, too. The game launches okay initially, and runs pretty much OK, but on its second launch it'll refuse to start properly, displaying only a black blank screen. Your only options here are to either wipe the prefix, or manually edit the configuration file to enable windowed mode.
Unlike Mafia I DE, there's no option for borderless windowed mode, so you'll have to either ignore your DE's window bars and other elements eating away at your game's real estate, or wipe the prefix every time you'd like to play.
Custom launch settings are must to avoid issues with 2K Launcher. No issues with stability other than sometimes-broken-fullscreen.
eval $(echo "%command%" | sed "s/2KLauncher\/LauncherPatcher.exe'.*/mafiadefinitiveedition.exe'/")
Sometimes fullscreen defaults to windowed, not even borderless. Most often than not, it depends on whether the game has been exited properly.
2K Launcher shipped with the game launches the game okay out of the box BUT asks to update itself. Once you'll do that, it won't launch properly again, and you'll be forced to clean up the prefix. The launch command above allows to bypass the launcher completely, with no damage to performance, stability. Cloud saves work as well, with no issues or additional tinkering. Performance is solid, with over 120 FPS with my hardware, assuming that V-Sync is off. Ran it capped at 75 FPS most of the time, no issues with frame drops or unexpected stutters.
The only issue I've encountered is that when game is terminated abnormally, it will refuse to start full-screen. Every time I tried to force it back to full screen from settings, it froze. Resolved it with wiping out the prefix and properly terminating the game since then.
Works fine, but one must enable Proton Experimental, otherwise you won't be able to log in into this god-awful EA app.
Occasional stutters with or without Feral's gamemoderun
Performance is not great, given the hardware. Need to test more with async-enabled DXVK.
Must switch to Proton Experimental or GE-Proton to work your way around EA app issue. Doesn't work with latest default Proton at the moment.
DXVK_ASYNC=1 gamemoderun %command%
Alt-Tab is problematic, sometimes leaves partially corrupted image at the center of the screen. Fixable via selecting a few of the other opened windows, by mouse.
Even with Feral's gamemoderun, the game still stutters a bit, especially on graphically challenging worlds, such as Virmire. Given the hardware I'm running, this is unexpected, but I guess this is more of an issue of the game itself rather the Proton.
dxvk-async is not providing any meaningful difference in performance, at least in my case.
I guess your best bet on similar hardware would be to frame-lock the game to 60 or 75 frames per second. This have given me the least amount of stutters. Plus, the game has the bug where shields stop working when frame rate is over 120+, so you should do this in any case.
dinput8.dll override to native is required (details below)
Mouse pointer was present outside of the game menus, introducing heavy stuttering when panning the camera.
First and foremost - EA launcher app still sucks balls. I've played this game on Proton 7.0-5 a year and a half ago, so EA app was installed and launched without any issues. Now (June 2024) it simply refused to launch on that or any other version of the Proton until I removed the prefix in the compatdata. Then and only then EA app installed properly and allowed me to launch the game.
This is not specific to Andromeda itself: I had the same issue with ME Legendary and Burnout Paradise. It's just that EA app is still a horrible piece of software.
With that resolved, I was able to continue with my older saves, but unfortunately I've encountered a strange bug where mouse pointer would stay on the screen after navigating game menues or overlays (like reading a journal or opening a container). Afterwards the pointer stayed on the screen dead in the center, and every time I tried to move the camera with mouse, I've experienced heavy stuttering.
Although pointer was gone after an Alt-Tab, it would return after the next menu interaction, so I had to use this mod in order to fix this.
You'll need to copy dinput8.dll into the game's root directory (the one where MassEffectAndromeda.exe is located), and after that launch protontricks --gui, select the Andromeda's appid (123800), launch winecfg, and set up a manual override for dinput8.dll ("Native, than built-in").
The same can be achieved by launching the game with this launch options command: WINEDLLOVERRIDES="dinput8=n,b" %command%
To be perfectly clear, this is a long-standing bug of the game itself, but I've never experienced it with Proton. Maybe it's GPU-dependent, maybe it's something else. In any event, this fix does the job.
Performance-wise, everything is top-notch (over 150 FPS on all-ultra @ UWFHD), which is to be expected, considering my hardware and the game's age.
You'll need to use either Proton Experimental or GE-Proton to get past EA laucncher, which is borked at the latest available stable Proton. Otherwise, no tweeks were needed in my case.
Works perfectly fine -- as far as I can tell
Runs without any hitch. Load times probably could've been a bit shorter, but otherwise, a very enjoyable experience. Stable 75+ FPS on highest available settings minus MSAA. No glitches, no sound stuttering or any other stability issues.
6.19-GE-2 GloriousEggroll
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/6.19-GE-2
Pretty much nothing to add to my previous report from a year ago. Updated Proton version to newer GE fork, to try and use DLSS -- works absolutely fine, with or without it. Personally, I chose to use DLSS because my hardware is not able to provide good frametimes at ultra settings without it. When enabled, it's buttery smooth.
No other issues whatsoever.
Runs out of box. If you're playing on a decent enough hardware, you should be okay.
Some lightning effect during the storm might look distorted.
It is possible to switch to desktop using Alt-Tab, but on return, you won't see anything except black screen, and you'll have to kill the process.
Runs with relatively small random stutters, with an average FPS of 50-55 on my config. It's a bit uncomfortable (and certainly not buttery smooth), but playable. Given that my video card, the infamous 1063, is not the best card to run Vulkan apps to begin with, game behaves and performs better than I've expected. Controller (Dualshock 4) works fine with an Xbox mapping, force feedback works as well.
50-55 FPS @ 2560x1080 (mix of high and ultra) with DLSS, or 40-48 FPS without DLSS. Runs good enough to forget about dual boot.
6.21-GE-2 GloriousEggroll
6.21-GE-2 GloriousEggroll
Used the following launch options to enable DLSS:
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command%
Around 50-55 FPS with DLSS enabled (quality preset), or 40-48 FPS without DLSS. To be honest, DLSS implementation in this game is not great, so I personally wouldn't bother.
Rockstar Launcher behaved that time and didn't break anything on its own.
Fullscreen mode switches to windowed sometimes when changing graphics settings here and there. You'll have to switch the resolution and set it again to fullscreen to fix.
Fullscreen works properly only with 4:3, 16:10 and 16:9 resolutions. WFHD and higher break the cutscenes and partially break the game menu.
This is a report for GOG 1.1.1.0 version, which is equivalent for whatever's up in Steam right now, minus the DRM.
The game FINALLY is out of the woods of the multilib issues which have been plaguing its existence pretty much from the very beginning.
With custom protonified Wine-Tkg-Staging build, I was finally able to view all the cutscenes (encoded with proprietary Windows Media video codec) without ANY kind of modifications to the game, and without installing 32-bit verbs of the gstreamer0.10
The only thing that's required from the user is to install gstreamer-bad and gstreamer-ugly in the system. Apart from that and the custom Wine build, the experience is finally hassle-free.
Here's hoping that Valve will backport that WoW64 support into Proton soon, and will enable it by default.
Linux native build is outdated which breaks the multiplayer when host is running Windows. Had to use Proton to run Windows build of the game
eval $(echo "%command%" | sed "s/2KLauncher\/LauncherPatcher.exe'.*/Base\/Binaries\/Win64Steam\/CivilizationVI.exe'/")
Linux & MacOS native builds are a couple of versions behind Windows release. You'll have to either run Windows version via Proton or make whomever you're going to play online to downgrade their version via "Beta" tab
If you want to do that, use ineedlegacyaccess code to access previous build (see https://www.reddit.com/r/civ6/comments/zn295y/civ_6_multiplayer_not_working for details)
As for performance under Proton -- rock solid @ 2560x1080 at my rig, unlike the native build, with all of the settings cranked to the max. No issues stability issues apart from being unable to Alt-Tab properly, had to escape to the different desktop.
The launch options are MUST in order to get past 2K Launcher which is borked after its recent updates. Otherwise you won't be able to launch the game at all.
This game is 18 years old and it doesn't really run on modern Windows anymore as well. All of the issues are stemming mostly from its age.
Intro videos are not being displayed properly: no picture, only audio is played.
Crashes randomly, have not been able to figure out any kind of prevalent reason.
Cyrillic input (i.e. Russian) is not working unless "LANG=ru_RU.utf8 %command%" is set as a launch option.
Pretty much the same behavior as on Windows. Animation may stutter without PROTON_USE_D9VK, which is something caused by the age of the game and the quirkiness of WINE's default DirectX9-to-OpenGL translator. Planetary battles, arcade battles and text quests all work without a hitch. Game automatically detects that it's being launched under WINE\Proton, and tweaks the rest of the settings to run properly by itself.
35 FPS lock, 6 watts TDP lock
Default font size is quite small for Deck's resolution and display's physical size combo. With that said, there's a toggle for font size in game's settings (accessible via game's UI).
Control scheme is a bit funky, but no more funky that that of Worms Armageddon (which is, in my opinion, less intuitive).
Performance is perfectly acceptable for 2D mode. I haven't tried 3D (planetary battles) mode at all, but it is fully optional. There are frame time spikes, a lot of them, but given the game's gameplay nature, they do not distract or ruin the experience.
Battery life is projected to be around 8 to 9 hours with the with aforementioned FPS and TDP lock.
On first launch, game will detect that you're launching it via Proton, and will mention a few details regarding such configuration which may be of note for you.
TLDR: experience is quite nice, given the game's age and technology stack.
Doesn't crash anymore when loading a game, but NVIDIA drivers are still half-baked. Performance is barely passable.
Randomly crashes every 15-45 minutes.
You absolutely have to install 545.43.10 driver, otherwise you won't be able to run the game properly. Still suffers from NVIDIA's issues with VK_NV_device_generated_commands_compute. Currently vkd3d solves this with a workaround which causes a huge performance penalty.
I barely see 40 FPS around starting locations, using default "High" preset, with no modifications whatsoever, and running 2560x1080 res. I would imagine that later locations will perform even worse.
Starts and runs OK with NVIDIA h\w now, can be considered playable with some caveats (please read below in full)
Game has to be alt-tabbed to proceed normally with launch. Otherwise, the image will be frozen.
FPS is about 2\3 of what I'm seeing with the same exact hardware on Windows.
Crashes are minimal at the moment of writing this, but they do happen. Most likely to happen during saved game load.
I'm running forced Proton Experimental (switched to bleeding edge branch). NVIDIA's 545.29.06 driver is a MUST -- it is the only version of the driver which partially resolves issues with very erratic frame times.
PLEASE NOTE: as of Jan 24 2024, you really have to use this exact driver version in order to squeeze all of the performance your hardware has to offer. All other driver versions of the 525, 535, 545 and 550 branches will have lower performance and significant issues with frame times -- as in, you'll see way more stutters.
Performance, as noted above, is lower than on Windows by at least 30%: with settings at all-high, DLSS quality and 2560x1080, I'm getting about 35-55 FPS on average, with occasional dips in high twenties. On Windows, I've never seen less than 55 FPS with the same exact settings, with buttery smooth frame times.
All in all, NVIDIA has screwed the users once again with the quality of the drivers and quality (or lack thereof) of customer support. The way how they have handled Linux users' reports regarding this game (i.e., game was nearly unplayable for month and a half) was a final nail in the coffin for me personally. My next card will be from AMD, and I'm suggesting for you to consider the same if you're in the market and serious about playing games on Linux further on.
Still requires a lot of dances to run properly on NVIDIA GPUs. Frame pacing and stability on AMD are so much better that I partially blame this rehash of Falllout 4 for my move to Team Red after 11 years with NVIDIA.
Given the hardware I run it on, with everything set on ultra and without upscaling, I'm hitting vsync limit, which is "good enough" for me.
Works pretty much out of the box if we're not considering a fix for Pulseaudio latency. Steady 60 fps on all-high, 25-40 fps on all-ultra.
Custom configuration for sound stuttering issues: WINEDLLOVERRIDES="xaudio2_7=n,b" PULSE_LATENCY_MSEC=90 %command%
Native version runs OOtB, zero issues whatsoever
Decided to finish my abandoned 2015 save after finishing TTP2.
Installed native version, applied zero tweaks - just pressed "Launch". My original saves from nine years ago loaded from Steam Cloud without any hitch, was able to continue the game.
Zero performance issues, stutters, no glitches, artifacts or anything else.
Now this is how you make a native Linux port.
Works pretty much OOtB. First UE5 game in my experience to not have any traversal stutters.
Never ran it on Windows, but I imagine that it runs pretty much the same. No graphical glitches, no hiccups or stutters, absolutely no crashes. Cooks the shit out of the GPU though, more so than Cyberpunk 2077 does.
Should work on any relatively recent hardware and distro with no issues.
Pretty much broken as of Nextgen update. Works only on Proton Experimental on bleeding-edge branch
https://www.reddit.com/r/linux_gaming/comments/zlce6o/witcher_3_nextgen_update_just_dropped/j06iu4i/
Tested only DX12 mode.
Hangs immediately after launcher unless you are using Proton Experimental on bleeding-edge branch, whch has to be enabled manually, see details here: https://www.reddit.com/r/linux_gaming/comments/zlce6o/witcher_3_nextgen_update_just_dropped/j0715xl
Runs at more or less 75 FPS when capped, with occasional spikes here and there. Had to disable Hairworks and RT altogether. Hairworks requires now-missing from the game's shipment d3dcompiler_47, and crashes DX12 mode, but according to Reddit, kind of works in DX11 mode. RT breaks the game completely, dropping framerate to less than 1 FPS per second, no matter which of RT options you've enabled.
DLSS seems to be working fine, if exposed thru PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 VKD3D_FEATURE_LEVEL=12_1 launch options.
Works straight out of the box. No tweaks were required for my config.
Played entire deathmatch campaing without any issues whatsoever. Played on WormNet a bit, works just as well. Game itself since 2010 ships with some tweaks and settings designed to improve Wine\Proton compatibility.
All of the features, like switching from window to fullscreen, minimizing, etc -- everything works just as it's supposed to on Windows.
