Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Sounds like a UPNP or port forwarding issue to me. I can't help you troubleshoot your home environment. If, based on the messages I saw, I'll tell you right now that command line execution variables will NOT solve a network issue and I have 15 years experience in network engineering.
Good luck.
If you are seeing this in the main menu of TF|2 and have a 10th or 11th generation Intel CPU this is a bug which has a simple fix:
In the Windows Start menu on the bottom left search for "Edit the system environment variables" and open the program. In the "advanced" tab click on "Environment Variables..." near the bottom.
In System Variables (not user variables) click "New..." and add a new system variable where the variable name is OPENSSL_ia32cap and the value is ~0x200000200000000. Make sure to click OK to apply the changes. Finally restart your device and you should be good to go.
If you're on Linux, you can set the appropriate environment variable via env OPENSSL_ia32cap=~0x20000000 %command%.
Note: This issue is not exclusive to Northstar client but also affects the vanilla version, so if you only get it on Northstar there might be a different problem at hand as well. In fact it's not even unique to Titanfall 2 either.
https://steamcommunity.com/app/1237970/discussions/0/3081016749018656768/
> some guy makes a thread asking for help
> you respond by providing a totally generic and unrelated advice
> someone tell you that you're not doing anything useful & pretending to have skills that you surely dont have
> "muh stay mad"
you're a mad one, kiddo
when you have nothing useful to say it's often better to stay quiet
you should set that environment variable for the whole system anyway because it's a workaround to a CPU bug with OpenSSL, Titanfall 2 isn't the only game that is being affected
you can try setting up that variable only for titanfall 2 by using the following cli arg for the game : cmd /c "set OPENSSL_ia32cap=:~0x20000000 && %command%"
note that i cant test it because i don't own an intel cpu and i don't use windows
the command you mentionned in your first post :
cmd /c "OPENSSL_ia32cap=:~0x20000000 && %command%"
the command i sent:
cmd /c "set OPENSSL_ia32cap=:~0x20000000 && %command%"