Parzival Wolfram
Published
Does not work out of the box. Cannot determine GPU feature levels, so it errors out due to not seeing a GPU with DX11 support.
Occasionally, audio falls out of sync but the issue fixes itself shortly after.
The fullscreen setting is busted, but switching to windowed mode will immediately switch to working fullscreen. Switching back breaks it again.
Pressing Start in Steam, the game launches, but after a moment, it stops. No window is ever made, no errors or logs generated.
Very, VERY buggy.
Textures are so low resolution that a lot of them are just a solid color.
In fullscreen mode, attempting to exit the game keeps your cursor locked in the (now-frozen) window with no way to unlock it aside from switching to a tty and killing the game.
Trying to pause or open the Codex, etc. takes a very long time, sometimes upwards of 10 minutes on an SSD.
Black screen on launch. I remember this being a bug with the intro on Windows, too...?
Refuses to load OpenXR runtime, stuck on broken calibration menu
Aside from fullscreen issues, works flawlessly.
Alt-Tab sometimes doesn't work at all, and sometimes when it does the game will become 320x200 in the upper-left corner of my monitor when alt-tabbing back in. Both problems are uncommon.
Works fine, aside from a small issue with needing to start SteamVR first.
Start SteamVR first, as this game won't launch it itself, and you won't be able to do anything if you don't.
Crashes on starting a mission or performance test.
Crashes on launch with "Failed to create Direct3D device."
Doom 3 seems to work fine, Doom 1/2 have some sporadic issues
Doom 1/2 generally play like trash, but that's just the Doom 3 versions of the game, that's the intended experience.
Unity remake crashes on startup, DOSBox version works but won't detect controllers.
Most things work... some do not.
"Bete Grise" cannot be started, "Chip's Tips" will not display video properly in-game.
LLVM GPU issues, monitor locked in fullscreen
Proton 5.0-9: GPU listings show as "AMD RADV TONGA (LLVM 10.0.1)" and auto-detect settings are Low, which is nowhere near correct. If launched fullscreen, I have to hop into another TTY to kill it or my primary monitor is rendered useless. If launched windowed, "Gamebryo failed to initialize due to an unknown error." and I can hit OK on the error to quit.
Proton 4.11-13: Detected GPU is of the same family as my actual GPU, but is not the same model (detected as R9 285, and not an R9 380.) Auto-detect settings are High, which is correct. On launch, game hangs in either Windowed or Fullscreen.
Works ALMOST flawlessly. Almost. There are very, very rare hiccups, and I think it has a very slow memory leak?
Very rarely, on game startup, the amdgpu driver will die and take the rest of the system out with it. This ONLY happens when starting this game.
Single-player is flawless. Multiplayer is locked because of EAC.
Only first logical monitor usable.
Requires using Proton Next or Experimental to play. No launch flags required.
Game will not start more than once per Steam launch. Exiting and re-launching Steam fixes this temporarily.
Remake only works in stock Wine, not Proton. Start "winsetup.exe" instead of the game's normal executable.
Game bad. Proton good.
Trees are sometimes translucent, letting you see geometry behind them.
Fullscreen scaling is very bad.
Transitioning between full screen and windowed with F4 crashes, but starting in either mode works fine.
Other than inconsistencies with window dancing, works fine.
During level(s) with window dance, XFCE4 will move the window and such, but if other windows are present, or you have multiple monitors, the game sometimes comes back to the front without properly retaking focus, so suddenly inputs stop registering.
Works OUT OF THE BOX on Proton 6.3-4!
Minor audio crackling, not loud but slightly annoying
Using Proton Experimental, edited CheckDriver.lua to set gfx_iRequireDriverVersion
to 1000, and set sfx_strAPI = "OpenAL";
and gfx_strAPI = "Vulkan";
in UserCfg.lua (These work on AMD mesa only! See details for Nvidia and non-Mesa AMD drivers at https://github.com/ValveSoftware/Proton/issues/4218#issuecomment-706674259)
Rarely, controller would stop working despite button prompt changing accordingly. Unplugging the controller, waiting 5 seconds, and replugging controller fixes this.
I can max everything out on my 5500XT and still run it at 60FPS, which is much better than most people's experience on Windows with a 5700XT!
-skipintro
Installed dotnet46
via protontricks/winetricks
With default Wine mono package, performance would dip to ~17% sim speed as the game reported using 600%+ CPU time in multiple categories. With dotnet46
installed via protontricks/winetricks, the game runs fine, but is unstable.
With dotnet46
installed, the game crashes within an hour of loading into a map with a message stating something like "Your graphics driver has crashed." The game's logs state the game segfaulted.
Online multiplayer works well enough, despite all the other experienced issues.
It comes down to a choice between bad performance or annoying crashing, it seems. The game's not unplayable at 13% simulation speed, but it's certainly annoying. Meanwhile, the game can be tinkered with to fix performance, but you'll be reloading the game very often due to crashes, which can take forever even with a mostly empty map and no mods.
Occasionally, the mouse would be locked into a smaller window size than the game was actually running at. Closing and reopening the game fixes this.
I'm getting something like 30% better performance on Proton due to DXVK. YMMV, but it's nice.
Voices and some music is missing. Sometimes footsteps aren't audible, but this is infrequent.
Occasionally, when alt-tabbing out of the game then back in, I have to re-do the process as the Alt and Tab buttons don't work. Alt-tabbing out and back in fixes this.
Multiple mismatched-size monitors, first physical monitor was used as display but with the resolution options and aspect ratio of my set-primary monitor.
Inputs occasionally dropped or fired late, not constant, just occasional.