oho
Published
env OPENSSL_ia32cap=~0x20000000 %command%
Crash without launch command env OPENSSL_ia32cap=~0x20000000 %command%
This is another EA game that requires the OpenSSL related launch command to stop crashing. Most likely wont help though if you have some other CPU than 10th or 11th gen Intel. https://www.intel.com/content/www/us/en/developer/articles/troubleshooting/openssl-sha-crash-bug-requires-application-update.html
On dimly lighted scenes particles (footstep dirt and underwater air bubbles etc.) would cause bad artifacting which made the game unplayable. However on well lit/sunny scenes no problems at all
Wierd problem where control input would rapidly change in between keyboard/mouse and xbox 360 controller and also the mouse cursor would "drift" to top left corner. This also happened when controller was turned off. Short video demonstrating the problem: https://youtu.be/aJyDZYW1FqA
Initially solved the problem by switching proton version but trying to deal with the graphics artifacts the problem came back and couldn't no longer get rid of this issue (nor the graphics artifacts)
Works great
Reported this game before where I had graphics problems that were actually caused by messed up GPU drivers, now everything with this game works extremely well! 5/5
Launching the game is a big hassle. I clicked play on steam for the first time today and it took about 30 minutes of work until I got to main menu. Initially it hang on "Connecting to Origin". Second try it was stuck on blank white Origin screen. Third try it it launched the game but froze up and crashed and it was the fourth try that I made it in to main menu.
Definitely not great if you just want to play one match BF real quick. However the game runs great when you finally get it going.
FairFight
Native version doesn't recognize both controllers. Using Proton it would detect both controllers.
Using proton it usually crashed when loading into a new scene (completing dungeon etc.) Extremely frustrating as it would lose the just completed game progress. Wouldn't have been a major issue if it would save the game just before loading the new scene.
Couldn't play local co-op in native linux due to controller detection issue. Couldn't play with Proton either because of the occasional crashes that would lose some of the game progress.
Playing alone or with online co-op would probably work in native linux, wasn't an option for me because I would only play this game local co-op.
If you have G29 you need to use older version of proton. For some reason newer proton versions do not have force feedback for G29
Launcher broken, game cannot be started
Now that original FFXIV launcher is broken (again) XIVLauncher is needed to play the game. However I have a problem where if I hold mouse button(s) down it doesn't register most of keyboard input.
As I have played MMOs for +10 years so that I run and move my character by holding mouse buttons down the game is currently unplayable for me.
I am on multi monitor setup and moving the game to other monitor would not work as the game stayed locked to the primary monitor. The monitor which I wanted game to be on had to be set as primary before launching
I am using wireless Xbox 360 controller and I believe the input seemed to be just slightly delayed. Might be that the NFS Payback car controls itself are a bit wonky which made it seem like there would be input delay, don't know for sure
Constant slight stuttering, disabling esync seemed to help but still very unpleasant to play
If you really really need to play this game I think it is possible. But I personally had too much problems with it to be a pleasant experience
Use Proton! Native linux seems to be a bit broken, window/fullscreen issues and xbox controller doesn't work in native version.
Works just fine using Proton
Runs great, see below if you have newer Intel processor and stuck "Data center searching"
10th and 11th gen Intel processor have been known to cause OpenSSL issues with software and games that are running ancient version of OpenSSL, such as Titanfall 2. If you are stuck at "Data Center Searching... Contacting Respawn servers..." you need to set Steam launch option "env OPENSSL_ia32cap=~0x20000000 %command%"
Details about this here: https://www.intel.com/content/www/us/en/developer/articles/troubleshooting/openssl-sha-crash-bug-requires-application-update.html
