60 replies to this topic

[CptnMunch]

MrVaad, on 01 December 2021 - 12:06 PM, said:

Sadly, you can't do anything on your side (except applying the workaround)

OpenSSL is a free library to encrypt data. It's used (at least) during login in MWO.
PGI needs to replace the OpenSSL library with the fixed one. And recompile (ie rebuild) the module using that library.

That's unfortunate, but thank you for explaining it! I was about to go and try to figure out how to update it myself on my PC. Hopefully they can update MWO soon and any other game running on Unreal Engine.

[RomeoOscarXray16]

Want to say thanks for the post about current intel processors. This fixed my game closing when clicking the Play button in the portal.

[Sateqla]

Million thanks! This fixed it for me as well! Running 11th gen Intel Core i9-11900K, exact symptoms described here and adding the environmental variable for OpenSSL fixed it. Very good!

[Ballpoint]

Fixed my issue. Ty OP.

[Ch_R0me]

OK, finally managed to encounter the issue myself (not only in MwO, but in games using Easy AntiCheat as well (error 10011)).

Yet, the provided solution by me was flawed, here is the correct one (to be applied in Command Line Options in Game Properties in Steam):

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

Sorry for problem.

Edited by Ch_R0me, 25 December 2021 - 01:32 PM.

[Gr8Legs]

Blank screen on start up. Thanks for the information. worked 100%
11th Gen Intel® Core™ i5-11600K

Step 1. Open "Control Panel" by searching for it in Windows search bar, by pressing the Windows button or key.
Step 2. Go to "System & Security"
Step 3. Go to "System"
Step 3. Press "Advanced system settings"
Step 4. Press "Environmental Variables"
Step 5. Create a new "System Variable" (NOT USER VARIABLE)
Step 6. Enter the following into the Variable name box: OPENSSL_ia32cap
Step 7. Enter the following into the Variable value box: ~0x20000000
Step 8. Now press OK.

[ConanTheGamer]

Tulip Lee, on 08 December 2020 - 02:11 PM, said:

Hey, y'all!

There appears to be a problem with MWO and new Ice Lake processors. I was having that same problem, and this fixed it. I bet that's the case with a new Razer laptop, too. Funnily enough, mine died hard and would have needed ANOTHER total motherboard replacement in 3 years, so I got this HP instead of another new Razer. Here's the fix they sent me:

GM Zen (Piranha Games)
Dec 7, 2020, 14:11 PST
Hello there,

Could you please try the following workaround: https://www.pubg.com...ash-workaround/

Let me know if that doesn't help.

Regards,
GM Zen
Technical Support Rep
Piranha Games

[mod] Edit:
The PUBG link is dead, but we have a step-by-step solution thanks to resourceful users like MrVaad, Tarl Cabot and Ch_R0me. [/mod]

Woohoo.. Thanks.

[PHANT0M23]

Gr8Legs, on 29 December 2021 - 05:22 PM, said:

Blank screen on start up. Thanks for the information. worked 100%
11th Gen Intel® Core™ i5-11600K

Step 1. Open "Control Panel" by searching for it in Windows search bar, by pressing the Windows button or key.
Step 2. Go to "System & Security"
Step 3. Go to "System"
Step 3. Press "Advanced system settings"
Step 4. Press "Environmental Variables"
Step 5. Create a new "System Variable" (NOT USER VARIABLE)
Step 6. Enter the following into the Variable name box: OPENSSL_ia32cap
Step 7. Enter the following into the Variable value box: ~0x20000000
Step 8. Now press OK.

I cannot follow these directions verbatim because I'm running Windows 11, and the user interface is different. Things are located in different places. Searching for "Environmental Varibles" yields no search results. Interestingly, I own two different Windows 11 machines at the moment. One of them has no problem running MWO, and the other one repeatedly refuses to run the game at all. The one that runs the game fine has a 10th gen CPU, and the other an 11th gen.

