While working on the FPSPlayer project, I encountered a severe crash issue. The crash occurred when generating an Actor containing a custom Animation Blueprint.
After careful investigation, I found that the issue was caused by the Animation Blueprint Update Event in the Event Graph of the animation blueprint. Even an empty event could cause the crash.
Replacing the project's Config folder configuration files with the game’s own configuration files resolved the issue. This is the most recommended solution as it also resolves the issue of not being able to use custom materials and allows the loading of other game configurations.
Removing the Animation Blueprint Update Event from the Event Graph also resolves the issue, but you will need to find an alternative solution to achieve its functionality.
The main purpose of the Animation Blueprint Update Event is to check the status of the Actor that owns the Animation Blueprint and update variables within the Animation Blueprint itself.
The solution is to think in reverse—actively check the Actor's status in the Actor's Tick and update the variables in the Animation Blueprint.
This solution does not offer any advantage over Solution 1.