Titanfall® 2

Titanfall® 2

Not enough ratings
Fix Titanfall 2's Multiplayer not connecting & being locked
By CobraTee
100% guaranteed fix for Multiplayer being Locked & saying "Connecting to datacenter"
   
Award
Favorite
Favorited
Unfavorite
Introduction
So, you just want to play Titanfall 2's amazing Multiplayer but you've loaded the game and Multiplayer is fully locked and you seem to never connect to the data centers?

Yeah.... same here, but not anymore!

Why is this happening?
The issue with Titanfall 2's multiplayer is largely attributed to a combination of the games Engine and configuration issues on your system. One major factor is the use of outdated or incompatible cryptographic libraries that cause connectivity issues with the game's servers, which may prevent you from properly accessing online multiplayer features. Specifically, the game utilizes OpenSSL, and some versions of OpenSSL have compatibility issues with modern systems or certain configurations, leading to connectivity disruptions.

People have also reported that system environment variables like OPENSSL_ia32cap - which controls certain cryptographic operations, can interfere with the game’s ability to communicate with the servers properly. This has led to many users needing to manually adjust global Variable settings in their system to bypass these limitations, which in turn can cause issues with other programs that do use OPENSSL_ia32cap perfectly fine.


How do I fix this?
There's 2 different ways that I know can work to fix this issue once and for all.

*The first way IS NOT guaranteed to fix the issue for everyone!

The first way:
After having this issue myself I went online like everyone does and came across so many people saying to edit a global variable called "OPENSSL_ia32cap" and then restart my system, which I honestly didn't want to do as it will affect other programs and cause slowdown or in some instances cause things to struggle. For the purpose of giving people Options ill list the steps down below.

Open “File Explorer” (Win+E), right-click on “This PC”, and select “Properties”
Select “Advanced System Settings”
Select “Environment Variables” in the “Advanced” tab
Select “New…” under “System variables”
Input the text below and select “OK”

Variable name: OPENSSL_ia32cap
Variable value: ~0x200000200000000

Restart your system and it should be working...

The second way:
Now, I wanted a way to change this variable and ONLY change it for when i want to play Titanfall 2 and have it automatically delete the variable after exiting the game. I didn't want to potentially slowdown other things just for Titanfall 2's Multiplayer, so the following is what I came up with:

I've made a .EXE that when run, opens a Powershell window and asks for your Steam Directory before anything actually happens. Once you've provided your Steam directory, the directory will be saved to a config JSON file located inside a newly automatically generated folder called "Titanfall 2 Launcher".

This folder can be located here:
"C:\Users\USERNAME\AppData\Roaming\Titanfall 2 Launcher"
NOTICE: You will NEVER need to interact with this folder at all.

After this the Powershell Window will then tell you exactly what it is doing every step of the way, the following are the MAIN things that happen:

Save user provided Steam directory to a config file,
Make the OPENSSL_ia32cap and set the Global value to 0x200000200000000,
Confirm OPENSSL_ia32cap has been set and updated,
Check if steam is running and if so it will close the process of Steam and restart Steam,
Wait for Steam to restart before continuing,
Load Titanfall 2,
Wait until the process of Titanfall 2 has closed,
Delete the OPENSSL_ia32cap global variable,
Restart Steam.

This sounds like alot but its really not, it does this all autonomously only needing you to provided Steams directory on the first ever time you use the program.

I wanted to make this fully automated and as easy to use as possible.
Why does your way do what it does?
The reason I made this was to avoid potential issues created by making the Global variable of OPENSSL_ia32cap and always having it active.

To me, it wasn't worth potentially slowing down my PC and applications due to having this Variable set Globally full time.

I'll explain why we do what we do:

Why save my directory?
We save the Steam directory to a Config file so that we don't have to enter it every time we want to play Titanfall 2, but also so I could share this to the public a lot easier considering hardcoding a directory WILL NOT work for everyone as everyone has things installed in different places.
For example, Some of you might have Steam installed to C Drive but mine for example is Installed on my E Drive.

