6 years ago
Won't launch game
Game won't launch syncs with cloud then does the first load box then just closes and i can click play again, restarted computer, verified files... updated game. still doesn't want to let me play..
I'l found fix for me, just close logo alt+F4 xD
Alt F4 was the only thing that works for me .. thx
Thanks!
Any 1 have any updates or has everyone given up.. posted this dx file like 20 times.......still hopeful
On my side, I've re-installed Origin + Fallen Order and now I can play.
I too have a Razer Blade Stealth GTX 1650 model. So as for many others the game didn't launch properly.
I've looked for solutions and found the source of my issues. This is related to some other programs and games that use Unreal Engine, not unique to Jedi Fallen Order. Here is a copy of the original post:
There is currently a known issue that prevents the Epic Games Launcher from running on a class of processors(CPUs) that support the SHA-NI instruction set. This includes Intel Apollo Lake CPUs, Intel Ice Lake CPUs, and other CPUs that report SHA-NI in the same way.
The fix for this issue has made its way into other Epic products and will be making its way to the Epic Games Launcher in the near future.
Until the fix makes it out, a potential workaround to this issue is to set the following environment variable before starting the launcher:
OPENSSL_ia32cap=:~0x20000000
So what I did was, as told by the original poster, create a system variable
OPENSSL_ia32cap
with value
:~0x20000000
(exactly like this, all symbols are important, see attached image)
Then restart your system. Worked like a charm after that for me.
Personally I'm going to keep this setting until I finish the game, then disable. The laptop seems to work without issues anyway, but future game releases should handle the processor instructions properly so there should be no need for it.
Tried all of the above...nothing. DXDiag att.
Works fine on my ROG laptop though...
I have a Dell XPS13 7390 2-in-1 also running an Ice Lake processor using an eGPU and this environment variable fix worked for me.
Thanks a million @niaphim.