Fix for crash when trying to start a new game (UE4-Atlas)

[Judas]

This crash is caused by the same old SSE 4.1 problem that Phenom II users etc have been suffering recently when games like No Mans Sky and Resident Evil 7 released.

The fix may be a bit awkward for people who aren't very technical, and if someone has a way to clean this method up, please do.
First, download the following sde-external-7.49.0-2016-07-07-win.tar.bz2 from here - https://software.intel.com/en-us/articles/pre-release-license-agreement-for-intel-software-development-emulator-accept-end-user-license-agreement-and-download
Click 'DOWNLOAD Intel® SDE for WINDOWS' accept the terms, then select the file stated above to download. EDIT: Make sure you download the file that's 4th down in the list, one with 'win' at the end of the file name.

Once downloaded, extract folder to where you'd like. Then, go into folder, select all files, right click, copy. Then go to wherever your installation is, and where littlenightmares.exe resides, eg D:\Program Files (x86)\Little Nightmares\Atlas\Binaries\Win64 and paste all the files here.
Now run Command Prompt as admin and change your directory to X:\Program Files (x86)\Little Nightmares\Atlas\Binaries\Win64 (X being the drive your game is installed on eg C, D etc)
Now start the game, get to the start screen then tab out to cmd, type 'tasklist' (without quotes), once list populates, look for littlenightmares.exe, then look at the PID number.
Now, type in sde -attach-pid XXXX (XXXX being the PID number on the tasklist. Give it a second, tab back to game and start it, should start straight up. (please note, the PID changes each time the game is opened, so you need to do 'tasklist' every time.)

Another note - It may make your game feel a little laggy while sde is running. Also I haven't checked through if it makes any more SSE 4.1 calls, I did close cmd about 5 mins after my new game starting, has been ok since, so it may be that it's only needed to start the game then can be closed.

So sorry if this is a mess, I don't do this very much, I hope you all understand my ramblings. Happy gaming!

EDIT 1: I'm so sorry, I forgot to add, this doesn't work on Windows 10 unless you right click LittleNightmares.exe and change the compatibility to windows 7.

EDIT 2: Can confirm I've now tested this on both Windows 7 and Windows 10 64bit, with 100% success.

EDIT 3: The few people that have had trouble so far re: too laggy, they've all had 4GB and under RAM. So maybe it's a no go with that RAM.

[Tetsuo Shima]

true_shadow64님이 먼저 게시:

Benelor님이 먼저 게시:

And i guarantee you its 100% not the issue with the SSE 4.1 its a not optimized Game Engine for certain CPUs like the AMD ones cause they programm it mostly on Intel Hardware.

I tested it with multiple RIGS
AMD A6 -3650 is capable of up to SSE 4.2 and the Game is still giving me an Error.
Intel 7 6700K is also capable of up to SSE 4.2 and the game is still giving me the Error.
Intel 5 760 is also capable of up to SSE 4.2 and the game is still giving me the Error.

Sorry but its not the support of SSE 4.1.
The Problem is that the developer forgot to optimize the game for PC Hardware and focused more on consoles. A Bad Port so to speak.

All your solution does is to emulate something the CPU already is capable of doing on its own yet the programming of the game is not capable of recalling the CPU doing so.

Im not saying its not working for ppl who wanna try all im saying is you put immense pressure on your system by emulating stuff your CPU can do already yet the game engine cant adress or find it doing so.

The Issue is a Bad Port that needs optimization by the developer.

PS: The SSE4.1 Problem of RE7 was fixed by the dev a week later with a patch.

i can confirm the game does start and run using this SDE method. tested it myself. the exact same solution that solved the RE7 problem, also works as a fix for this game. so im not sure why you are so certain the problem is unrelated...

ok its work, probleme is big lag, cmd close or not... not playable.

[Froste]

Ok wait do I have to have it on the Windows 7 compatibility for windows 10?


(Edit)
Also my game is set here:
C:\Program Files (x86)\Steam\steamapps\common\Little Nightmares\Atlas\Binaries\Win64

Could that possibly be the issue?

[Clutch Shift Go]

When i do this sde fix, i keep getting an incompatible operating system or incompatible software installed on the system
Pin is exiting due to fatal error

Win 10 64bit
Phenom ll x6 1090t black edition
16gig ram
asus rog crosshair iv mobo
amd radeon hd 5850

[Tyler Durden]

Souleyman님이 먼저 게시:

true_shadow64님이 먼저 게시:

i can confirm the game does start and run using this SDE method. tested it myself. the exact same solution that solved the RE7 problem, also works as a fix for this game. so im not sure why you are so certain the problem is unrelated...

ok its work, probleme is big lag, cmd close or not... not playable.

it probably does have optimization issues, it runs about 30-40 fps for me with high settings. with occasional chop here and there. i havent played the game very far yet, but so far id say it is playable. 30 fps is very playable for most games.

[Benelor]

true_shadow64님이 먼저 게시:

Benelor님이 먼저 게시:

And i guarantee you its 100% not the issue with the SSE 4.1 its a not optimized Game Engine for certain CPUs like the AMD ones cause they programm it mostly on Intel Hardware.

I tested it with multiple RIGS
AMD A6 -3650 is capable of up to SSE 4.2 and the Game is still giving me an Error.
Intel 7 6700K is also capable of up to SSE 4.2 and the game is still giving me the Error.
Intel 5 760 is also capable of up to SSE 4.2 and the game is still giving me the Error.

Sorry but its not the support of SSE 4.1.
The Problem is that the developer forgot to optimize the game for PC Hardware and focused more on consoles. A Bad Port so to speak.

All your solution does is to emulate something the CPU already is capable of doing on its own yet the programming of the game is not capable of recalling the CPU doing so.

Im not saying its not working for ppl who wanna try all im saying is you put immense pressure on your system by emulating stuff your CPU can do already yet the game engine cant adress or find it doing so.

The Issue is a Bad Port that needs optimization by the developer.

PS: The SSE4.1 Problem of RE7 was fixed by the dev a week later with a patch.

i can confirm the game does start and run using this SDE method. tested it myself. the exact same solution that solved the RE7 problem, also works as a fix for this game. so im not sure why you are so certain the problem is unrelated...

And i can confirm it has nothing to do with the SSE 4.1 cause all CPUS i tested with support up to SSE 4.2 and the game still crashes and give us an error.

Its a bad port. All you do with this fix is to emulate something your CPU already can do. THe Game Engine is just to stupid to communicate with older CPUs.

To give you an example.

Your CPU can run Witcher 3 with MId to high settings. Needs SSE 4.1 otherwise crash.
Your CPU can run Fallout 4 all maxed out. Needs SSE 4.1 otherwise crash
Your CPU can run Mad Max on Ultra Settings. Needs also SSE 4.1. otherwise crash

Almost everything even the old Batman Arkham Asylum needed SSE 4.1 otherwise half the Games on Unreal Engine would not work.

Your CPU cant run Little Nightmares cause you have to emulate the SSE 4.1 in order to be capable of even starting the game.

That makes no ♥♥♥♥♥♥♥ sense at all.

Thats the whole problem here. The game engine is to dumb to adress older AMD and Intel CPUs to turn the SSE 4.1 on.

[kakarot_26]

for the people who said it did not recognised the sde line...it doesn`t work because you didnt download the good file...some files don`t have extensions and thus executebles don`t work you need 2 download the 47 one woth 14 mb the other don`t work....xd

[BlitzKillah]

Sde method works both with pid or exe in command line or any other method as soon as you add the game folder to antivirus exceptions (maybe just adding sde to excepions will work too), then finally command line stops closing and game starts. Not too fluid but game passed the fatal error at new game with no cmd errors about compatibility. Now it runs fine on friend's pc with Phenom II x4 and graphics set to high, a bit laggy but playable.
P.S. - not the steam version but i think it's pretty much the same.
Hope it can help.

[dramakun]

Thank you, worked for me.
Specs: Win7, AMD A8-3850, nvidia geforce 650 ti, 8gb RAM.

[BTR911 TV]

Don't work on Win10, Core i7,,,

[Dr Tetoso]

how do i get a refund? im just angry with this bug, you prefere to fix a dlc bug insted of the whole game im like ♥♥♥♥ you

[dramakun]

SuperCuate님이 먼저 게시:

how do i get a refund? im just angry with this bug, you prefere to fix a dlc bug insted of the whole game im like ♥♥♥♥ you

Choose a game here and select a refund
https://help.steampowered.com/en/wizard/HelpWithPurchase

[ViribusUnitis]

what is command prompt?

[Ice Bear]

sde-attach-pdi is not recognized, any suggestion?

I'm sure of version and extraction.

Also disabled win-defender.

[Tetsuo Shima]

Ice Bear님이 먼저 게시:

sde-attach-pdi is not recognized, any suggestion?

I'm sure of version and extraction.

Also disabled win-defender.

sde -attach-pid not sde-attach-pdi

[Mr Stealth]

Judas님이 먼저 게시:

This crash is caused by the same old SSE 4.1 problem that Phenom II users etc have been suffering recently when games like No Mans Sky and Resident Evil 7 released.

The fix may be a bit awkward for people who aren't very technical, and if someone has a way to clean this method up, please do.
First, download the following sde-external-7.49.0-2016-07-07-win.tar.bz2 from here - https://software.intel.com/en-us/articles/pre-release-license-agreement-for-intel-software-development-emulator-accept-end-user-license-agreement-and-download
Click 'DOWNLOAD Intel® SDE for WINDOWS' accept the terms, then select the file stated above to download. EDIT: Make sure you download the file that's 4th down in the list, one with 'win' at the end of the file name.

Once downloaded, extract folder to where you'd like. Then, go into folder, select all files, right click, copy. Then go to wherever your installation is, and where littlenightmares.exe resides, eg D:\Program Files (x86)\Little Nightmares\Atlas\Binaries\Win64 and paste all the files here.
Now run Command Prompt as admin and change your directory to X:\Program Files (x86)\Little Nightmares\Atlas\Binaries\Win64 (X being the drive your game is installed on eg C, D etc)
Now start the game, get to the start screen then tab out to cmd, type 'tasklist' (without quotes), once list populates, look for littlenightmares.exe, then look at the PID number.
Now, type in sde -attach-pid XXXX (XXXX being the PID number on the tasklist. Give it a second, tab back to game and start it, should start straight up. (please note, the PID changes each time the game is opened, so you need to do 'tasklist' every time.)

Another note - It may make your game feel a little laggy while sde is running. Also I haven't checked through if it makes any more SSE 4.1 calls, I did close cmd about 5 mins after my new game starting, has been ok since, so it may be that it's only needed to start the game then can be closed.

So sorry if this is a mess, I don't do this very much, I hope you all understand my ramblings. Happy gaming!

EDIT 1: I'm so sorry, I forgot to add, this doesn't work on Windows 10 unless you right click LittleNightmares.exe and change the compatibility to windows 7.

EDIT 2: Can confirm I've now tested this on both Windows 7 and Windows 10 64bit, with 100% success.

EDIT 3: The few people that have had trouble so far re: too laggy, they've all had 4GB and under RAM. So maybe it's a no go with that RAM.

Hey Judas. I`ve tried to see if your fix could work for me, but when i download that file that you said should be downloaded, all i get when i unpack it is a TAR-file that keeps saying i dont have the necessary program to open the file. What do i need to then to continue with the process of making the game work properly?