Skip to content

Commit

Permalink
Remove ~ that people keep putting in the system variable (#224)
Browse files Browse the repository at this point in the history
For the record, `~0x20000000` clears the 29th bit of the result from cpuid, while `0x20000000` replaces the result with one with just the 29th bit set (OPENSSL_ia32cap.3). The 29th bit represents the Intel SHA Extensions.

As such, if the second one (without the ~) works, the actual solution has nothing to do with the 29th bit; it's one of the others.
  • Loading branch information
JMM889901 authored Jul 6, 2024
1 parent bfcaf44 commit a69afc5
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/installing-northstar/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,9 +80,9 @@ On newer Intel CPUs you might see a message like this
If you are seeing this in the main menu of TF|2 and have a 10th generation or newer 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.
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%`.
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.

Expand Down

0 comments on commit a69afc5

Please sign in to comment.