UnsupportedShow Details
Unknown
Games was running at 14FPS (Native)
Game wasn't starting when using proton
When launching in Game mode, you are unable to interact with the graphics configuration launcher, switching to Desktop mode and launching the game allows you to set your desired options.
My personal configuration was using the "High" graphic preset, setting the Deck to per game profile, disabling the frame limiter and setting refresh rate to 60. I also set up my back buttons for stick clicks and quicksave/load. The total experience on offer was quite comfy.
Sometimes the game crashes after loading a save game.
Played with Proton-Experimental [bleeding-edge] in High settings, 1080p fullscreen with 60 FPS stable.
Just install and play!
To change graphic settings i need to go to desktop mode and then it works
Performance is better on Proton than on native version.
Geralt's hair get stuck during the Kayran fight, reload the game after leaving the area to fix it.
Running fine
No issues so far.
Native Linux version malfunctions, cant start the game properly, need to use Proton
PROTON_USE_WINED3D11=1 %command%
Le jeu en natif n'est qu'en anglais.
Native game is only in english.
TDP - 9
Версия из Steam. Запускаем игру в игровом режиме. В лаунчере можно просто нажать А, игра запустится. Далее - закрываем игру и переходим в режим рабочего стола. Снова запускаем игру, выставляем в лаунчере высокие настройки и выбираем язык. Запускаемся и переключаем управление на геймпад уже в настройках игры. Теперь можно перейти в игровой режим.
Works out of the box
Works very well without any thinkering
Installs and plays well out of the box
The audio would occasionally stutter. This seemed more prevalent during the early game. It was not bad enough to degrade the experience.
Besides the occasional audio stuttering, this game played really well using the latest Proton 9.
During the second mission in act 1, after the conversation with Zoltan and Dandelion, the game crashes.
I'm just starting with Linux, using the Kubuntu distro
40 fps/40 hz
Change controls to gamepad in the control settings.
It worked on my system without any tinkering.
Was unable to run it on Proton, even with options proposed on ProtonDB. But afret installing Steam Linux Runtime works fine.
The Runtime can be installed from Steam "TOOLS" menu.
eval $( echo "%command%" | sed "s/launcher/witcher2/")
you will see a black screen if you open big picture mode . \n you can add the launch option to skip the black screen If you see a black screen.\n the launch option will skip the launcher.
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command%
caused by stutters sometimes while in dialogs and other times in certain locations
Weird box like shadows on shaders, happens sometimes only, might be caused by opengl since I also have observed similar patterns in minecraft java edition when using shaders(oculus/optifine) which also uses opengl
stutters sometimes while in dialogs and other times in certain locations
Works perfectly fine with Standard Proton
Native Version doesn't start.
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command%
8.0-2 works well, Proton Experimental starts the game, but when you start the campaign or tutorial it crashes down.
Low TDP
GOG Windows version installed over Lutris
Text is a bit small but it's readable
A versão nativa não funciona (entra em uma tela preta e fecha) , nem mesmo a versão beta que pode ser acessado também não funciona.
Utilizo o proton GE somente porque é a ultima versão do projeto, utilizar a versão oferecida pela steam flui perfeitamente também.
After the first 10 Hours, in the first city game keeps crashing.
Game was fine for the Intro untill the first city. Then it crashs after some minutes. The time goes down the further i play. After 15 playhours its only 2-5 Minutes. Sometimes even unmounts the data drive. Tried Linux Mint, GE_Proton 7.35 - 7.38, Lutris, Wine.
eval $( echo "%command%" | sed "s/Launcher.exe'.*/bin\/witcher2.exe'/")
- Launch the game FIRST in Steam Deck game mode. Otherwise might risk a "direct3d 9 initialization error"
- Make your changes in the launcher. Click ok
- If you see a black screen just press A on the controller
- Once the game is launched you can exit and then add the launch option to skip the black screen caused by the launcher:
eval $( echo "%command%" | sed "s/Launcher.exe'.*/bin\/witcher2.exe'/") - To add mods:
- Switch to desktop mode
- Place the mod files in the following location:
/home/deck/.local/share/Steam/steamapps/common/witcher 2/CookedPC - Note: might need to enable 'show hidden folders' in file browser to see this folders mentioned.
Small text, can be circumvented by using comfy couch mod.
To use the Steam Deck controller or any external controller you MUST change the control settings to "Gamepad" in the options under the main menu. Otherwise you will load a game and get stuck and forced to restart.
eval $( echo "%command%" | sed "s/Launcher.exe'.*/bin\/witcher2.exe'/")
- In your Steam Deck, switch to Desktop mode.
- Launch The Witcher 2.
- Make change in the Launcher.
- Quit the Launcher.
- Go to your Steam Library, make change in The Witcher 2 launch options.
- Add following launch option: eval $( echo "%command%" | sed "s/Launcher.exe'.*/bin/witcher2.exe'/")
- Save, and then you can bypass the launcher and run the game directly.
Text is too small to read in the game. But mods may help.
MANGOHUD_CONFIG=no_display,vsync=3 mangohud gamemoderun %command%
Great performance, don't bother with the "native" version.
occasional crashes but great game
Game crashes sometimes and upon exiting the game normally, I would get a submit a crash report window, otherwise game is great.
occasional crashes but great experience
Game runs fine but it has occasional crashes. Upon exiting the game normally I get the window for submitting a crash window. Not sure if this is an isolated case for me only but otherwise the game runs great and I am enjoying it so fra :D
Refresh rate set to 40Hz.
When the launcher starts in Steam Deck game mode you will see the black screen and you might think the game crashed. If you press A button the launcher will actually close and start the game properly. After that everything runs perfect.
Also, once you've set the settings during first start you won't be able to access the settings window again outside of desktop mode, as you need to actually see the launcher to select configuration.
Most of the text is very small, but for me at the verge of being readable. The combat log though is just too small. I turned it off in the options, since I couldn't decipher it anyway.
native crashes every 10-30 minutes, freezes for 5-10 seconds after cut sequences. proton has missing backgroun in cut scenes
if I had known this was the tradeoff, I might have gone with proton version. but i'm a bit into the game so don't want to start from scratch. so, i'm stuck with regular crashes and lower performance on native version.
DXVK_FRAME_RATE=60 %command%
If you're gaming on X.Org, the native version of the game runs perfectly. However on Wayland the mouse input is limited to the bounds of the display which makes it impossible to spin the camera in a complete circle. Switching to the Windows version and playing through Proton has no such limitation, and otherwise runs at native speed. I did limit the framerate to 60 FPS because my monitor has a 165Hz refresh rate which seems excessive and runs my graphics card hot. Completely optional, but the launch option I used is listed above
PROTON_USE_D9VK=1 taskset 0x14 %command%
Updating my previous report:
If you have a Ryzen CPU, you might need to pin the game to specific cores to get it to start. I struggled with the Windows version of the game under Proton hanging at the splash screen (the Wolf medallion) until I found this thread:
https://steamcommunity.com/app/20920/discussions/0/1499000547495366770/?l=turkish
Lo and behold, pinning the game to a single core solves the problem and the game loads right up. Unfortunately, a single core wasn't beefy enough to run the game at full frame rate, so I tried pinning it to 2 separate cores (i.e., cores that don't share threads) using the given launch options, and that also worked fine.
So my recommendation is either 0x14 (2 procs: binary 10100) or 0x54 (3 procs: binary 1010100), skipping the first core and every other processor (in /proc/cpuinfo terminology) in case threads aren't all in the latter half of the CPU list. I now get about 110 fps on the listed rig with vsync off and everything else on Ultra.
Why was this worth the trouble? Because the native version of the game is buggy as hell. It mysteriously launches on the wrong head sometimes and frequently crashes. The Windows version is far less buggy. Now my only complaints about the game involve the absolutely awful fighting mechanics and the on-rails world vs. W3.
