Techbane
Published
Generally fine, somewhat unstable.
At baseline, the game crashes at seemingly completely arbitrary intervals maybe once every couple hours. Autosaves and fast-forward make this a non-issue in most cases, with one exception: one particular character's Somnium (PSYNCIN' IN THE MaiN) is horrifically unstable and tends to crash every minute or two, making it difficult to even get through certain cutscenes before the game crashes again. Could not find any tweaks to ameliorate this.
Seems to detect gamepads but not allow mapping or using them. Otherwise works as well as this port has ever worked.
Using the GOG version: doesn't seem to detect controllers properly through Steam (and keyboard binds are unbindable and awful), but works well through Lutris. Always takes about 8 seconds for the title screen to first detect input, but works fine after. Performance is decent, although the game hangs up a lot whenever it has to build shaders (when a new character or enemy shows up, or during almost any new screen transition). Borderless Fullscreen seems to have best performance. Won't let you alt-tab properly, but doesn't choke and die if you attempt it. Having Esync enabled is possibly slightly better than disabled, but messing with D3D11 tweaks just seems to break lighting. Crashes very occasionally.
PROTON_NO_D3D11=1 PROTON_NO_D3D10=1 %command%
You need to disable DX10 and DX11 to get the game to not launch to a black screen, after which you can go into the settings and change the renderer to DX9 or OpenGL and remove the launch option. OpenGL runs much more smoothly but seems to lose some of the fancier lighting effects.
Works fine out of the box with Proton 5.13-1
Occasional stuttering when changing music tracks or playing certain SFX
Works OOTB, no configuration needed. Did not try multiplayer.
There is one stage towards the end of the story mode where the audio just horribly broke halfway through, to the point of causing the subtitles to not progress. Some dialogue was missed altogether, but after reaching the next stage it returned to normal.
The dev is specifically building the game around Wine compatibility, so issues in general play seem to be few to none. That said, the game only runs fullscreen for me and attempting to alt-tab out of it has completely taken away control of the system every time I've tried, requiring a force-kill via emergency shell to recover things (which destroys the current run in the process). Make sure you're able to give the game your full and undivided attention before beginning.
Works fine OOTB
Only slight problem is it seems to hang on exit in a weird way that can hijack your mouse clicks until the process is terminated.
All volumetric smoke effects look like a mosaic censor effect with certain versions of Proton.
Entire game halts frequently and randomly. Once I managed to get an uninterrupted ~40 minutes, but more often than not I can't even get past the main menu to load the game.
Tried many versions of Proton and GE, and several launch tweaks. Could not get the game into an acceptably stable state.
Cutscenes can get extremely jittery when trying to load geometry. Performance is otherwise pristine.
Game freezes without warning maybe once every hour or two. Autosave is not particularly reliable. If you're in the middle of a really long trek or just pulled off something tricky and have a minute to breathe, go into the menu and SAVE MANUALLY.
Doesn't do very well on OpenGL, fares better after setting the renderer to Vulkan in-game. Still performs a little worse than native Windows, but no noticeable major hangups or graphical issues. Does sometimes go aggressively unresponsive when alt-tabbing or changing resolution.
The biggest problem with the Linux version of DC is it's dependant on a build of GLIBC that needs to be custom built in a pocket install to work on Ubuntu 18.04 (and any distros relying on that). There's a guide to getting it working: https://steamcommunity.com/sharedfiles/filedetails/?id=2227934399 but in my case even after going through all the steps the game still crashes with a generic segfault. I have no alternative but to run it under Proton, which incurs noticeable crackling in the audio because of too short a buffer which I'm not sure how to fix.
Can't even get through the install process to try using Proton
Game is permanently stuck on the first-time setup phase, installing DirectX (step 3 of 3). The Steam library page displays "Launching - Running install script (Microsoft DirectX for Windows)", but it flickers irregularly, seemingly hitting some sort of failstate and silently relaunching itself but without ever spitting out an error or halting the install process.
Displays an oddly grey and featureless off-center logo, then a black screen. Same problem on both Steam and Lutris. No amount of launch configuration seems to change anything.
Audio doesn't work at all, and cutscenes either don't play or crash the game depending on your setup.
Proton-5.4-GE-3 GloriousEggroll
No audio. May be fixable with protontricks, but I haven't managed it yet.
1.5 update broke Proton support
Freezes within 5 seconds of launching, usually during the initial load. If I'm lucky it might get as far as playing the intro music, but this is consistent across every version and fork of Proton.
You might need to add "-linux" to the game's launch options to not hang on load.
Game halts for a couple seconds when loading next music track. Next music track won't play until a sound effect is triggered.
Some lobby text and all hats are misaligned down-right of where they should be, which is cosmetic but very distracting.
game can sometimes hang when toggling fullscreen and windowed.
Cannot get game to recognize save data from pre-1.5.
One or two maps will for some reason make the game chug to sub-1 FPS after a minute. Advancing to next map fixes it.
Not only runs perfectly out of the box with controller support and good performance, but in my experience it actually FIXES the inescapable crash-on-final-boss issue present in Windows!
Works out of the box, if using M+KB. No apparent issues other than controller support.
With Steam input disabled, controllers sort-of work, but you're stuck constantly using your secondary attack.
Runs nearly perfectly OOTB
There's a wait of about a full minute between the 'Made in Unity' screen fading out and the actual Loading screen appearing, and the game won't exit properly when I try to quit. Otherwise runs flawlessly.
Works generally fine with Proton 7.x's new EAC support, albeit with low framerates
Alt-tabbing doesn't work, but the game window loses focus until you tab back in.
Regardless of graphical settings being on low or maximum, framerate is often sub-30 in open areas. Not very conducive to Fromsoft combat.
Can't get past the launcher, even with all tweaks
Can't use Proton 5.13-x because protontricks doesn't work with that version of Proton. Using Proton 5.0-x, Tried applying protontricks 359320 -q dotnet472 win7, and installing wine-mono-5.1.1.1_ED-x86.msi via protontricks --gui, which let me open the launcher and register an account. After registering an account, the launcher now crashes when I click anywhere on it.
Will not start with any version or fork of Proton, no CLI errors given
Crash on launch with Proton 5.0-x, black screen with every other version and fork of Proton.
Probably because I've never been able to get Adobe AIR to successfully install.
On older versions of Proton, doesn't progress past the language selection popup before the main menu.
Generally runs fine out of the box, but can slow down a LOT when zooming into or away from larger ships. PROTON_USE_WINED3D fixes this.
Does not launch
Tried every version and fork of Proton. Tries for about a minute to launch but fails to materialize.
in terminal: protontricks 1224290 d3dcompiler_47 launch option: WINEDLLOVERRIDES=”d3dcompiler_47=n” %command%
Audio crackling was fixed by changing system configuration of PulseAudio to disable timer-based scheduling and custom tweak the buffer size. This has also fixed several other games with this problem.
After protontricks, add to launch options: WINEDLLOVERRIDES=”d3dcompiler_47=n” %command%
Personally I had to update protontricks and delete the game's compatdata folder, run it again, THEN apply the d3dcompiler fix to get it to work. Initially loads a black screen, but pressing anything begins the game.
Crashes immediately on launch.
Tried standard Proton, older versions, and Proton-GE. All the same.
protontricks: mfc140
Cannot capture audio driver, so can't really use the program at all.
Two possible fixes for nVidia users.
-dx11
To get the game to stop instantly CTD'ing on launch, I had to get rid of CrashReport.exe and .dll (I put them in a new subfolder just in case). Then I was hit with the dreaded Fatal D3D error which seems to afflict people trying to run the game through almost any version of Proton on an nVidia GPU.
The fix for me was to find Proton Experimental in my game library, right-click > properties > betas > enable Bleeding Edge, and set MHW to use that. Like it says when you select this, BACK UP YOUR PREFIXES FIRST if you're using Experimental to get any other games running.
Now I can compile shaders and wait for the beta test to actually go live.
Multiple fixes required for nVidia users
VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 %command%
If you get an immediate CTD on launch with no error message, take the CrashReport.exe and .dll from the game's folder and move them somewhere else. If you then get a Fatal D3D error, this seems to be from trying to run the game in Proton with an nVidia GPU -- find Proton Experimental under Tools in your Library, then right-click > Properties > Betas > Bleeding Edge. BACK UP YOUR PREFIXES FIRST if you're using non-bleeding edge Experimental for other games. This should get you through to shader compilation. Once that is done, you may get a C++ Runtime Library Assertion Failed error. Add the launch option listed above to fix that and get through to the language selection screen.
Still listed as borked at time of writing since the game isn't actually live for anyone to play yet, but fingers crossed this will make it playable once the servers are up.
Proton-6.5-GE-2 GloriousEggroll
Cutscenes all run with audio at varying amounts of desync, most pronounced in the opening cutscene. Can't find a working fix, but isn't much of an issue.
Shortcut wheel gets stuck on when alt-tabbing. To fix, hold Select/Back on controller to bring up quickchat menu, then back out. Might also need to tap L1/LB once or twice. VERY rarely, may crash when tabbing back in.
Controllers don't seem to work right unless you change the game's Properties in Steam to Disable Steam Input.
Probably works well enough? The freezes are extremely annoying though.
Poor framerates on even medium settings on a system that should easily handle it
Stops responding sometimes. Seems to happen more frequently with more fish.
Via Steam, takes an inordinately long time to launch and runs at an utterly unplayable framerate. Via Lutris, requires DXVK enabled to fix lighting and rendering glitches, and runs at a not great but perfectly playable framerate. Still nowhere near native performance. Crashes or hangs now and then, which may be due to Early Access rather than Proton.
Despite being out of early access, still lags and crashes as much as ever
Mouse is jittery to the point of being borderline unusable in menus
Some levels run alright, some stutter like nobody's business
Game crashes randomly at the drop of a hat, in levels, in menus, in minigames
Game also takes ~3 minutes to load to an unresponsive black screen, then another 2 minutes to actually start running. When it crashes, it can't be relaunched for ~10 minutes for some reason. With its level of instability, it's almost impossible to play for any prolonged length of time.
Doesn't quite fullscreen properly, as I can see the edge of my wallpaper along the bottom and right borders of the game. Some performance issues when a lot of stuff starts happening, and end-of-life records aren't saved, though these seem to be universal issues stemming from early access right now. Otherwise no problems!
Playable without protontricks. Greatly improved with it. Only remaining issue seems to be one instance of garbled text.
As cited earlier (thank you Unknown!), running the game once, killing it, then running "protontricks 266210 -q directmusic dsdmo gmdls" and "protontricks 266210 sound=alsa" in a terminal should both fix the MIDI music and make it close properly on exit.
Some of the music tracks are MIDI (such as all of the field themes) and won't play without protontricks.
When saving a replay, the filename text is totally borked, but it'll still work fine and is legible when you load it.
Didn't need protontricks, didn't need to install or configure anything, just selected Proton Experimental and bam. Works, runs well, has sound, no crashes.
Works out of the box with default Proton.
Mouse aim seems to have a strong intertia that makes it next to impossible to use properly. Unclear if this is Proton, the game itself, or some kind of obtuse hardware/software conflict.
Cannot get it to launch even after 2 weeks spent troubleshooting.
Rockstar Launcher spins its wheels for 2-3 minutes before saying the game is already running, and exiting. Tried Steam, Heroic Launcher, Lutris, every iteration of Proton, nothing will work.
It REALLY does not like alt-tabbing from fullscreen, but runs just fine windowed without tweaking. Twitch integration does not work however.
Game actually runs, audio can be heard if you click around the menu, but it doesn't display video.
Tried in Steam, tried in Lutris, tried with Proton, regular Wine, multiple versions of Proton-GE.
Runs fullscreen with a black BG as stated. Gamescope launch options cause it not to launch.
Not much fun to look at like this, and the semi-mitigative steps don't work for me.
Works, but needs a big audio buffer to avoid problems.
Audio is crackly with the default buffer length. Go into Options (top right) and increase it. 1024 should be enough to eliminate crackling entirely, with the caveat that there's now a full second of delay between the audio and video.
Generally runs without issue at max detail except for some notable performance dips in indoor areas with excessive godrays. Recommend turning shadow detail down a bit. Also note that the only way to adjust mouse sensitivity is via console command "inp_fMouseSensitivity=#" (use a value anywhere between 0 and 1, e.g. 0.38).
Generally runs unhindered other than some notable slowdown in indoor areas with excessive godray effects. Unfortunately, also seems to occasionally corrupt profile data on startup -- meaning ALL of your saves. Maybe do a manual backup of "steam/steamapps/common/Serious Sam 2/Content/SeriousSam2/PlayerProfiles" after each session just in case.
Vertex Shader Error
Same error as everyone else is having, which is odd when the prologue and main menu work fine. I dug up one old report of it working on Proton 3.7-8, but if there's any veracity to that it was likely an older version of the game.
Go into game options, Betas tab, select "prevamped". It's a much older version of the game that runs in an SD resolution and lacks several new features and bugfixes, but it doesn't have the fatal vertex shader error.
-Technically- runs and has sound with esync off, but has nasty arbitrary performance hitches that occasionally cause the physics to bug out, and all audio is a horrible stuttery soup that plays at about 20% of the intended speed.
Denuvo is gone now, so no worry of DRM errors. Great performance, recognizes controllers just fine.
Note that you will need a more recent version of protontricks than is provided by your package manager (version 20181203 at minimum)
Instant CTD without tweaking. Have only successfully tweaked Proton 5.0-10. SpaceEngineersLinuxPatches and its autoinstaller do not work properly. Protontricks installations get trapped in an endless failure loop when attempting via commandline. What DID finally work was manually changing the one line in the config file as documented on the SELP page, and running protontricks in GUI mode to install dotnet472, faudio, and d3dcompiler_47.
The dotnet install process took about THREE HOURS as it downloaded and installed almost every prior version of dotnet in order. The vcrun2015 install failed as it somehow detected another version present, but with this unholy mess in place the game now works, seemingly quite well and with Steam/multiplayer integration. I daren't touch it further.
Other than input drift (fixable by restarting), no issues, great performance.
After playing a few songs, input starts slowly drifting left. Not sure if it's the mouse or gamepad.
Proton-5.4-GE-3 GloriousEggroll
Has about a 50% chance of crashing instantly on launch, but otherwise runs perfectly, no tweaking.
Runs passably, but advertised drawing tablet support is broken
Whether Steam Input is enabled or disabled, the game will pick up taps and button presses from a tablet stylus, but will NOT allow use of the stylus to look around or paint. This was kind of a dealbreaker for me, if not necessarily for other people.
Framerates can dip while moving around or doing intensive things; shouldn't get in the way of painting, though.
Seems to help with music crackling. May actually make the visual choppiness slightly worse, though.
Noticeable visual choppiness. Not exactly a problem gameplay-wise.
GIF exports seem to work, but upon trying to find the file, it's never there.
If I tick the box to "Force the use of a specific Steam Play compatibility tool", it doesn't matter what version of Proton I select, any of the inbuilt ones, the current experimental, any version of GE, the game either won't boot or boots to a white screen. If I leave the box unchecked, it runs, albeit not particularly smoothly.
Proton-5.4-GE-3 GloriousEggroll
Game is barely playable at absolute lowest graphics settings, wineD3D and esync settings don't help at all.
Crashed once in the tutorial.
Works just fine out of the box with latest Proton build, other than a minor hiccup with detecting controllers.
Gamepad not recognized until Steam Input Per-Game Setting set to Off
install: corefonts, d3dx9, mfc42, xact
None of the fullscreen options apply properly, and at best horribly distort the game window. Would recommend against tempting fate with this.
With Steam Input disabled, most controllers should be detected, but analogue sticks and analogue triggers do not register. This means that you'll need to use the D-pad exclusively for movement, and almost no controllers will have enough buttons to map to all the required actions.
You need the three protontricks fixes to get the game working, and corefonts to make sure some of the fonts aren't broken. If you absolutely must use a controller to play this, you'll probably need to find some third-party keyboard mapper.
Works well with default Proton
Only complication of Proton is it may not terminate properly on exit. Performance is good though not as good as native, but more importantly running it through Proton can potentially fix crashes or freezes you may be experiencing on native Linux. You'll have to move your saves from ~/.config/unity3d/IronGate to ~/.steam/steam/steamapps/compatdata/892970/pfx/drive_c/users/steamuser/AppData/LocalLow/IronGate/ but they seem to transfer fine. Haven't gone online with it yet but it seems like it's integrating with Steam properly.
Works out of the box without any noticeable graphical or audio hiccups, albeit with abysmal performance until turning the graphics detail as low as possible. There are however major toothing issues with mouse support: occasionally it will become unusable in menus, but worse, if two stages are played in a row using M+KB (including the one-time intro stage), mouse aim will spaz out and become completely unusable. Controller support is unaffected. Playing through multiple stages with the controller does not seem to break mouse aim. It could be tied to starting or ending a stage with the controller, or even just using the controller briefly to reset the mouse aim. Further testing required. If you don't have a controller handy, YOU MUST restart the game between each stage to not have your run ended by technical difficulties.
Performance is vastly improved by using WINED3D11, at the tradeoff of inducing some Z-fighting in distant shadows. Mouse aim still tends to spaz out as a result of using M+KB at some indistinct point in the menus between levels, or from alt-tabbing. It can be fixed by toggling to windowed mode and back again while ingame (not while in the pause menu), but this is also inconsistent and can require multiple tries. TL;DR: Use a controller for all your menuing between stages to avoid mouse issues.
Irreconcilable performance issues
Game always starts minimized, struggles to switch into fullscreen, and occasionally gets stuck on a random resolution in doing so, including resolutions larger than supported by the display device.
Framerate tanks into the single digits in menus, or whenever multiple particle effects are active.
Seems to make far too demanding use of D3D11, WINED3D makes it even worse, and it fails to launch if attempting to force D3D10 or lower. No version or fork of Proton yields any better result.
Initially I got caught in a launcher loop that was fixed by deleting the Launcher.exe and overwriting it with the automatic backup. Then the game was closing every 5 minutes, which I fixed by keeping a controller plugged in. Then to fix the silent voices I applied GloriousEggroll's FAudio tweak. Vsync is off, esync is disabled, and the game is running windowed.
At this point it's reached the state of "playable", but it still crashes at the drop of a hat and has so much performance hitching as to be nigh-unplayable in Interception or Defense missions, and completely unplayable in any other mission type that actually has you moving around extensively. Downgrading graphics settings has next to no effect on this.
I have not yet tried running it via Lutris, but given that's basically bypassing Proton altogether it doesn't seem entirely pertinent.
Even with all available 'fixes', trying to play almost any part of Warframe in Linux is a nightmare.
Proton-4.21-GE-2 GloriousEggroll
All voice lines are missing unless FAudio tweak is applied, which increases frequency of crashing
Broken lighting in many environments
Instability in fullscreen
Game crashes if 360 controller is not plugged in
Crashes when mousing over or attempting to view the Abilities screen on many frames. Crashes immediately when trying to view Intrinsics menu (cannot level up Railjack skills). Crashes randomly if GPU particles are enabled. Crashes constantly in Orb Vallis. Crashes 28 minutes into a 30-minute survival run. Crashes whenever it feels like.
Launcher can sometimes break itself and get caught in an endless loop; backup launcher that used to self-propagate no longer seems to exist to escape from these situations
Works OOTB, crackly audio
Audio crackles badly. Can be fixed by changing PulseAudio settings. This does affect your system configuration, but shouldn't have any ill effect and is simple enough to reverse. Instructions are in section 4.3 here: https://wiki.archlinux.org/title/PulseAudio/Troubleshooting
With Esync disabled, hangs on trying to load a level. Without, FPS is so low as to be borderline unplayable.
Proton-5.0-GE-1 GloriousEggroll
Game runs in Steam via Proton 4.11 but unplayably slow. Doesn't launch at all via Proton 5.0.2. Runs generally well in the Proton GE fork.
minor input lag
Full version of the game seems to crash every few waves while in the middle of a wave regardless of Proton settings, despite that the demo was perfectly stable.
Seems to work just fine out of the box
Haven't gotten far yet, admittedly, but seems like-native so far.
