Re: Titan Fall 2 "data center: searching" message
As the title says, I am attempting to play Titanfall 2, but I cannot connect to the servers. When attempting to join multiplayer, I am met with the screen shown in the screenshot attached to this post. No matter how long I wait, the servers do not connect.
As discussed in the now closed post here: Solved: Infinite data center searching titanfall 2 - Answer HQ, the problem seems to lie with newer Intel processors. I won't go into the technical details as to why this occurs here, but since the link in the proposed solution is now invalid, I will summarize the standard fix below:
Windows/Non-Steam Fix:
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
Steam Fix:
Right click in Steam, click Properties, and paste the following into Launch Options:
cmd /c "set OPENSSL_ia32cap=:~0x20000000 && %command%"
The proposed solutions do not solve the problem for myself, and I'm sure many others, and here is why:
Computer-Wide/Non-Steam Fix:
- Caps speed for other online applications that would normally take advantage of the better processors
- Can cause some applications to crash
Due to these two problems, someone like me would have to change the environment variable, restart the computer, then change the environment variable back, and restart the computer again if I wished to play Titanfall 2 and then switch to another application. I have also heard some talk of this not working for some people, but I am unable to confirm the validity of their claims.
Steam Fix:
- Does not work for some people
- As of posting this, the reason this doesn't work for some people is unknown
- Can leave a lingering command prompt in the background
If the Steam fixed worked for all people, I wouldn't have a complaint, but it doesn't work. The Steam fix would change the environment variable for just the process the game is running on, leaving the rest of the computer to run as usual, solving the problems of the Non-Steam Fix, but if I perform the fix, the game no longer opens. No error code appears to say why the game failed to open; it just simply never opens. To people who are able to find success with the Steam fix, the lingering command prompt window can make some people uncomfortable.
This is not a new problem, as seen in forums going back several years discussing this issue. I will continue to troubleshoot what I can, but I have found no viable solutions so far. While I understand there is more to this problem than "Just fix the servers," I still have to raise the question: What can EA and Respawn do on their end to fix this widespread problem?
For those willing to try and find a viable solution, I have included a DxDiag text file in hopes it will help in the search.
