Saint Demon
Published
gamemoderun gamescope -w 2048 -h 864 -W 2560 -H 1080 -F fsr -f %command%
Used slight FSR for some smoother thermal GPU performance
As explained here https://github.com/ValveSoftware/Proton/issues/641#issuecomment-487423565 except prolly no need to bother with being this sophisticated with killing the game in #4. Following this exact post will spare you doing things that are not really needed.
The game apparently happens to appear under various numbers. The thread I linked mentions 33340 and 33350, but my Anno installation appeared under 33250. I followed the above steps for it and apparently it worked, too. Take a note of that just in case. Overall the game seems to work pretty much great just once you get it running.
Used mf-install, it didn't take any significant effect though. Neither Glorious Eggroll seems to do.
Respawning in checkpoints and using saves that are not loading chapter beginning kill most of the audio for a significant amount of time
You won't play without using workarounds described under this link https://github.com/ValveSoftware/Proton/issues/2081#issuecomment-450017977 Launch parameter lets you pass to the menus, the config tweak lets you run the actual game.
Easy Anti Cheat
Confirm.
In other words: EAC is simply being difficult.
Still displays an in game window about EAC
Clicking confirm still throws you out of the game
This game starts up once you use the Wine D3d11. It runs very smoothly in menus. There is no problem to run a mission either. And all that is for nothing as the in game FPS is like 3 times lower than when you run the game on Windows, which is 30-40 fps out of combat. But once the combat starts the frames drop like beat in some hardcore techno, or rather stuttering kicks in very hard. It's absolutely unacceptable in a game, which demands so much timing. Wanted to give it a borked, as for me it is barely playable (until you play it for sightseeing), but hey, it runs somehow after all. Gotta mention it kinda looks like there's a huge problem with using the power of the hardware, I've noticed my gpu temperatures not really getting above the idle, while I believe it still should warm it up a lil bit.
Performance is very solid, happens it dips quite strongly for short moments though. Stability wise, it's weird. I started by updating proton to 5.0-1, the game had trouble even passing to the rendered stuff (in game, benchmark etc.) After tweaking a bit, Fsync option seemed to help and now the game and benchmark would work. After some time it would freeze or throw you out back to desktop. Any loadings were a huge risk of the game's suicide as well. Made some more tweaks to throw something more that would hopefully work. Once I used Large Address Aware, the game turned pretty much stable. I could pass the 12th mission, run the benchmark again, no dying. Overall it turned stable. Then wanted to disable these settings to track what exactly each one does. Weirdly though, after doing so the game would boot like normal, launch the in-game or benchmark and run it without crashing. After more thorough testing though, it seems like when I have Fsync off and LAA, it indeed prevents freezing.
I think happened I saw shadows glitch, wouldn't bet though. Not that easy to focus on observing this.
Alt-Entering it and returning back would leave the game stretched. Attempting to fullscreen it back will black the window then and leave the game not responding.
Occasional, yet pretty deep stutters.
As described before, initially it would crash a lot, prolly not letting you pass a mission.
Doesn't work
I bring nothing new. Basically won't boot to show anything, the process just shuts down. No luck with trying launch options either.
If no anti cheat gets introduced to the game, it should work just great. Nearly.
Happens the game just kind of freezes after the stage, stop recording any input, or just keeps searching for a game and never finds it. Restart necessary.
Rest in EAC
Game boots up with no problem, menu seems to be functioning well. Can't start playing though - anti cheat couldn't be initialized.
The EAC issue still remains
You can browse the menus, but you still cannot enter as EAC is said to be not initialized.
Version 3.7-8 crashes when autosaves happen, but enabling the 3.16-4 beta fixes the issue. Everything seems to work nicely. Framerates on my setup and max settings are around 30-45, which seems good enough at least (I have no comparison to native Windows performance here)
Game itself works just the way I remember native Windows
Spacing of text in item descriptions doesn't work correctly, so it ends up being messed up together with titles (some of them being also placeholder names). Hover popups don't detect window edges and disappear behind them. I think it was not an issue in native Windows.
You can totally live with any issues I experienced, they don't affect gameplay.
Simply flawless.
I wish I could test the multiplayer, but so far no luck finding someone online, nor my friends play the game.
gamemoderun MANGOHUD=1 DXVK_ASYNC=1 PROTON_NO_ESYNC=1 PROTON_ENABLE_NVAPI=1 WINE_CPU_TOPOLOGY=8:0,1,2,3,4,5,6,7 %command%
Tried installing Bink Video codec, as pcgamingwiki suggests it's used by the game, even if the cutscenes look apparently rendered on the go.
When Aloy starts running away from the kids in 2nd cutscene, there's foliage struck with strong light. This light flickers when is visible. In fact, a lot of lit foliage seems pretty grainy and noisy, too.
Framerates not exceeding 20 by a significant margin, mostly 18-ish
In 2nd cutscene, when Aloy stumbles and falls into a pit, there seems to be something special going on, as usually in the same specific moment, with exceptions scattered by a few seconds, game goes frozen. And it seems to have some hate for Plasma as well, as often the system freezes and is not recoverable, but happens that with mashing of alt+tab and meta key, control over mouse can be regained and shutting the game down from Steam level generally works with no problem, but Plasma still doesn't survive intact (losing task manager icons among many other issues) and has to be restarted in order to work normally. The freezes occur also after skipping the cutscene and are nearly instant after the cave scene gets loaded. One time though, after reading a post-cutscene save the game actually kept going. Did not use it much, I tried to go through cutscene again hoping that I made an actual fix to the problem through some proton version or launch option. In fact I didn't.
Tried both proton experimental and GE, tried launch options suggested in previous reports, additionally started experimenting a little with the CPU Topology option to make my hardware maybe a little more similar to Deck or PS4 core count wise in hope that it actually helps. Could not get a consistent positive result with the freezes.
gamemoderun WINE_CPU_TOPOLOGY=16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 %command%
Use ProtonGE so the game plays the startup video stuff, otherwise only a colorful placeholder displays.
The game ran in 20-45 FPS on my hardware, barely ever crossing 30% of GPU utilization reported by Mangohud. It did feel a bit sluggish, but was perfectly playable. Enabling ProtonGE FSR only made the game blurry and oddly, halved performance. After some research I stumbled upon a thread with a fix
https://www.reddit.com/r/linux_gaming/comments/nqwkaq/proton_low_gpu_utilization/
It appeared to work, apparently the game is made in Unity and does not really like SMT, which is fixed by WINE_CPU_TOPOLOGY launch option. In order to use it, learn about the number of cores/threads in your Ryzen CPU (can't speak for Intel). On my example, I have a 16/32, so after the equal sign I put number of cores (16) and after colon I list the 16 cores, but starting from 0 instead of 1, hence WINE_CPU_TOPOLOGY=16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
For 8/16 Ryzen CPU use WINE_CPU_TOPOLOGY=8:0,1,2,3,4,5,6,7 and so on.
Enabling it pretents around 3-4 times performance boost
The game is perfectly playable without the fix, but the feeling of smoothness coming from framerates is quite unsatifsying, even if just a rather minor inconvenience (speaking as user of a 75Hz screen)
Doesn't start
Tried running the game with various launch options set, KDE system monitor ended up displaying the process is a zombie every single time though
Now this plays quite well
I was able to pass 2 bosses and die from the 3rd miserably. No issues noticed.
Good alternative for the Linux native which doesn't work anymore
Performance likely to be considered correct considering my GPU. No stability problems as long as I remember.
Note: mentioned Proton version used for around 3 hours, around 40 on previous Proton versions. It works very similar since then though. Game works pretty much perfectly (enough), a few things, which don't really affect the experience should be noted though: there happen sound glitches, like it gets cut into a few pieces, FPS drops significantly when you get hit by some melee enemy attacks, the average FPS seems lower than while playing on Windows, but even if so, it's high enough it's not any bother anyway. Overall the game is super playable, so just shoot some demons and have fun with it.
Install and run this pretty much like it was native and play. No actual problems in-game I guess.
Doesn't start
The game would show splash screen, possibly display a black rectangle in top left quarter of screen, but after 30 seconds or so, it would just shut down. Tested with Proton 5.13 and 6.1-GE-2
gamemoderun %command%
Probably a part of Paladins experience
All probably not varying from the basic Paladins experience
Anticheat in the game is alive and kicking
Practically out of nowhere, without restarting the game, downloading patches etc. the game started kicking me out of matches, which first occured around 16:00 cest 11.06.2022. No luck switching experimental to eggroll, restarting, reinstalling and so on.
gamemoderun %command%
Lack of support as usual, kicks out of the match
As far as I could tell from running around the shooting range, it seems to work
I am very confused, as the last two months in this game's section is a solid BORKED wall. For me the game works. I can log in, set borderless window, can tweak loadouts, run through the interface, test champions on the shooting range, play with players against bots and finally play with players against players, it all works (botvp and pvp around 4-5 games summed up). Just did not try ranked games, cause I haven't gotten to that overall yet. The game is playable overall, but once again I probably have to blame my CPU for being ancient here, so protoning the game eats up some FPS. My native Windows (8) is around 70 I think, here it is half slower, with drops to 19 which is pretty much right above the red line which borders a somehow comfortable gameplay. But overall - it works and deserves a Silver from me I think. Also worth to mention the tweaks I tried. PROTON_USE_WINED3D made the game wreck on start, but PROTON_NO_ESYNC might have helped (but I admit I did not exactly test that reverting back to no esync disabled), cause originally using skills for the first time during the match was causing short, but hard framerate drops. The other time I attempted playing with no esync the drops were gone. Take it as a possible yet not confirmed thing to improve performance in the beginning of the match.
gamemoderun %command%
In the starting cutscenes there was a moment, when some elements visibly took a fraction of second to load after displaying the scene, so that might be slower. Happened just once though.
Besides of games own inability to find players for a match, it just worked.
Turned all of the settings to highest possible and performance was solid, it seems with GPU's coils playing melodies of triumph. Did not use Mangohud, so did not have any insight about what the actual framerate was considering all mentioned before.
Perfectly playable
Alt-tab would cause behavior like weapon auto firing when starting a new round in round based game modes, each next round included. Click fire to stop it when it happens
None of the above eliminated encountered difficulties.
If WINED3D used playable game renders somewhat dark and brownish, hard to navigate through the level. Default Vulkan render runs fine.
Probably shader caching, but too little gameplay to judge
In the 2nd tutorial the game just stops on black screen and won't load any further.
tl;dr: EAC will let you through to start tutorials, but second tutorial won't fire up (can't bet right now, but I think that one was just a video tutorial course? Perhaps that's the source of problem.)
Surprisingly you can play online matches in this game despite EAC
Occasional stutters
99% native experience I believe.
Might happen it'll freeze when you want to quit the game and needs to be nuked from process table. Very rare though.
I believe, as I simply did not have any reason to run this game on Windows. I play it using proton for 360 hours already through a few software and hardware configurations. For all this time the experience is great in general. Tested both in single and multiplayer. Rock solid.
gamemoderun DXVK_FRAME_RATE=75 %command%
Looks like sometimes in certain places under a certain camera angle part of texture/geometry can go wild "twitching" back and forth
No problem with multiplayer as usual
While on the Radeon I could experience framerate drops when displaying the blue/celestial/gold portal and a long string of launch options could partially patch it, killing Steam overlay with it, on Intel I just stuff gamemode and 75 frame limit to DXVK in (because of my screen refresh which can't be set to 75 in game) and the experience I had so far is brilliant as far as I don't play on Wayland, as it causes game freezes. But that seems to be more of a global issue for games on ARC?
EAC
The game runs just to show an in-menu window saying anticheat couldn't be initialized. Thank you for your time.
The game itself works
In 2nd task of the tutorial you'd be told to come to the cliff, but once you approach there's no more guidance appearing and the progress can't be pushed further
There was nothing much I could see not working gameplay-wise as long as I could play. What probably is the work of anticheat though, is you can never fall to the ground crushing your pretty face, cause the game will suddenly display that it "couldn't connect to the server" or so. Let's wait for 5.11 kernel to kick in, there's a great potential
Flawless, except slight windowing/input issue if you're impatient
I am not all certain about the mechanism behind this, what I managed to find out is that if you run the game and alt+tab it while still in loading splash screen, to run streaming on Discord for example, after you return back to the game you'd end up with the interface buttons not responding left click. Seems like some alt+tab shenanigans are able to fix this without restart though?
Mentioned in windowing issues
Sometimes I had a feeling there were very gentle microstutters or some general lowered framerate, but in fact I often happen to play with a number of apps opened in background plus Discord streaming and OBS recording with kinda balls to the wall bitrate, while I kept the maxed out graphics settings. Might be a totally normal behavior to expect for those conditions, so take that with a pinch of salt.
Just letting you know that you might want to try running the game with Proton Experimental
This solved for me the inability to connect to Steam in the game, encountered with up to Proton 6.3-X, which was preventing the game to continue to the lobby.
5.11-GE-3-MF GloriousEggroll
Included in Glorious Eggroll Proton, fixes cutscenes not playing
Default proton keeps the bug in Ripto's with jump and fire attack not working, the Glorious Eggroll fixes the issue.
Default proton works with no issues. GE crashes on fire attack if RADV_PERFTEST=aco %command% is set. Using default radv keeps the game stable.
Played through the first game with default proton, used GE for the second, playing for over 2 hours.
Proton support not enabled apparently
The game did not start at all with the auto setting for proton, after picking experimental it would remain in black window for a few moments and close down.
Necessary to make Origin and the game run, more details below
I have to thank guss77 for his report, as while it wasn't really making a lot of sense in the first moment... it's certainly what made Origin do anything at all.
To keep my procedure clear and tidy...
...Below I present the steps which made the game run for me:
(excluding steps which clearly didn't help and were misleading)
- Download the game as usual
- Right click the game in your library, enter properties. In launch options insert
PROTON_USE_WINED3D=1 %command%(we will need that after Origin) - Shut down the current Steam instance and open terminal
- As suggested by guss77 enter a command
PROTON_USE_WINED3D=1 steamwhich should open Steam back for you - Click play, Origin should start sooner or later now and do some config for itself. In my case it ended with something like a request to restart, accept the prompt
- Shut down this Steam instance and open the usual Steam
- Run the game again and soon it should start without any problem (that's where the line from step 2 kicks in)
I have to point out that sometimes the game might not want to start, like get stuck on the loading screen. Otherwise, my sister played the game for a few hours on her machine and didn't complain about any problems.
Just if it doesn't break down for you weirdly, it seems great
When first installed the game was working correctly for me, but after just restarting the game, it was not booting up after Origin. It was like play and reinstall to play again. Can't exactly say what I did to make it work, but it started working again after some popup window clicking in Origin. Can't provide exact info though, you'll need to figure it out by yourself in case you encounter the issue.
Only displays a black ~250px squarish shape in the middle of the screen
Seems to do absolutely nothing other than that
