Subverse
This Community Hub is marked as 'Adult Only'. You are seeing this hub because you have set your preferences to allow this content.

Subverse

View Stats:
KingOfHalves Nov 20, 2024 @ 10:31am
7
2
3
2
UE4 Fatal Error crash solutions thread
This problem has been an issue for quite some time now. I had hoped the Devs would fix it for 1.0, but it's still there.

After some research, I discovered that it's a problem common to Unreal Engine games. I'm not sure the Devs can actually do anything about it. I've come across a ton of different potential fixes that have been reported to work for some people. Here's the list.

- IN GAME -

Switch graphics to potato mode. (set everything to low)

Switch to Native Fullscreen in the graphics options.

Turn off 4k cutscenes.

Set FPS cap to 60.

Switch Anti aliasing modes.

- IN STEAM -

Turn off the Steam overlay.

Force the game to run using Direct X 11 in the Steam advanced settings.

Force the game to run using Direct X 12 in the Steam advanced settings.

- OUTSIDE STEAM -

Turn off as many background processes as you can.

Update Windows

Update your GPU drivers.

Update Microsoft Visual C++ Redistributable.

Set your computer's display scale to 100%

Disable Fullscreen Optimizations in the game .exe's Properties menu.

Switch to "adjust for best performance" in the Advanced System Settings Visual Effects tab. (Control Panel → System → Advanced System Settings)

Delete the Unreal Engine cache in your AppData folder.

Run as Administrator.

Stop any overclocking you have active.

- FOR NVIDIA -

Turn off the NVidia overlay in GForce Experience.

Turn off Multi Frame Sampled AA in the Nvidia control panel.

- FOR AMD -

Disable Freesynch in your monitor settings.

_____________________________

Yes, it's completely absurd that troubleshooting this issue has so many different things that *might* work. So far, none of these have worked for me. I'll keep adding to the list as I try things.

If anyone else has potential solutions, of if something on the list works for you, please leave a comment. I'll add your suggestions. Mods, please sticky this until the Devs can find a solution on their end.
< >
Showing 1-15 of 22 comments
Baron Nov 20, 2024 @ 11:44am 
BIG F! THANKS
vine Nov 20, 2024 @ 12:29pm 
imma wait til devs actually fix and finish the game. it's not up to me to fix suboptimal product. wish we already had a warranty on software enforced through law.
NachosAndCheeezzz Nov 20, 2024 @ 2:24pm 
Let's bump this one, cuz this has been quite a problem for me and I don't want to lose this thread.
KingOfHalves Nov 20, 2024 @ 4:54pm 
Originally posted by vine:
imma wait til devs actually fix and finish the game. it's not up to me to fix suboptimal product. wish we already had a warranty on software enforced through law.

I agree with you in principle, but in this case I'm not sure it's an issue the devs can fix. It's an issue with Unreal Engine itself. A lot of the potential fixes came from videos and threads about other games.

That said, I'd like the devs to address the problem even if it's just to say "we can't help with this."
Henry Nov 20, 2024 @ 5:22pm 
The game used to run extremelly well with every setting in Epic before the 1.0 patch, but now if I enter in a dialog, there is 50/50 chances to get a Fatal Crash... I've done several test and nothing for now. I won't be playing the game on Low settings if it used to run perfect before.
vine Nov 20, 2024 @ 9:01pm 
Originally posted by KingOfHalves:
Originally posted by vine:
imma wait til devs actually fix and finish the game. it's not up to me to fix suboptimal product. wish we already had a warranty on software enforced through law.

I agree with you in principle, but in this case I'm not sure it's an issue the devs can fix. It's an issue with Unreal Engine itself. A lot of the potential fixes came from videos and threads about other games.

