
The game worked perfectly using proton 7.0-6. Newer proton versions (including hotfix and experimental) were not working: in popOS hybrid mode, the nvidia GPU was not being used, the game was not running smoothly and the colors were off. In NVIDIA mode the game didn't even launch. With proton 7.0-6 it worked in both hybrid and nvidia mode without any additional tinkering.

Plays like a dream
No isues, no tinker, works perfect on standard install, plays like a dream on Mint, also very good and interesting game.

-windowed -noborder
Some texture pop in and fizzle, but nothing game breaking. Tried different Proton versions and got the same results.
The borderless windowed mode launch option is a must to launch the game at all. For non-Steam Deck users, to change your resolution, be sure to do it in Steam under the Properties > General, as attempting to do it in-game will simply crash the game. Running the game borderless 1920x1080 and ultra quality on an RX7600, expect 40-60FPS, which is fine for this type of genre.

no problems after switching to borderless windowed mode
In fullscreen (default when running the game for the first time) there were heavy black artifacts covering some parts of the screen. Switching to (borderless) windowed mode fixed those and made the whole game playable without any graphical issues.
The game runs smooth.

Tal vez, depende del hardware
El juego es injugable
En mi caso por mi hardware no lo he podido jugar debido a que el rendimiento no es bueno. No lo he probado en Windows aún para tener una comparativa

Tried using Proton, did not work

Works smoothly. -dx12 had quite bad artifacts, but changing the launch option to -dx11 fixed it for me.
gamemoderun bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command% -dx11
Had quite bad artifacts until adding -dx11 in the launch options.

bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command% -dx12
Top Left Quarter/Third area of screen has a constant quick green flicker that only affects characters: Any character in the top left corner will have constantly fickering green-ish skin

-windowed -noborder
The game start in full screen mode with bad resolution witch cause a fatal error message
Need to put some arguments so the game can launch
-windowed -noborder
Nice game

Crashes at the very first loading screen with "Fatal Error" message box. Tried other Proton versions but this seems fundamentally incompatible in mid 2024.
Completed without issues

To enjoy the game with an acceptable performance I need to switch shadow quality from Ultra to High. On top of that, I have to lower the resolution from 3840x2160 to 2560x1440. With Proton-GE, lowering the resolution enables AMD FidelityFX Super Resolution 1.0.

It's great on the SteamDeck , it's pretty good and the performance is flawless, the only time i got 11 fps was at the beggining with the car
I locket my screen to 60 hz and 30 fps for good performance without lag.
It's saying Connection lost and i cant even find a single game hosted by anybody.
Best played with lowest graphics , locking the fps to 30 and hz to 60 for best performance, the game still looks really great.

bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command%
Occastional audio sync issues.
Hair doesn't render very well. There were lots of weird bright spots throughout the game.
Other than the story being painfully slow at times and there being no way to speed up cutscenes without using cheat software, the game was pretty fun. Also if you want to change the ending you have to play the whole game again which takes like 8 hours.
Full play-through, no issues

bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command% -force-vulkan
Had texture problems (like in the character's face) until i switched launch option from "-dx12" to "-force-vulkan". This fixed the texture problems.

Very rare crashes right after save points, but otherwise perfectly playable without any issues.
Crashed twice in 12h, but both times immediately after a chapter transition save point, so no playtime lost.
2K Launcher didn't find the game on first launch, but worked fine on subsequent launches.

Works perfectly out of the box
No issues with the 2k launcher.
Spiel installiert und gespielt. Alles lief bisher ohne Probleme.

Works fine
After installing and updating the launcher, it tells me to lauch the game "wher you bought it (EPIC or Steam". I closed the launcher and started the game again, and now it bypasses the launcher.

bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command%
After installation, the game did not want to launch, so i set the launch options to launch the game directly:
bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command%
The game worked for a few days, then it refused to start. So i removed all launch options and started the game trough the launcher.
Apart from the startup issues everything else ran well.

Game crashed on connecting to a hostes session or on hosting your own.
No remote play together and couch coop is not possible and requires 3rd party apps which do not allow for swapping controllers so remote players can not operate.

bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command%
Played in the default DX12 mode, and did not spot graphical glitches that some previous reports mentioned. The launch option is for skipping the 2K launcher.
On my setup locked the framerate to 30fps for 1440p resolution. Ultra shadow quality completely tanks performance in some parts of the game, so might want to set it to high.
VKD3D_CONFIG=dxr bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command% -dx11
I found artifacts using DX12 - no artifacts in DX11
bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command% -dx11
I used the DX11 option with the command line argument and with that the game runs smooth on high settings. Also I had no audio sync issues.
Requires Proton Experimental for the 2K launcher.
bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command% -dx12
Can't resize text or UI in the game's options, so you might need to use the Steam Deck magifier feature if you have bad eyesight
Minor audio sync issues, but only occasionally. Seems to only happen when the scene cuts from one shot to another
minor LOD pop-in, mostly in fast scenes
- Use the launch options
- Set to low preset
- Cap at 30fps in game settings and in steam
- Vsync on/off didn't make a noticeable difference
- Many report 15-25 FPS in the initial opening scene. I found that it might just be shader cache slowdown. I played through the opening scene once and got the same low FPS dips, but then started a new game again and the FPS stayed very close to 30 at all times. Tested this up to the point where the 2 opening scene characters approach the summer camp.
- The audio sync issue many experience (myself included) in the opening scene did not ocurr again when I played it a second time (as outlined above)
Set FPS litmit to 40
Sometimes I got lags and FPS drop from 40 to 15 or even 10 in dynamic scenes for short period of time like 2-3 seconds.

bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command% -dx11
do not play with dx12 . Severe flickering and artifacts
bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command% -dx12
Not sure if the customized commandline was technically required in this case, but I used it anyway after reading other comments. No problems with it (didn't test without).
No noticeable framedrops. Vsync: on, framerate limit: 30fps, ssao: off, all other graphic settings on low.
UI text is way too small. Subtitles can be resized up to your taste.
bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command% -dx12
Sokmetimes the faces are showing some transparent artifacts.
First run after the installation this game was pretty smooth and I played for fourhours trait without isues. Next day the game would not start, no matter which proton version. After adding the command of running dx12 and using another .exe file, it now starts and runs smooth but with some minor artifacts from time to time.