AbedsBrother
Published
Normal performance in menus, 2 fps in-game
I knew there were fps issues with AoM. Tried a number of things: no Fsync, no Esync, Force Large Address Aware, WineD3d (instant crash), over-clocking, underclocking. Nothing. Same 2 fps.
Here's the thing, though: Mangohud worked, so I got to observe system usage. In menus, the cpu and gpu usage was normal; cpu used about 6 threads, loaded at ~15-30%, gpu clocked up to its max at 10% utilization. Exiting the menu and returning to the game, cpu usage plummeted to a single thread at 100% with the rest at 0-1%, and the gpu clocked down from 2060mhz to 800mhz. This isn't how the game performs in Windows, so this isn't normal behavior. Something's off in the resource allocation / the way Proton answers the program's request for system resources.
There are both DX9 and DX10 versions of Assassin's Creed. By default, Steam uses the DX10 version, which resulted in a black screen after viewing the intro videos. The screen was not frozen; mangohud still showed changes in fps and system load, and I could hear the menu sounds when moving my mouse around. I simply couldn't see anything.
Re-named AssassinsCreed_Dx9.exe to AssassinsCreed_Dx10.exe to force the game to use DX9.
MSAA cannot be enabled if the resolution is set too high (this is an issue on Windows as well). To fix it, edit Assassin.ini and set Multisampling=2 In Linux, Assassin.ini is located in .local/share/Steam/steamapps/compatdata/15100/pfx/drive_c/users/steamuser/Application Data/Ubisoft/Assassin's Creed
Sometimes lines of audio repeat. Like the question, "Altair, why are you here?" would play as, "Altair, why are you - are you here?" (not a problem on Windows)
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 DXVK_ASYNC=1 mangohud gamemoderun %command%
delete systemdetection.dll in the game's installation folder, otherwise game would crash before reaching the menu
Followed the recommendations of no esync and no fsync, game still wouldn't get to the menu. Discovered I needed to delete system detection.dll from the game's installation folder. Then the game started normally. Had choppy framerate. Added the Proton Async parameter, and everything smoothed out.
While the game quits normally, need to manually end ACR from within Steam to force-quit Ubisoft Connect.
Disabling Esync helped with smoothness. Also added the "RADV_PERFTEST=aco" parameter (w/o quotations o/c)
- enabling DX11 features caused stutter (left them off)
- enabling MSAA caused stutter (left the setting on FXAA High)
- since I'm on Radeon, didn't bother experimenting with PhysX
- gamemode did properly turbo my gpu when needed, but got higher fps by manual overclocking (through CoreCtrl)
- cpu performance profile (in CoreCtrl) needed to be changed to "CPU Utilization". This allowed individual cores to clock higher (around 4.0Ghz) than then when the "CPU performance" profile was selected (which overclocks all cores to around 3.45Ghz). Made a big difference in overall smoothness (Batman AC is of the old school of games that prefers fewer, faster cpu cores).
Also used RADV_PERFTEST=aco
Renamed Borderlands2.exe to Launcher.exe (otherwise the game would refuse to start). This resulted in the game launching immediately after clicking the Play button in Steam (bypassing the BL2 launcher).
Frequent frame-drops, esp. in Tundra Express & Bloodshot Stronghold (also problem areas when playing on Windows), with frame-rate dips into the upper 30's when there was a long draw distance. Otherwise low-60's to my screen-refresh-rate of 75 was common.
The native Linux port of BL2 has three major issues:
- no shadows or dynamic lighting (bugged)
- no character import (you have to start over with a new character)
- Commander Lilith DLC not available to Linux players (even if it is registered to your Steam account). This DLC also broke crossplay (Linux gamers cannot match-make with Windows gamers)
Despite the Proton-Windows version running worse than the Linux port, the Proton-Windows version offers the full range of graphics features (had no issues with the HD texture pack, either), all of the content (if you purchased it o/c) and all of your previous saves / characters. And most of the remaining player-base is on Windows anyway, so using Proton to play Borderlands 2 is the clear choice at this time. Fps-wise, it's not the best experience, but it's tolerable.
RADV_PERFTEST=aco gamemoderun
Do not use the HD Texture pack. Game crashed almost immediately.
Switching to the Zen kernel has made a big difference in overall smoothness.
The native version was actually running very well for me - I fixed its issues w/ shadows etc. by editing a config file - but since the Commander Lilith DLC is Windows-only, Proton is the way to go for Borderlands 2.
mesa_glthread=true double_buffer=true depth_size=32 gamemoderun mangohud taskset --cpu-list 0-3 %command%
The shadows are disabled by default (this was done by Aspyr when they ported the game to Linux to get better performance). To re-enable the shadows, you'll need to edit willowengine.ini. By default this is located in
[home folder]>.local>share>asypr-media>borderlands 2>willowgame>config
open willowengine.ini with a text editor (like gedit)
Find the section SystemSettings
Find the DynamicLights line, and change the parameter from False to True
Save & exit. Borderlands 2 will now have the correct shadows & lighting.
Proton is the way to go if you want to play the Commander Lillith DLC (and its 10 additional levels), which is only available for Windows. But I just felt like trying the native port and seeing how it performs. It's good up to about 90fps; if you try for 120fps it won't hold it, it'll dip under 120 regularly. Neither cpu nor gpu was maxed, so I suspect it's an OpenGL bottleneck of some sort. I played at 60, so it was still a smooth experience.
RADV_PERFTEST=aco
Ambient Occlusion is bugged. Enabling it adds horizontal lines across the lower half of the screen. Disable it, and the anomaly disappears.
I have a Freesync monitor, with variable refresh rates from 50-75hz. The game's v-sync, when enabled, only detected the lowest possible refresh-rate, locking the frame-rate to 50fps (tested with MangoHud and the Steam overlay fps monitor). Turning v-sync off and capping frames to 75 in-game (75fps is one of the options in the game's "fps limit" menu) helped, but there still is minor screen-tearing.
- Like many others, had to rename / move Launcher.exe, then rename BorderlandsGOTY.exe to Launcher.exe, otherwise the game wouldn't start.
- Had an odd render issue at first. MangoHud would glitch & flicker every time it refreshed; while this glitch was occurring, any attempt to change settings in the Options menu would result in rapidly scrolling through the options (as if the mouse wheel were stuck in an endless scroll). Disabled MangoHud and Game Mode, and the problem disappeared. Re-enabled MangoHud and Game Mode, and everything was fine. Problem has not re-surfaced.
After working through the issues, runs as well as it does on Windows. Achievements and Steam overlay work properly.
RADV_PERFTEST=aco
Disable the Steam overlay, otherwise game would crash on alt-tab. Disabling the overlay also got the in-engine cutscenes working again (with the overlay, the audio of the cutscene would play, but there was no visual until it was time for gameplay)
Some performance issues, but still playable
Occasional missing textures, and every time I loaded a game or a new level I had to re-apply my anti-aliasing settings.
Major frame-drop in engine-driven cutscenes (to around 24fps) and when entering new areas (game completely locks up for about 3 seconds). Still playable tho
I've played Close to the Sun on Windows and it had some frame-drops even there, though the problem is significantly exaggerated on Linux. DON'T disable E-sync; doing so made performance much worse.
I ran the game with my usual parameters enabling the ACO shader compiler and game mode.
DXVK_ASYNC=1 gamemoderun %command%
Alt-tabbing would result in the game crashing
Had to lower settings to Medium at 3440x1440 to get a mostly smooth framerate. Still had occasional frame-drops, but they disappeared in seconds. Otherwise an acceptable experience.
6.10-GE-1 GloriousEggroll
Glorious Eggroll Proton-6.10-GE-1
I usually prefer using the standard Steam Proton builds, but running with 6.3-5 resulted in no cutscenes. There is a lot of story in the cutscenes of Echo, so they're really needed to fully experience the game. It's probably some sort of "media foundation" glitch, but instead of trying to patch individual files I installed Glorious Eggroll Proton-6.10-GE-1 (the latest GE build at the time of writing this). Everything worked after that.
RADV_PERFTEST=aco gamemoderun
Occasional texture flicker
Sometimes crashed when loading a cinematic or loading a new area
In the game's forums, people frequently complained about performance & optimization. I had no issues holding 60fps at 3440x1440, with everything maxed but Ambient Occlusion turned off.
DXVK_ASYNC=1 DXVK_FRAME_RATE=60 gamemoderun %command% -high -USEALLAVAILABLECORES
Borderless Widowed crashed when alt-tabbing. Exclusive Fullscreen worked correctly.
Had to play on lower settings than on Windows to get a smooth frame-rate
Some serious frame-rate drops. Disable all of the following:
- vsync (causes some stutter)
- Cloths physic (disabling improved frame-times by a lot)
- SSAO (solved the frame-drop issue in the skills menu when leveling up)
Ran perfectly after configuring it this way. Saves, leveling, complex visual geometry - steady 60fps almost the entire time. Just a few frame-drops here and there, usually when there were a lot of reflections on-screen. I did try a newer Proton with the new RADV_PERFTEST=gpl, but that produced a stuttery mess, so worth sticking with an older Proton and DXVK_ASYNC=1 for now.
Crashes when clicking in menu
Can view the main menu, but try to move the mouse or click anything and the game immediately crashes. Tried several different options (including forcing D9VK) but nothing helped. (Using Proton 6.3-4) HOWEVER The standalone GOG installer, installed via Wine and run through Lutris (using system-installed dxvk 1.8.1-1), works very well (only the cutscene-videos are missing, which, going by the other reports, is a common problem).
Proton-6.10-GE-1 GloriousEggroll
Proton-6.10-GE-1
No cutscenes
Switching to Glorious Eggroll 6.10-GE-1 made the game perform roughly the same as Windows (no more crashing in the menu). Still no cutscenes, though.
gamemoderun %command%
Use DX11. Has some issues with frame-rate dips because its Unreal 4 (even with reduced settings), but ran well otherwise.
gamemoderun
Played using the Vulkan port (which is the default download). Never knew I was playing on Linux. Everything worked the way it was supposed to, and performance was excellent. 10/10
fwiw the OpenGL version is still available as a beta.
mangohud gamemoderun DXVK_ASYNC=1 %command%
Unreal 4 can be a problematic engine, and proves to be again in Paradise Lost. Frame-rate was all over the place (High preset at 3440x1440), but this is a common complaint when the game is played on Windows as well, so am satisfied that there were no unusual hiccups.
Deck users will need to lower settings to get steady frame-rates.
You'd never know you're playing on Linux
Runs just as it did on Windows. (Didn't try multiplayer.)
Dynamic Lighting can glitch without warning, resulting in light & shadows flickering on and off. Turning Dynamic Lighting off fixes the problem but makes the visuals look flat. Not consistent, and may go 30 minutes without an issue, or it may happen multiple times within 5 minutes. (Dynamic Lighting works correctly in the native Linux port).
The native Linux port averages around 45fps, the Windows version through Proton averages around 60. Both still demonstrate Saint Row 2's horrible optimization, with frequent frame-drops into the 30's (the Linux version drops even lower, into the upper 20's). If you're picky about your graphics quality and don't mind a lower frame-rate, the Linux port will work. Also worth considering: save games from the Windows version are not compatible with the Linux version (neither are Linux saves compatible with the Windows version). Which version is better comes down to which sacrifice you're willing to make: frame-rate or visuals.
completely broken
gamemoderun
Native version crashes after intro videos. Launching the Windows version through Proton freezes Steam with a "finishing installation" message. This lasts about two minutes, then an error message appears saying, "The Steam servers are busy at this time. Please try again later."
All - literally all - of my other installed games run fine after receiving this message. (My other installed games include easy-to-run games like Shadow of Mordor, but also tricky games like Assassin's Creed Revelations. Both launched without issue after receiving the "busy server" message).
The GOG version, installed via Wine and run through Lutris, launches and plays without issue. This is a rare case of Steam's framework being literally broken.
Choose DX version, then crash.
- Tried numerous configurations and several different versions of Proton (5.0-9, 4.11-13 and 3.7-8). Tried Esync on vs off, WineD3D (kind of pointless since the native port runs in OpenGL, but tried it anyway), ACO on vs off. Tried renaming the preferred exe (whether DX9 or DX11) to the name of the launcher, so the game would launch immediately after clicking the Play button in Steam; this has worked in other games (Borderlands 2) but didn't work here.
- Each time, the pattern was the same: hit Play, the Launcher appears, offering the choice between DX9 and DX10 & 11. Didn't matter which DX I chose, the Steam icon would spin for a few seconds, then the game would close. Didn't even get a momentary black screen like the game tried to load the main menu.
- Kind weird that there is such a major issue with SR3, since SR4 works really well with Proton, but at this time, the native port is the way to play Saints Row The Third. Because at least the native port functions properly (even if the frame-rate dips can get very bad).
gamemoderun
Sometimes the game wouldn't exit when clicking "quit." Had to alt-tab and select quit from within Steam. The game would then quit as expected. Sometimes audio would skip when passing a checkpoint. Minor issues.
Otherwise, runs the same as on Windows.
Doesn't start
Clicking Play results in the game running for a few seconds, then closing itself. No window ever appears. Using a cracked exe is NOT a proper fix. The GOG installer version does work when installed through Wine and run via DXVK through Lutris, so this is definitely a Steam problem.
gamemoderun
Audio didn't work on the native version. Switched to Proton 7.04, enabled gamemode, and it was just like playing on Windows.
RADV_PERFTEST=aco gamemoderun
Disable tessellation to prevent heavy artifacting.
The native port works well enough, but got literally double the frame-rate by using the Windows version + Proton (went from 45-50fps to 90-100fps). Had to disable tessellation, otherwise got major texture artifacting. Now performance is comparable to Windows.
Occasional flicker of the character shadows.
Disable "Next Generation Content" in the graphics settings (to eliminate stutter)
Any attempt to change graphical settings crashed the game. However, any graphical setting I was attempting to change would in fact be changed upon re-starting the application.
Also used the the launch parameter "mesa_glthread=true"
Do not attempt to Alt-Tab to the desktop! The game will not properly render after alt-tabbing back into it.
Long load times. Otherwise perfect.
Abnormally long loading times (15-30 seconds)
