Ginger
Published
Saw no zombie processes like others reported, game runs and closes just fine. Easily hit over 144 fps at 1080p ultra.
Performance isn't great, but the game does run without tweaks. Main issue I found was minor stuttering along with missing polygons on the protagonist's face.
Just like Black Ops II Multiplayer, Modern Warfare 2, Black Ops 1, etc, the amount the mouse moves per frame seems dependent on the time that frame takes to render. Thus, though the mouse moves in real time, it's more jittery than it should be. Nowhere near as bad as Black Ops 1, it's definitely still very playable, but it is there.
Still a very playable framerate, generally 90-120 FPS, but far lower than on Windows on the same hardware. Seems to be a CPU bind.
Despite the aforementioned performance and input issues, it's still a very playable experience that's close to how it plays on Windows. Players using keyboard and mouse will enjoy.
Mouse stuttering makes it essentially impossible to comfortably play.
Mouse input seemed to be dependent on framerate.
Audio stuttering (incidentally, just like through Wine on macOS). Low framerates as well, but mostly audio issues.
Now that FAudio is integrated into Proton, the audio sounds perfect, with no stutters. Could even qualify for the whitelist.
Before Proton 3.16-4, corefonts installation was required to play. Now, the game runs perfectly out of the box.
Runs perfectly in both OpenGL and Vulkan modes. Slightly lower performance than on Windows, but still above 120 fps in most cases.
Works well
Runs slower than I'd like, but I'm also on an i5-7200U's integrated graphics, so not exactly surprising.
Didn't work on my Intel iGPU, but runs perfectly on my dedicated 940MX. Only issue I had was that fullscreen doesn't work properly and won't alt-tab.
Lower than normal framerates at around 30-35, but that's to be expected when running DOSBox through Wine. Levels run fine, albeit with minor stuttering.
No significant issues
If you tab out and back in while using a controller, keyboard inputs will start displaying instead of controller inputs. While a controller button or stick or trigger is being input, the prompts flash between controller and keyboard every frame. Not game-breaking, but unpleasant.
The prompt thing is annoying, but it's not game-breaking, and it's easy enough to avoid triggering. Otherwise, game works great.
On the new Beyond update, tessellation must be set to Low to run on AMD video cards, as far as I'm aware. This must be done in the config file TKGRAPHICSSETTINGS.MXML, as the game will crash when loading into the world. Once this adjustment has been made, the game runs perfectly, even better than on Windows on the same machine.
Only thing that doesn't work is the cutscenes, of which there was only 1 that I saw within an hour of gameplay, and which can be skipped. Runs above 150fps on my machine, no issues with audio or fullscreen capability.
Mouse stuttering, general stuttering. Crashes occasionally when running 3DMark tests. 3DMark test videos are all black. Freezes when attempting to exit the game.
Rating stars now show up in job criteria. The only remaining issue is that benchmark videos don't play, but literally everything else is 1:1 with the Windows version, no issues whatsoever.
GLQuake and GLQuakeWorld CTD, but everything else runs perfectly with no tweaks required.
Works out of the box with zero issues that I could notice.
Runs perfectly fine out of the box, albeit with less than stellar performance for my hardware. The issue with missing models appears to be gone, as the pod is visible in the in-game intro cutscene.
Takes a couple clicks to get back to fullscreen from alt-tab. It'll attempt to fullscreen a couple times before actually managing to push itself into fullscreen. Windowed mode doesn't work correctly, framerate is incredibly sluggish.
Shadows get a little screwy in some areas, but overall runs pretty well. The opening cinematic did crash for me, but I'm not sure if that's a Proton issue.