Ch_R0me, on 25 December 2021 - 01:31 PM, said:

OK, finally managed to encounter the issue myself (not only in MwO, but in games using Easy AntiCheat as well (error 10011)).

Yet, the provided solution by me was flawed, here is the correct one (to be applied in Command Line Options in Game Properties in Steam):

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

Sorry for problem.

if that's the spot you mean, it didn't work for me.

-edit-

Went back and opened the control panel, and within that did a manual search for "advanced system settings" and found it. The remainder of the fix worked.

Two notes here:
1) the user interface is *slightly* different under Windows 11. Search for "advanced system settings" within Control Panel, and this will work.
2) This worked on one windows 11 machine, but not the other one, so Win 11 was not to blame for this not working. This is just to confirm what you already know: 11th gen CPUs don't like old SSL lol

Edited by PHANT0M23, 13 February 2022 - 06:22 PM.

[Texas Wildcard]

After a few hours of search in the Forums found the work around and applied. It worked!

Thank you!

[Wolodymyr]

Environmental variable string worked for me, new Win 11/ i7 12700KF build

[cazeral]

Thank you Tulip, fix worked a treat on i5-11 series and GT3050 laptop

[Pasulj]

Just upgraded to i5-12400 and creating bat file to launch works like a charm. Thanks.

Edited by Pasulj, 05 April 2022 - 10:00 AM.

[Zozofling]

Hey everybody, I have created the text file using the above copy paste but I am struggling to run it. I cant make a call to the file name in the cmd prompt.

Edited by Zozofling, 08 April 2022 - 01:52 PM.

[Wolf Exhaust]

Confirmed working!!


Processor 12th Gen Intel® Core™ i9-12900KF 3.19 GHz
Windows 11
System type 64-bit operating system, x64-based processor
RTX 3080ti

[Cookem]

This worked great on my new 12th gen 17 12700 build....Thanks Tulip you saved me a hassle

Edited by Cookem, 29 April 2022 - 10:05 AM.

[Seelenlos]

MrVaad, on 18 April 2021 - 12:32 PM, said:

You can try to create a file to launch MWO with the fix inside it (it's what the intel link recommends)
something like LaunchMWO.bat with the following inside :

set OPENSSL_ia32cap=:~0x20000000
MWOClient.exe

This must be made STICKY!

[Ekson Valdez]

Added MrVaad's post to the OP.

[Ch_R0me]

MrVaad, on 18 April 2021 - 12:32 PM, said:

You can try to create a file to launch MWO with the fix inside it (it's what the intel link recommends)
something like LaunchMWO.bat with the following inside :

set OPENSSL_ia32cap=:~0x20000000
MWOClient.exe

Awesome thing to use when you're using a standalone client.

In Steam, I think it could be imported as an "outside" game (but of course the adjustments would be needed).

Meanwhile, did anybody else tested this command in game options in Steam? It's working in my case.

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

Edited by Ch_R0me, 09 May 2022 - 05:29 AM.

[MrVaad]

I saw two new files in MWO on the PTS :
\bin64\libcrypto-1_1-x64.dll
\bin64\libssl-1_1-x64.dll

Perhaps, PGI fixed the problem using those new libraries ?

[Tarl Cabot]

We can only hope, though not seeing anything in the actual patch notes, ya think they would add that!! /nm.. tis PGI..

Add general info for those who are challenged with search function

Libcrypto-1_1-x64. dll is considered a type of OpenSSL library file. It is most-commonly used in The OpenSSL Toolkit developed by Fortinet. It uses the DLL file extension and is considered a Win64 DLL (Dynamic link library) file.

[color=#202124]Libssl-1_1-x64. dll is considered [/color]a type of OpenSSL library file[color=#202124]. It is most-commonly used in The OpenSSL Toolkit developed by Fortinet. It uses the DLL file extension and is considered a Win64 DLL (Dynamic link library) file.[/color]

Edited by Tarl Cabot, 23 May 2022 - 03:52 PM.