Why do you set and delete the OPENSSL_ia32cap this way?
I set it this way for a few different reasons.
  • Firstly, this way its not always set and is deleted on exit of Titanfall 2.
  • Secondly, this way other applications that use this Variable without issues, can still use it.
  • Thirdly, deleting the variable on process close makes it so nothing is slowed down or restricted.
  • Lastly, I'm cool

Why do you close steam when its already running?
I done this mainly to make sure that Steam and Titanfall 2 can fully make use of OPENSSL_ia32cap as without a full stop and restart of the Steam & Titanfall 2 processes, Multiplayer will still continue to not work even using this.

Do I need to keep Powershell open whilst playing?
YES! please do NOT close Powershell, mainly just to make sure that the variable gets deleted properly before fully closing and restarting Steam after Ending Titanfall 2's game/process.

How do I use this?
Simple, open the exe and give it your Steam directory and let it do its thing.
Download
Head over to this Link[mega.nz] and download the EXE file

NOTE: If for whatever reason you can't open that link, either copy and paste this in your browser:
https://mega.nz/file/yroEBYaR#InnBYEWSm7WzDUqah2amYnRuYFRU8ZCWqIVqrVESO58
OR just right click the white "Link" text and click "copy link address" and open it in your browser.

NOTICE: If the EXE doesnt open a Powershell windows and instead either flashes or doesnt show at all, right click the exe, go to Compatibility and make sure you tick "Run this program as an Administrator".

Just download the exe file, save it somewhere ( i have it in my Titanfall 2 Directory alongside the official EXE) and right click onto the .EXE file you downloaded, and click "Show more options" and then "Send To" and make a desktop shortcut for the Titanfall 2 Launcher.
Whenever you want to play Titanfall 2, whether it be Campaign or Online Multiplayer, use this EXE to load the game and you'll always be connected to the DataCenter and ready to play Titanfall 2's Multiplayer!
Credit
I worked on this fix alone, and to understand what the issue was i used multiple online posts detailing that it had to do with the SHA Variable.

If this was useful to you then please, leave a comment, like or an award. I worked on this for a good amount of hours before finalizing it and then another 2 hours writing all this whilst performing tests and making the code more efficient.

Credit to:
Myself (CobraTee),
Users on Reddit,
EA's Forum Users,
Steams Discussions Forum.

ENJOY
11 Comments
CobraTee  [author] 26 Aug @ 11:03am 
I'm glad i could help you W4J0R.
W4J0R 25 Aug @ 9:34pm 
Hello, thank you very much for the guide !
CobraTee  [author] 22 Aug @ 8:54am 
I am glad that i was able to help!
[KOLA] Kohllah Studios VT 22 Aug @ 8:49am 
literally saved the game for me. years thinking the servers were dead turns out that my computer cant talk to the servers.
CobraTee  [author] 18 Aug @ 8:43am 
TheMajesticBear thank you i appreciate you, the only thing i will say is maybe change over to using the second way. i explain why in my post but yeah, either way glad it works
Themajesticbear 17 Aug @ 7:08pm 
+rep, 1st way fixed it for me, W author
CobraTee  [author] 12 May @ 2:54pm 
Thank you for replying and giving your feedback. i will make a Github Repo so that people can check the source code so that they feel alot better about it. Im very happy that its managed to help you. have a good time playing dude!
Kirchberg 12 May @ 10:45am 
I have used launcher, it was very informative that you wrote each step that script is doing in console. I didn't have any issue (only needed to run as administrator).

You made a good work, you should make it on GitHub so that every user didn't get suspicious about the content of the .exe file
CobraTee  [author] 11 May @ 6:59pm 
& if you used my Launcher fix, which i hope you did for better all round stability, can you comment on how its performed & ease of use?
CobraTee  [author] 11 May @ 6:57pm 
not a problem dude, i hope it helped you out... did you go with the 1st fix or my Launcher fix?