Mr. Brewski
Published
I've played 8+ hours at max settings. Game play is buttery smooth. No issues at all.
No issues with the game at all, runs buttery smooth and has not crashed once. My Steam overlay does not work, however. It will open but flickers constantly and my mouse cursor is not visible within the overlay.
Apart from the audio missing in one cutscene, it has been perfect. Using Nobara distro.
Audio missing from one cutscene
Install Proton EasyAntiCheat Runtime
Once the Proton EasyAntiCheat Runtime is installed it was smooth sailing.
I hope to see more penguins in the Bayou.
Perk progression has carried across perfectly (was being wiped under previous versions) and server browser no longer crashes the game. Performance is equivalent to Windows, none of the stuttering reported by other users. I played a couple of rounds online and offline, no issues. Steam overlay works but I cannot see the mouse cursor for some reason.
EAC - no multiplayer
The game runs without an issue. I was hopeful with the Operation Greyhound update that they had "ticked the box" to allow Linux gamers to use EAC. At this point in time they have not, and I get an EAC error on startup. I expect this will eventually change seeing as Squad (owned by the same company) works perfectly on Linux.
I had to run this command to get EAC to launch -
cd "//steamapps/common/Rising Storm 2/Binaries/Win64"; %command%
Once done, the game launched without a problem and appeared to be running quite smoothly. I tried out the training mode for a while and didn't have any problems at all. Once I tried to join a server, I was booted with an EAC error (no sandbox). This would easily be a Gold rating if not for the EAC issue when trying to play online.
Version 1.3 update I kept this command in from last time to get EAC to launch - cd "//steamapps/common/Rising Storm 2/Binaries/Win64"; %command%
After hitting play it started without any problems. I didn't even get the "Init failure code 3" error message, just the little splash screen and then straight into launch. I joined a server and played half a round of Saigon and another half a round of the Mamayev remake (I think it's called DMZ or similar). At all times it looked good, it sounded good, and it ran well. The leaning mechanic is amazing and very welcome to the game, I just wish they had a toggle option.
The only small issue was there seems to be an odd shadow flickering thing on all of the grass. It doesn't affect the game play at all, just looks a little odd and it was like that on my machine before the 1.3 update anyway.
The launch command is no longer required to get EAC running, and there are no error messages at launch. This game now runs perfectly out of the box, no tweaking required.
Played through tutorial and numerous battles, absolutely flawless.
It works flawlessly out of the box. All of my saves came across and I raced two tracks using an Xbox 360 controller without any issues.
This is a tough one to rate because the game itself runs perfectly out of the box. I clicked 'Play' and it booted up no worries at all. I fiddled around in settings, changing graphics and key configs for a while and then spent a good chunk of time running around in the firing range. There was a tiny bit of lag when I first loaded in as the textures were catching up, but once that was done it was smooth sailing. No problems with sound at all either. I used a variety of guns and spent some time working through the CQC area. I did not have a single issue the entire time. However, and it's a big however, I was kicked immediately from every server that I tried to join. EAC boots straight away and gives the 'dummy client' reason. The game itself scores a Platinum rating because it ran without any issue whatsoever. The Borked rating is wholly and solely because of EAC and, being that Squad is a multiplayer only game, it effectively makes the game crucially unplayable. As previously stated, the training mode works perfectly well, but who is going to want to spend more than 15min or so firing at targets? I wasn't able to find any non-EAC servers to test the ability to join.
I had to rename the video folder as others have described, but it was platinum performance other than that. Go here "/steam/steamapps/common/Squad/SquadGame/Content/Movies" and change the folder name to something other than "Movies" (eg MoviesOld) and you're good to go. I'm running at mostly high settings in 1440p and generally hovering around 40-50fps, which is comparable to my Windows performance. One extremely happy Linux gamer right here ^-^
Alpha 13.1 patch released today and from the changelog - "Fixed an engine crash that happened if required files to play the introduction movie were missing." It is no longer necessary to change the name of the Movies folder. Instead of playing an intro, there will be a momentary black screen and then you will reach the menu screen. This game no longer requires any tweaking whatsoever to play, multiplayer continues to work and performance (for me) is very good. It now plays perfectly out of the box.
I have connected to two different servers and played a number of matches in a row on both, with no issues.
It runs as if it were a native title - solid frame rate, no jitters and no problem with audio.
When I launch the game without any launch tweaks it gives me an error pop up stating that the game has crashed and telling me it has made a log in a crash report folder. Once I click ok, the dialogue box disappears but the game continues to run, according to both Steam and System Monitor. It never appears to actually launch and I end up either sigkilling it or closing Steam. One time it randomly did launch and seemed to working fairly well from what little testing I could do, but I have not been able to reproduce that launch. I have tried disabling Esync, D3D11 and using Wine D3D11 but all have said that they were running in both Steam and System Monitor without ever launching, the difference being that they all lacked an error pop up.
It runs quite well, audio works without any hitches. There are occasional graphical artifacts but I only saw them in the menu, they would flicker and then go away. Xbox 360 controller detected instantly. I played the tutorial without any problems. Last time I tried to run it I couldn't even get it to launch, now works perfectly. Great work Proton!
Initially got the "DirectX11 failed to initialise" error. I tried to disable Esync and D3d11 in the launch options but they both failed to launch. After forcing it to use Wine D3d11 it launched but the launch window was empty aside from hyperlink options "Play", "Settings" and "Support". After clicking Play, it launched straight away and went through the splash screens without issue. Upon reaching the main screen, the menu options all appear perfectly but the background picture appears to be 3D models without any textures on them, all just shades of white. I played a solo horde mode and, while it appeared to perform very smoothly, it had the same issue as the main screen. Most areas of the map and the characters lacked any textures at all, but some of the areas of the map that were deep in shadow were displaying correctly.
In my previous report using Proton 3.16-4 I needed to force Wine D3D11 to get it to run, but the launcher was really ugly and most of the textures were missing. I tried it again this morning and removed the command forcing Wine D3D11 and it works perfectly, aside from the launcher which still looks really bad. There were a couple of micro stutters when I first loaded in but after about a minute it was smooth sailing and not a single hiccup with sound.
