
GetBeaned
Published
Capped refresh rate to 40hz.
The game can run at 60fps a fair amount of the time, but can dip into the 40's and at time sub 30.
Cutscenes are broken using native Linux version.
Using Proton is a must if you care about cutscenes, as the native Linux version will display a black screen when cutscene should play.
I capped the game at 40hz as it can run quite hot and I observed dips into the 40's anyway.
No sound or keyboard input using the native build so I was stuck at the first screen. Changing to Proton makes the game fully playable.
So a few days ago, before I switched to Nobara, this ran absolutely fine using the native build, but on Nobara, the game wouldn't receive any keyboard input, which you need to get past the first screen.
Switching to using Proton works fine (it even recognised my Steam name which the native build didn't).
Strangely brutal on hardware, though I don't believe that is due to Linux. SSD pretty much required.
gamemoderun mangohud PROTON_ENABLE_NVAPI=1 %command% --skip-launcher --dx11
Poor performance in Act 3, though this isn't Linux exclusive.
Over 200 hours and between 5 - 10 crashes.
Non Linux-exclusive bugs relating to quests, items etc.
Most notable launch option is PROTON_ENABLE_NVAPI=1 for DLSS. Don't expect good performance in Act 3. I tried playing on a HDD initially but textures couldn't load quick enough.
Only occured occasionally when putting the Deck to sleep and waking it after some time. Fixed on relaunch.
Played on both a Linux Mint desktop and Steam Deck, perfect on both.
Perfect OTB.
I imagine this plays a lot more fluidly on mobile, though I also tried this on Deck, and it treats the touchscreen as mouse and therefore is a little bit wonky. There might be a way to get the game to recognise the touchscreen as a mobile touchscreen throug Steam Input. Ran fine there too though.
Audio worked fine for me using the native build. If using an external display, you may need to force higher resolutions in the Steam properties menu for the game as the highest it would go for me in game prior to any changes was 720p.
The default Unity port is fine from what I understand, but there's just no reason not to go with a source port. Chocolate or Crispy DOOM for a vanilla experience, or GZDOOM for everything else imo.
Perfect OTB.
Online is seamless, though I don't believe you can sort by server location, so you have to sort through all the 200+ ping games.
I tend to use source ports whenever I replay DOOM, but I might just stick with these from now on. Turning off VSync gets rid of the input lag, and from there it's solid. The new campaign, Legacy of Rust, works as expected too (and it rather great).
Use a source port for the best experience. The Unity ports of both games are perfectly fine, but there's no reason not to use a source port if you want better modding support (GZDOOM) or a vanilla expierence (Chocolate DOOM) for example.
Perfect OTB.
I noticed some minor flickering at the bottom of loading screens (and the credits), but it doesn't translate to actual gameplay and is apparently an issue with Unity, not the Linux build.
Using the native build there was general input lag, very noticeable in menus. Using Proton it still exists, but it's barely noticeable in menus and gone in actual gameplay.
Frame rate drops into the 50's in Act 2 on the native build. Switching to use Proton fixed it.
Worse performance and input lag using the native build, fixed by using Proton. I'd recommend installing the "essential fix" mod which removes all motion blur and makes movement less awful.
Seems to be the exact same as Dead Island, so running the native build, I needed a launch command to fix the black screen, and then performance is worse and inputs are less responsive.
Using Proton Experimental, the game runs flawlessly and all prior problems are fixed.
Issues with lighting and Steam overlay can be worked around, but crashing every 5 minutes can't.
Running in anything other than fullscreen causes massive lighting freakouts.
Sometimes drops to as low as 40fps seemingly randomly. Restart the game and it's running at 90fps in the same area.
Crash simulator. Crashes more with ProtonGE, but ProtonGE is required to fix some videos.
Regardless of proton version, the game just doesn't run properly. It will randomly tank in framerate and fix itself on a restart, until it decides to tank again. Lighting freaks out if you don't play in proper fullscreen mode. The game seemed to be more stable under Proton 9, but videos like the startup RE Engine video will be broken and some cutscenes will, literally, run at 1fps. With ProtonGE, the video issue is fixed, but it ended up crashing every 5 minutes.
Warning from prior Capcom Denuvo games: DO NOT mess around with proton versions more than 5 times; each proton swap is treated as a new system and after 5 "new systems" you will be blocked from playing for 24 hours.
Force vsync off as per other reports https://steamcommunity.com/app/410320/discussions/0/1747898397219502826/
Performance is largely stable in the base game, outside of dragons using large spell moves or a particular "enemy" in the very late game (Concecrated Snowfields). The DLC is mired with seemingly nonsensical frame drops, worst found in the final boss fight where I went from 60fps to 15fps.
A handful of crashes, almost all of them occured playing the DLC.
In solo mode, the game runs at a locked 60FPS. Playing online, the GPU and CPU utilisation is stuck at around 50% and the framerate hovers between 45 and 50FPS.
I noticed that using the default Proton (experimental), I couldn't find a game online. Switching to hotfix seemed to fix that, though it could have just needed a restart.
Solo is fine, but the framerate for multiplayer is too inconsistent to be enjoyable.
Huge framerate drops in multiplayer, often hovering around 40/45FPS, dipping below 40 sometimes.
I'm not sure what's causing multiplayer framerate to be so poor but it's specific to Linux. Testing on Windows shows a constant 60FPS, but on Nobara 42, it's just all over the place.
I'm reluctant to say it's due to the Nvidia DX12 issue because solo on Linux is absolutely perfect.
gamemoded -r in terminal before launch
Occasional hitching and generally can't maintain 60fps.
Using WhiteEyeDoll's suggestion, I ran "gamemoded -r" in a terminal before launch and found the sub 40fps drops gone. It generally maintains above 50fps, but rarely a steady 60fps, and using gamemoded -r seems to make the game less stable in that I saw more hitching than before.
Compared to how it runs on my system using Windows, there's clearly something wrong with running this game on Linux. In the former it's a pretty solid 60fps which I still can't achieve on Linux.
Controls are rubbish, but it works on Linux fine.
A is bound to jump, B to run, as defined by the in game controls, but actually in game, they're flipped. Rebinding them also rebind A and B in the menu. No option to use a normal camera either (permanently inverted horizonal axis).
Stuck in terrain 3 times.
Installed Microsoft C++ library.
I have a desktop profile for my controller mapped within Steam Input which caused this game to get confused as to whether it was a controller or mouse & keyboard, so I had to remove that profile to get it working properly.
Worked fine OTB, some settings cause texture flickering.
Setting the graphical preset to max enables a setting which causes texture flickering, though I'm unsure which setting it is, as I just reverted back to high and it stopped.
Ran Epic version via NonSteamLauncher. Didn't change any settings since it ran at 800p 90fps just fine.
Performance isn't great, though Windows users also report the same issues. Doesn't effect gameplay much.
Mostly runs above 60fps, but will frequently drop below that into the 50's and sometimes 40's. Looking at metrics, it's not stressing the PC at all, so no idea why it runs so poorly.
Given Grunn is a more relaxed puzzle game, the performance issues aren't a big deal, but they are weirdly present.
Almost perfect. Very, very tiny stutters can occur when loading into a new area - like going from Tartarus to Asphodel for example. I had to turn off vsync as I had bad microstutters with it on.
Native runs fine, but controller issues made me use Proton, which was also fine.
Using the native build, my controller inputs would sometimes not work, as if two inputs were bound to the same button. Sometimes it would fix itself on restart, sometimes it wouldn't. This problem didn't occur using Proton.
I didn't try this one out the box, but as with all DOOM-clones, there's really no reason not to use a source port, like GZDOOM for example.
Constant crashing makes for an infuriating time. Denuvo locked me out of playing too so I can't troubleshoot the issue even if I wanted to.
Used Proton 9 and Hotfix.
Borderline random crashes. If I had to pinpoint the issue it I would guess it has something to do with loading new assets as it tends to happen in new areas or cutscenes,
Perfect OTB if using X11, and probably fine with Wayland if using AMD.
My last report noted constant crashing and digging into it, it seems Nvidia's 555 drivers under Wayland (using Xwayland here) can cause crashing in any game hitting the VRAM limit. I've seen some say reverting back to 550 drivers echews this issue, though you give up the improvements of 555 and will potentially experience flickering.
I instead just swapped to an X11 session and it works absolutely fine.
One single throughout my entire playthrough. Stable framerates throughout with no tinkering required.
Fine out the box, but required a hex edit to be up to the standards of the first game.
Due to capped and inconsistent framerate, mouse movement was sluggish.
Game prior to hex edit was capped at 50fps and would fall below that.
No other report mentions this oddly, but on the PCGamingWiki entry for the game, it makes note of a hex edit required to get high, stable framerates, and I needed to do this.
Firstly you need to de-obfuscate the Monkey2.exe using Steamless (should run fine using Wine), then, using a hex editor, change "76 05 0F 57 C0 EB 06" to "89 C0 0F 57 C0 EB 06". Lastly, cap the framerate (using Mangohud for example) to your desired framerate otherwise the game can refuse to launch.
Disable Steam overlay to play.
As other reports highlight, the game will freeze on the startup screen without tinkering. Several solutions seem to exist, but the most straightforward one I tried was to just disable the Steam overlay in the game's property window and it works perfect.
Two times the audio disappeared during a match, and the controls on the end results screen died too, but once back on the main homescreen it fixes itself.
Frame rate in menus drops to the low to mid 40's for some reason.
Every time you boot the game, your first or second match will include a 2 - 3 second freeze, after which the game will run fine.
There's also a consistent lag when entering a match. The 3 second countdown as a fight begins isn't in sync with your game so you can often start fighting on "2" or at worst you get control as the countdown has just started.
Almost perfect. There can be some slight slowdown during intense fights, but it tends to occur when you're getting knocked around beyond ability to fight back on a busy stage.
Opt for the Steam version if possible. GOG version via Lutris requires complete reinstallation after every update.
Edited TKGRAPHICSSETTINGS.MXML for better performance (see NumLowThreads stutter fix)
On a few launches, the game's audio would cut out for a second or two every half a minute or so.
A very stuttery game on Windows and very much the same on Linux.
Steam version is the way to go, if only because you don't have to completely reinstall the game after every update. The Lutris install script which bundles in GOG Galaxy is required for online, but GOG Galaxy is unable to push updates properly.
Stuttering seems to be inevitable regardless of hardware. I initially played this using a Ryzen 2700x, but even with a 5600x it can fall into the 50's, just low enough to irritate you.
Bar that, very playable.
Due to whatever bug is causing the huge framedrops, the game is too unstable for extended play.
gamemoderun PROTON_ENABLE_NVAPI=1 %command%
For an reason I can't determine, occasionally the game's framerate will tank below 20fps when opening the inventory menu. Coming out of it it returns mostly to normal, but the inventory will permanently run like crap. Sometimes, entering a new "zone" will permanently make the whole game drop below 30fps until restart.
Perfect OTB.
I played mostly through the vkQuake source port, but the new(ish) remaster is honestly perfect for pretty much anyone.
Perfect OTB.
I played this mostly through vkQuake2, but should've just stuck with the 2023 remaster as it's pretty much perfect. vkQuake2 had a nasty sound bug for me.
Occasionally on launch no inputs will register and it required a relaunch.
In addition, my PC went into sleep mode once while the game was running and continuing the game after wake capped the FPS at 22 fps until relaunch.
Perfect out the box.
3 completely random crashes. The game auto saves so frequently it didn't matter.
Only played single player, but worked perfectly with default settings using Heroic to play an Epic Game Store copy.
eval $( echo "%command%" | sed "s/2KLauncher\/LauncherPatcher.exe'.*/Base\/Binaries\/Win64Steam\/CivilizationVI'/" )
I first tried the Linux native build, but experienced several crashes, frequent frame drops, and an inability to set the game to windowed fullscreen.
Using proton to play the Windows version fixed all these problems: zero crashes since, option for windowed fullscreen, and a rock solid 144fps.
One draw back is that with the Linux build, they seem to have disabled the superflous 2K launcher, and thus using proton means it tries to launch the 2K launcher which is cumbersome, pointless, and broken in my experience. Using the launch command provided circumvents this.
Near perfect out the box.
In the tutorial, changing the sensitivity didn't work for me, so I had to get through it with my sensitivity at wacky speed, but getting into a proper game the slider worked fine.
Perfect out the box.
By the late game (say, 300+ on screen cards) I was seeing dips into the 50's, though it wasn't stressing my PC at all.
Late game FPS problems, though given the slow nature to the game it's not really an issue.
The game is hardcapped to 60fps. Doesn't support 16:10 so black bars on the top and bottom. Otherwise perfect on max settings.
Perfect(?!) out the box.
From what I can tell, these are just the original Flash games packaged as one using something to emulate Flash. They play exactly as they did back on 2000's browsers, which is to say really, really badly.
As of 17/01/2025, the game is unplayable on Linux.
Extreme framedrops to the single digits at random.
Rare crashes when loading into games prior to the 17th January 2025.
Inputs will rarely get "stuck", for example you won't be able to sprint or fire.
It should work fine despite some occassional crashing, but since the 17th January, an update (maybe) is causing significant performance issues across a range of Linux PC's. The issue is currently being investigated on a couple of Gitgub pages (https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2598859337, https://github.com/HansKristian-Work/vkd3d-proton/issues/2293), and until the issue is fixed, the game is unplayable.
Broken from 17/01/25, fixed 21/01/25, now broken again.
Last week the game suffered a universal Linux bug which caused unplayable framerates. It was fixed for a day via a Proton update, and as of today, the game is broken again after an ingame update causes the game to fail to launch.
The developer "addressed" the issue since it was affecting every operating system with a hotfix, but it didn't fix it for Linux. The game can't be launched in any way.
The game doesn't perform as well as it did a week ago. I'm getting drops into the 60's pretty frequently during fights, even dropping below that occassionally, where a week ago it would be 90+ all the time.
There still seems to be some sort of memory leak. After an hour or two the game will eventually crash when loading into a game.
The game now works using Proton Hotfix or bleeding edge Proton Experimental. It's a shame the game isn't performing as well as it did before this whole situation, but it works.
gamemoderun mangohud %command% -novid -nojoy -nosteamcontroller -nohltv -particles 1 -precachefontchars -noquicktime +exec custom.cfg
MasterComfig for optimisation.
Perfectly playable out the box, but as my launch commands indicate, you can optimise the game for more stable framerates. MasterComfig is responsible for most of them. Playing the game with a Ryzen 7 2700x, I noticed frequent frame rate drops below 60 for some reason, but upgrading to a 5600x allows for a stable 144fps.
Great OTB, better with tModLoader
Game logic runs at 60FPS, so if you want to play at a higher refresh rate, you'll need to install tModLoader (a Steam app) and in that "game's" workshop, subscribe to the "High FPS Support" mod. From there, it'll launch alongside Terraria and enable higher refresh rates.
The game is capped at 30fps which results in less than fluid aiming. It crashed on me a single time, right at the end of the game during the final boss fight, but I eventually beat it a second time with no crashing.
Bethini and ModOrganiser for stability mods only.
On medium presets, looking down on Whiterun from Dragons reach would cause major frame drops into the 30's. More general framerate hovers around the high 40's. In combat can absolutely tank into the 20's.
Bethini didn't make much difference to the framerate on medium. On low or poor presets, the game Raj significantly better, but looked closer to the Switch port which isn't in keeping with the power of the Deck.
Recommendation to play the Special Edition instead. The same test (looking down at Whiterun from Dragonsreach) reproduces no such issues on the same presets, with the draw distance cranked higher.
Initial review was negative as I was running it using Proton 6.3, which I've found makes for a stuttery mess in Bethesda games.
Upping the proton version to 7, experimental, or recen GE versions (I tried 28 and 29) led to very pleasant experience.
Looking down on Whiterun from Dragonsreach can still lead to some framedrops, but where I was seeking drops to the high 30's, they only drop into the mid 50's and generally improve as the game is played.
I recommend tinkering with shadows. Turning them from high to low left me with a near constant 60fps, but with shadows, stuttering was fairly frequent.
Bethini.
Bethini preset set to medium with recommended tweaks enables. Important as default Skyrim medium presets causes framedrops into the 40's. Increased view distance to around two thirds.
With these settings, game runs at a near locked 60fps. Without them, game tends to dip into 50's frequently and occasionally 40's.
Perfect out the box.
These play, to my memory, exactly like they did 15 years ago on Armor Games. They seem to be capped at like 35fps, but that's how they were back then.
Subpar performance and bad M&K controls. Playable, but should not run this bad for what the game looks like.
I bound "execute" and "pocketables" to side mouse buttons and both occasionally needed rebinding on game restart.
A lot of areas chug for some reason, falling into the 40's with 100% GPU utilisation. The only setting which had a meaningful difference was shadow quality. On low, I could get a somewhat stable 60, which is a bit of a joke given the game isn't exactly a showstopper. Doesn't seem to be Linux-specific going by Steam discussions.
A few crashes.
I tried Proton 7, 8, and experimental, but I was met by a white screen on launch followed by a crash after 10 seconds. Proton 9 beta was the only one which worked for me.
DXVK_FRAME_RATE=60 %command%
Framerate dips into the 40's specifically in Chapter 5, when outside, which is like 20 minutes.
Some physics and mouse movements are tied to framerate and if it goes over 60 it can freak out, so cap it to 60.
As functional as I remember it being on Windows.
Hectic areas can tank the framerate down into the 20's.
I played this in 2014 on an old FX Windows rig and it ran just as bad as it does here, which is to say it's mostly fine until the mid game when swarms of enemies can destroy the framerate.