MISSING_ANGELSCRIPT_CALLSTACK Discovery Fixes?

[mrtn™]

https://imgur.com/a/CXUxlWV
i start the game and the splash screen shows up. loading. Blackscreen for 20 sec and after that crash with the Image above.

Anyone have a FIX?

What i tried:

- reset Bios to default (because of XMP and CPU overclock), XMP off
- reset nvidia Graphic settings
- reset GPU overclock
- updated Nvidia Driver
- updated Windows 10
- updated Microsoft Visual
- game lauch options : -d3d11 -windowed and some others
- deleted the %appdata% folder "Discovery"
- repair gamefiles with steam
- reinstalled a few times
- run as admin
- clean directX shader cache

The last beta works without gamecrashes.

i9 9900k
RTX 2080
Win 10
3200Mhz Ram

EDIT:
It works with this old driver, i can play without any crashes:
https://de.download.nvidia.com/Windows/546.01/546.01-desktop-win10-win11-64bit-international-dch-whql.exe

[cwеl_oficjalnie]

What's help for me to change from win 10 to win 11 thats all

[r-2]

This fixed my error for the time being:

go to %APPDATA%\Local\Discovery\Saved\SaveGames and delete all files.
Restart game, and you will see all settings turned to default.
Turn Ray tracing to Static

So far running good on a 3080. I was afraid to touch Ranked mode with so many crashes and can now finally jump into Ranked mode.

[Dhomochevsky]

i did tried this driver you suggest it didnt worked for me, nothing has worked for me, what really makes me mad is to think that playstest worked so good not a single crash so i cant fathom how is that the final game is actually "worse" than beta.

[Pilzquadrat]

All the "fixes" seem to work for 3-4 matches then the error returns

[Spoon]

Same.

[r-2]

İlk olarak Pilzquadrat tarafından gönderildi:

All the "fixes" seem to work for 3-4 matches then the error returns

Still working for me. Second time playing Ranked today, havent had a crash so far.

[Spyder]

I delete the Discovery savegames then I get to play one match. The second match will MISSING_ANGELSCRIPT_CALLSTACK crash. Wash rinse repeat.

[Dhomochevsky]

İlk olarak Dhomochevsky tarafından gönderildi:

i did tried this driver you suggest it didnt worked for me, nothing has worked for me, what really makes me mad is to think that playstest worked so good not a single crash so i cant fathom how is that the final game is actually "worse" than beta.

i think what what finally worked for me was not touching the mouse keyboard config. i used to bind melee to my mouse side buttons, this far i think thats what was making game crash for me. althought i did the same on open beta and i didnt had any crashes

[Dhomochevsky]

İlk olarak Dhomochevsky tarafından gönderildi:

İlk olarak Dhomochevsky tarafından gönderildi:

i did tried this driver you suggest it didnt worked for me, nothing has worked for me, what really makes me mad is to think that playstest worked so good not a single crash so i cant fathom how is that the final game is actually "worse" than beta.

i think what what finally worked for me was not touching the mouse keyboard config. i used to bind melee to my mouse side buttons, this far i think thats what was making game crash for me. althought i did the same on open beta and i didnt had any crashes

--edit--

nevermind this, just got a crash so yeah i can tell you now that a lot of my crashes are related to explosions/fire, and maybe enviromental destruction.

[issheda1]

Getting this issue as well, has anyone heard/seen any response from the dev team on whether or not they are at least aware of this issue?

[VladGromov]

İlk olarak issheda1 tarafından gönderildi:

Getting this issue as well, has anyone heard/seen any response from the dev team on whether or not they are at least aware of this issue?

They are in no hurry with patches, and they don't have Trello, as I understand it, in general it really looks like this product was developed by AI...

[Marksman420]

İlk olarak Spyder tarafından gönderildi:

I delete the Discovery savegames then I get to play one match. The second match will MISSING_ANGELSCRIPT_CALLSTACK crash. Wash rinse repeat.

game crashes directly after clearing save files... this isn't a solution. like many, this crash is intermittent and it's really easy to think you've solved it and then find it's still happening.

3-4 of these a night is enough though, i'll come back for season two maybe if it looks like it's been resolved.

[Madshell]

Check your RAM/system stability, Unreal Engine 5 is very demanding.

I had lots of those MISSING_ANGELSCRIPT crashes and I think I solved it. If you have a Gigabyte motherboard (mine is Z790 Aorus Elite AX), it seems these DDR/RAM options are enabled by default, resulting in some unstable overclock of your system/memory:
- RAM Low Latency: auto
- RAM High Bandwidth: auto
Setting both to "disabled" AND letting the default Corsair XMP on the RAM did the trick.

Before doing this, I got errors on Aida64 "stress system memory" test. After it can run for 10 minutes without stopping. Same results with the memory test from OCCT. Check on the temps with HWiNFO64 if you are trying this.

I had the same crashes on Payday 3 (Unreal Engine 5 too) so I think it's solved now. :)

System: i7 12700k + 2x32GB + Nvidia 3090TI (latest 546.33 driver)

[AFEX]

new drivers new patch and STILL not fixed LMFAO