gauthi02
commented
8 months ago Hello, I'm deseperated to play Little Nightmares 1 using ue4, but I get the "UE4-Atlas crash fatal error" before jumping in the main menu. I do have a 12th gen Intel i7-12700F coupled to a RTX 3060 Ti, my PC has 16gB RAM. I've tried every solutions I found on the internet, such as changing the compatibility settings or setting the OPENSSL_ia32cap to the value you said. The last thing I didn't try is this: https://steamcommunity.com/app/424840/discussions/0/1318836262655833334/?l=koreana&ctp=5 , because I don't have an AMD cpu and it is very complicated. Please help me I'm very very disappointed because it's the first time there is no existing solutions online... (I've also tried the steam launch option, tell me if you need any details or crashlogs if existing or anything)
AwesamLinux
System Information
system_info.txt
Symptoms
Some games crash on computers that have CPU's with SHA extensions (Intel 10th gen and newer). On my Intel 12th Gen Alder Lake CPU these games crash on launch or after a few minutes of gameplay. The crashes appear to occur because of this issue:
OpenSSL* 1.0.2 beta (Jun 2014) to OpenSSL 1.0.2k (Jan 2017) contain bugs that either cause a crash or bad SHA (Secure Hash Algorithm) values on processors with the SHA extensions, such as the recently released 10th Generation processor. Both bugs were fixed years ago; however, any application that uses the old version directly, or as one of its dependencies, will fail. Unreal Engine* version 4.13 (Sept 2016) to version 4.21 (Dec 2018) contains the old version of OpenSSL, so any game built using those versions is possibly affected.Source: https://www.intel.com/content/www/us/en/developer/articles/troubleshooting/openssl-sha-crash-bug-requires-application-update.html
Reproduction
Workaround
Set Steam Launch option: OPENSSL_ia32cap=0x20000000 %command%
That disables the OpenSSL code check for SHA extensions and runs a different code path that does not contain the crashing bug.
Logs of playing games without the workaround (crashing), and playing them successfully with the workaround: Blair Witch (1092660) #3174 Song of Horror (1096570) Call of Cthulhu (399810) Man of Medan (939850) #3024
As tested on 12th Gen Intel(R) Core(TM) i7-12700T: steam-399810-fix.log steam-399810.log steam-939850-fix.log steam-939850.log steam-1092660-fix.log steam-1092660.log steam-1096570-fix.log steam-1096570.log
Summary / thoughts
Sorry if this problem is beyond the scope of Proton, but I wanted to bring awareness to this issue in case it has gone unnoticed. While this bug is not Proton specific it is unlikely that any of the games with the problem will ever be updated. So I was thinking that maybe these games can be made to work out of the box in Proton using the workaround.
Also as there are more games with this problem than the ones I mentioned, perhaps it should be considered to always use the alternate code path on Proton (if there is never any reason not to in games).