Gamma Lyrae
Published
mangohud %command% --skip-launcher
The given launcher line above is largely optional. Here's what you're doing with it:
mangohud: I use this to set my own framerate cap independent of the in-game settings, because the "early" setting for the framecap in mangohud results in more consistent frametimes and performance than the built-in limiter the game offers.
%command%: this signals to Steam that any further commands listed are not passed to your linux environment or prior invoked applications, and will instead be passed to the application being launched
--skip-launcher: This skips the launcher for the game, which results in a faster boot.
By default, the game will select the DX11 rendering pipeline, which will be translated to vulkan using the steam proton runtime tools. I haven't tested setting it to Vulkan natively instead since DX11 works well enough for me (if it ain't broke, don't fix it)
On a different PC using Windows, Baldur's Gate 3 will crash after a couple of hours of play, even in Act 1. On Linux, I can play for several hours and don't experience so much as a single stutter. While this may not be true for everyone, it is true for me that I have had a more stable and enjoyable experience playing this in Linux via proton than I had playing natively under Windows 10.
Optional features tested: Logging in to or creating a Larian account (works) Connecting a Larian account to mod.io (works) Downloading mods through the in-game interface (works) Playing game with mods enabled (works)
Optional features not tested, but probably work fine: Multiplayer (online) Multiplayer (offline via split-screen) Mods installed from an external source such as Nexus Mods
The linux native version is out of date. Force a proton build of your choice and play the windows version instead.
-tcp
Out of the box, when hosting a multiplayer session (even over LAN), the connected players would stutter around on my screen. They'd also complain of inconsistencies with interacting with objects and would occasionally stutter step around on their own client. Not a performance / fps related issue, it all has to do with the networking aspects of the game.
Setting -tcp as a launch argument switches the game from using UDP to TCP, which significantly improved playability for players connecting to me. Depending on your networking conditions, this may or may not be required. Played through the game from beginning to end on normal and didn't encounter any linux specific issues. Please be advised that the linux native version is out of date and cannot crossplay with windows users. Force proton as a compatibility tool to grab the windows version, it has the final patch for the game and lets you play online with other windows/linux via proton users.
Game wouldn't launch when installed to an EXT4 formatted mechanical hard drive. When I moved it to a BTRFS formatted NVME, it launched fine.
Aside from the weird issue of not booting from an EXT4 file system, worked fine.
Some of the tutorial videos do not play correctly (These are the small clips that play when a new screen has popped up to explain what a button does or how a feature works). An immediate one you'll come across is the "wall jump" tutorial video.
Minimal impact on gameplay. Most of them do play correctly.
When launching as configured by steam, there is no audio in the opening cut scene. I also attempted Proton GE 9-11, still no sound. Switching to regular proton 8-05 restored audio to the intro cutscene and seems to be the best fit for this game. Launch commands and recommendations to hex edit are likely deprecated and no longer required.
Needs a transcode of the videos and a plain text save edit to configure to play correctly.
/steam/userdata/xxx/631510/remote/options.sav
Change the width/height to match your resolution (Only required for resolutions higher than 1080p)
FMVs don't play correctly. Will play for a couple of seconds without sound, and then skip without any input.
https://www.nexusmods.com/devilmaycryhdcollection/mods/51?tab=description
You can download this mod, or you can manually run the provided script on your end inside the videos directory for each game.
Right click the name of the game -> Manage -> Browse local files Navigate to data. Inside each of dmc1, dmc2, and dmc3 is a videos folder. Navigate there for each game, and in a terminal and run this:
for FMV in *.wmv; do ffmpeg -i $FMV ${FMV:0:-4}.mp4; rm $FMV; mv -- ${FMV:0:-4}.mp4 $FMV; done
No "flip" was required for the videos to play in the right orientation while using GE-Proton.
Note that this does change the game files, and any time you try to verify the integrity of this game, steam will re-download the original videos. Once the transcode is complete, consider setting aside a copy of them to restore later.
The game does attempt to cap at 60fps. If yours doesn't or the frametimes are unstable, you can use mangohud to cap it to 60. My xinput controller was detected and worked fine.
Works well enough in single player mode. Wouldn't recommend for LAN or online multiplayer
Minor audio popping for a few minutes after boot. Seems to clear up after that.
Significant stuttering after a period of play that doesn't happen in Windows. Issue is worse in Multiplayer.
The poor performance/stuttering issue steadily gets worse, until the game eventually crashes.
Minor sync issues between host/clients. Sometimes player models will stop updating their position visually, though any actions they take are still honored (ie, you may be followed by invisible players, but their auras still affect you and they are still doing damage)
I've tried multiple versions of proton. Proton 8 was the earliest build that doesn't freeze on a black screen when initiating a multiplayer session. After cycling through a few variants (cachyos proton, different GE builds of proton, even a version of proton optimized for FFXIV since it includes easy to use NTSync patches), testing most of them on the 32bit, 64bit, and Legacy DX9 branch, I could find no solution to the stuttering and crashes.
I've played the game on Windows for a few hours and didn't experience any of these issues.
(STEAM VERSION) Works well out of the box using non-gmail email login
This report is specifically for the STEAM VERSION of the game, which differs from the standalone "Windows Version" you can download from the website.
No special tinkering required. Game just boots and plays fine. My account is associated with an email address (not using the Gmail or Google login processes). Other login methods, including just being associated w/ your steam account, I did not test.
SteamDeck=1 %command%
During Season 0, the game launched with no special tinkering. After the Season 1 patch, you must now run with the argument above.
This may be subject to change as I don't think they've intentionally done anything to break compatibility. Keep an eye out on future reports, as a general rule you shouldn't launch games with arguments unless they're strictly necessary.
Occasional crashing. Game seems sensitive to change and may work better if you boot using an older kernel.
Game hitches every 10-20s or so without a tweak.
Follow the advice here if you're experiencing the periodic hitching/stuttering/freezing that happens in 10-20s intervals.
https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2675637814
Current workaround found for issue (Linux only):
/home/USERNAMEHERE/.steam/steam/steamapps/compatdata/2767030/pfx/drive_c/windows/system32/WindowsPowerShell/v1.0
Rename powershell.exe to another name, this will only affect powershell in the instance for marvel rivals's proton, and will not mess with anything else. Fixes issue immediately with no apparent issues in multiple matches so far tested.
My guess is there's some dev-level performance profiling that got pushed out into the live patch. On the linux side of things, you can remove its access to powershell by renaming it in the prefix for the game and the stutters stop.
Game no longer requires "SteamDeck=1" in properties to launch. Aside from the stutter issue you can fix with the tweak, the game seems about as stable as before (for better or worse) on kernel 6.13 and mesa 25 as it did 6.12 and mesa 24.
Can work for some users out of the box with Proton Experimental; most will need tweaks to play
WINEDLLOVERRIDES="dstorage,dstoragecore=n,b" %command%
Open config.ini in the game directory, search for
ParallelBuildProcessorCount= Change this to match the number of threads your processor supports. RenderWorkerThreadPriorityAboveNormal= Setting this to "Enable" can improve maximum fps, but depending on your system specs and available processor threads, may reduce 1% and 0.1% lows (ie, introduce stuttering). If you don't like what happens on Enable, change it back to Disable. There's no good one size fits all recommendation here, it depends on your specs.
All of the "fix the typos" tweaks are placebo and the game will revert them on next boot. If you change things that you're meant to change, you wont have to set your config.ini to be read only.
The game doesn't poll VRAM correctly. It adds the space the game is taking to the "VRAM used by other apps" segment of VRAM, and then tries to squeeze the game into whatever it thinks it has left. You can mitigate this by not navigating to the graphics options. IE, configure the graphics the way you want them, save and exit, then reboot the game and DON'T LOOK AT THE GRAPHICS SETTINGS AGAIN.
Lots of stuttering when turning the camera due to an old version of dstorage libraries being shipped with the game.
With a series of tweaks, most users will be able to play. Even those that don't experience crashes or significant performance issues out of the box can improve their experience with tweaks. Here's what I've applied so far, and you can probably find guides to explain how to do these better than I can.
- Use a more recent build of vkd3d to address crashing (has no impact on performance currently, only fixes game stability). This is the DX12 -> Vulkan translation layer, and there are updates that address crashing issues specific to this game in recent updates that aren't yet published to any stock version of Proton/Proton Experimental/GE-Proton. If you don't know how to grab the dll from github or compile it yourself, you can change to Proton Experimental, and then opt-in to the "bleeding-edge" beta. NOTE: I do not recommend actually playing on the bleeding-edge beta. Changing proton versions counts as a new install according to Denuvo, and you are limited to 5 per day. Once you have the bleeding edge beta, make a copy of the directory, then revert the game to whatever version of proton you were using (Experimental is fine as long as you're not using bleeding-edge). Then, copy the contents of files -> wine and files -> vkd3d into whatever proton folder you're using for the game.
2)Update the dstorage dlls. This will address stutters related to loading in new content, most noticeable when you're panning the camera around or running to and from different areas. If you don't have a game that's using the latest build and don't know how to get them from microsoft directly, there's a mod on nexusmods that provides them. Copy the dstorage dlls from the game directory into system32 of the prefix for the game, overwrite the dstorage dlls in the game folder with the new ones you acquired, and use winedlloverrides to force the use of the ones you copied into the game folder.
- Configure the games graphics settings the way you like them, then save and quit. Never look at the settings again! When you go into the graphics settings, the game tries to detect how much VRAM it's using, how much VRAM is used by other applications, and how much VRAM you have. The game incorrectly counts itself in "VRAM used by other applications", which will severely hamstring the games ability to do garbage collection and load in new textures/content. As long as you don't trigger this bug, the game will correctly utilize your VRAM.
4)Don't use the high res texture pack.
Works fine
No issues currently. A major patch is coming sometime in 2025 with a new DLC which could change things. Keep an eye on future reports.
Works great out of the box
Seems fine. Controller support is good. Plays exactly as you'd expect. No apparent linux/proton/wine-exclusive bugs that I can report.
Note: Did not test playing with a keyboard.
Unlike Civ6, the performance between the Native linux version and the Windows version is very close. Personally, I observed better frametime consistency with the linux build. However, the graphics settings often did not "stick", seemingly adhering to a default level regardless of what I chose. Most notable of these is that it didn't matter what kind of AA or upscaling I chose, the game always rendered native with no AA at all. This made some fine details like hair on the leaders look especially bad. Additionally, as most linux distros do not yet have a native color management system or HDR support, nothing you do in the command line or OS options will enable the game to run in HDR mode.
The windows version via proton seems to honor the graphics settings you choose. I selected vulkan. If you can run other games in HDR using gamescope, Civ7 can also be ran in HDR using gamescope.
The UI suggests that if you turn on vsync, a framecap setting will be exposed. Personally, I never saw this happen on either the linux build or windows build. If you want to cap your framerate, I recommend an external tool like mangohud.
The game has a native linux port. It runs very, very poorly. During the gathering storm AI benchmark on my hardware, once over 540 seconds had elapsed, I ran out of patience and ended the benchmark. During the course of the entire benchmark, the framerate was low and audio skipped and popped constantly.
The windows version via proton completed the benchmark in two minutes on my hardware, ran at a high framerate, and had zero audio issues. I personally use proton 8 based on other recommendations here, but I haven't tested others to see if they crash or anything.
Feels like a native linux game.
Worked out of the box with no tweaks. This has remained true through a couple of game patches, too. Played for over 80 hours on a multiplayer server with no issues.
