Titanfall® 2

Titanfall® 2

View Stats:
opensll steam launch options
I have been trying to get my multiplayer to work using the steam launch options (I am hesitant to shut part of it down for my whole pc) but can only get a black box to appear momentarily than nothing happens any help to get this working would be appreciated

cmd /c "OPENSSL_ia32cap=:~0x20000000 && %command%"

thats the one i have been using have also tried 200000200000000 to the same results
Originally posted by Kyral:
https://r2northstar.gitbook.io/r2northstar-wiki/installing-northstar/troubleshooting#intel

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/
< >
Showing 1-11 of 11 comments
`digitaL.braVo Dec 6, 2023 @ 2:23am 
So I did my best, because you didn't provide an actual error message, by searching what you've changed and it seems to imply "Can't find data center, can't launch multiplayer"

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.
The author of this thread has indicated that this post answers the original topic.
Kyral Dec 6, 2023 @ 4:09am 
https://r2northstar.gitbook.io/r2northstar-wiki/installing-northstar/troubleshooting#intel

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/
Kyral Dec 6, 2023 @ 4:18am 
Originally posted by `digitaL.braVo:
So I did my best, because you didn't provide an actual error message, by searching what you've changed and it seems to imply "Can't find data center, can't launch multiplayer"

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 had 15 years of network engineering you'd be able to tell that his command is wrong and does nothing useful. you should be able to tell as well that the issue he's facing has nothing to do with port forwarding or his home environment
jordanleemn Dec 6, 2023 @ 1:47pm 
Originally posted by Kyral:
https://r2northstar.gitbook.io/r2northstar-wiki/installing-northstar/troubleshooting#intel

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/
Ya that's the problem I was hoping to avoid modifying an environment variable as I can't find what risks that might bring although after my initial post I did find something from Intel saying what that variable does and it seems to just disable some processor acceleration programs so I probably will just use the environment variable
`digitaL.braVo Dec 6, 2023 @ 4:29pm 
Originally posted by Kyral:
Originally posted by `digitaL.braVo:
So I did my best, because you didn't provide an actual error message, by searching what you've changed and it seems to imply "Can't find data center, can't launch multiplayer"

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 had 15 years of network engineering you'd be able to tell that his command is wrong and does nothing useful. you should be able to tell as well that the issue he's facing has nothing to do with port forwarding or his home environment
lol stay mad I didn't Google his issue for more than 2 seconds based on his vague description.
Kyral Dec 7, 2023 @ 4:41am 
Originally posted by `digitaL.braVo:
Originally posted by Kyral:
if you had 15 years of network engineering you'd be able to tell that his command is wrong and does nothing useful. you should be able to tell as well that the issue he's facing has nothing to do with port forwarding or his home environment
lol stay mad I didn't Google his issue for more than 2 seconds based on his vague description.

> 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
Last edited by Kyral; Dec 7, 2023 @ 4:51am
Kyral Dec 7, 2023 @ 5:01am 
Originally posted by jordanleemn:
Originally posted by Kyral:
https://r2northstar.gitbook.io/r2northstar-wiki/installing-northstar/troubleshooting#intel

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/
Ya that's the problem I was hoping to avoid modifying an environment variable as I can't find what risks that might bring although after my initial post I did find something from Intel saying what that variable does and it seems to just disable some processor acceleration programs so I probably will just use the environment variable

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
Last edited by Kyral; Dec 7, 2023 @ 5:03am
jordanleemn Dec 7, 2023 @ 10:15am 
I have applied the whole system one now and that one just for titanfall 2 is what I was putting into steam launch options was I supposed to put it somewhere else?
Kyral Dec 7, 2023 @ 12:27pm 
Originally posted by jordanleemn:
I have applied the whole system one now and that one just for titanfall 2 is what I was putting into steam launch options was I supposed to put it somewhere else?

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%"
jordanleemn Dec 7, 2023 @ 3:06pm 
Oh I see when googling I came across cmd /c or set but nothing with both I won't be able to test anything for a few days but I am interested if that one works
jordanleemn Dec 10, 2023 @ 1:47pm 
Tested and it seems to have the same result of a black box appearing momentarily than nothing
< >
Showing 1-11 of 11 comments
Per page: 1530 50

Date Posted: Dec 5, 2023 @ 8:11pm
Posts: 11