That said, I'd like the devs to address the problem even if it's just to say "we can't help with this."
right as Henry says after your post, EA ran stable on Epic even on my 7yo pc rig. yes its the engine but it also is the devs. they need to tame the engine again. something happened and its worse than it was before.
KingOfHalves Nov 21, 2024 @ 2:08pm 
Originally posted by vine:
right as Henry says after your post, EA ran stable on Epic even on my 7yo pc rig. yes its the engine but it also is the devs. they need to tame the engine again. something happened and its worse than it was before.

I noticed that too. I played about 10 hours of early access (whichever version was right before Huntress was introduced), and never had a single crash.

When I was researching this issue, I noticed that reports of these crashes on this forum went back more than a year. Makes me wonder what changed, and why the developers still haven't addressed it.
NotSerious Nov 23, 2024 @ 3:15am 
i got fatal error every 10 min of playing, totally random. I got a 6950 XT (3090 equivalent) so its definatly not a spec problem) and it never happend before the 1.0 patch and the 4k DLC ? it oonly happenned with this game, not very high end AAA games do that on my side... its unplayable
Henry Nov 23, 2024 @ 3:26am 
Originally posted by NotSerious:
i got fatal error every 10 min of playing, totally random. I got a 6950 XT (3090 equivalent) so its definatly not a spec problem) and it never happend before the 1.0 patch and the 4k DLC ? it oonly happenned with this game, not very high end AAA games do that on my side... its unplayable
I'm having the same problem and I didn't have any problem before the patch. What I do to "mitigate" that crash is: using windowed mode with a resolution less than the native, no 4k videos, no volumetric fog, all settings on High instead of Epic, and last but not least, try not to skip the dialogs. You will still having the problem but with less frequency.
sistertwister Nov 23, 2024 @ 9:10am 
Originally posted by Henry:
The game used to run extremelly well with every setting in Epic before the 1.0 patch, but now if I enter in a dialog, there is 50/50 chances to get a Fatal Crash... I've done several test and nothing for now. I won't be playing the game on Low settings if it used to run perfect before.
Up to 1.0, I never experienced crashes, not once.
Now I count my blessings if it doesn't crash during cut scenes and the best thing? I can't even end the boss battle in this sad joke of a game.
KingOfHalves Nov 27, 2024 @ 11:52am 
Originally posted by NotSerious:
i got fatal error every 10 min of playing, totally random. I got a 6950 XT (3090 equivalent) so its definatly not a spec problem) and it never happend before the 1.0 patch and the 4k DLC ? it oonly happenned with this game, not very high end AAA games do that on my side... its unplayable

Yup. In it's current state, the game is completely unplayable for some folks. The worst part is, there doesn't seem to be an easy way to diagnose why. I saw a thread last week of two people comparing specs. Nearly everything was the same. One had the recurring crash error, the other didn't. It's just bizarre.
Darth Alpharius Nov 27, 2024 @ 4:32pm 
Fatal Error is a Curse on every version of Unreal Engine.
Purple Sauce Nov 29, 2024 @ 12:54pm 
Originally posted by Henry:
The game used to run extremelly well with every setting in Epic before the 1.0 patch, but now if I enter in a dialog, there is 50/50 chances to get a Fatal Crash... I've done several test and nothing for now. I won't be playing the game on Low settings if it used to run perfect before.

Same story for me. Ran perfectly fine, no crashes pre-launch. Now it's a toss up if I get a fatal error during dialogue. I think this issue is more on the code than the player, especially since it's happening when the player isn't interacting with the game much.
Midori-San Nov 29, 2024 @ 4:11pm 
Ngl I thought they had fixed this by now even in early access Id pray I didnt crash during a dialog and behold 1.0 and still getting it...
KingOfHalves Nov 30, 2024 @ 9:02am 
Originally posted by Midori-San:
Ngl I thought they had fixed this by now even in early access Id pray I didnt crash during a dialog and behold 1.0 and still getting it...

Same. It's pretty weird that such an old and widely reported bug still exists after the 1.0 launch.
< >
Showing 1-15 of 22 comments
Per page: 1530 50