Unreal Engine Issues

Crash on applying animation modifier for some assets

When removing curves on some assets, a crash can occur. This seems to be due to const FSmartNameMapping* CurveMapping being null and dereferenced within UAnimationBlueprintLibrary::RetrieveContainer ...

Package fails after adding DesktopPlatform to public module dependency list

Adding DesktopPlatform to the PublicDependencyModuleNames.AddRange() section of the Project.Build.cs file causes the project to fail packaging with the following error (full package logs in callstac ...

Opening a Niagara asset that references a disabled plugin (Chaos Niagara) can crash the editor

Opening a module with references to a disabled plugin can crash the editor.  ...

SceneTexture:WorldNormal causes decal to ignore Emissive Color

SceneTexture:WorldNormal causes decal to ignore Emissive Color.  ...

Crash when attempting to revert a Child blueprint from overriding its parent's function while it also has a child of its own

When reverting the change of overriding a function from a blueprint's parent, the editor will crash if that blueprint has a child of its own. Regression?: No This also occurred in 4.16 ...

Attempting to generate abstract class from blueprint crashes editor on compile

Attempting to generate abstract class from blueprint crashes editor on compile. Frequency: 4/4 ...

If a Blueprint made from a class using PostLoad is saved immediately before and after PIE, a crash can occur

Using PostLoad in a class that has a Blueprint derived from it can result in a crash if the Blueprint is saved immediately before and after PIE. CrashReporter Link: [Link Removed] ...

[Crash]-[Reimport] - Crash on reimporting CAD file with deleted light sources

Adding a node or variable to a component referenced by another actor crashes editor

If compile is pressed after adding a variable or node to a blueprint component that has a variable referenced within another blueprint actor, the editor immediately crashes. Frequency: 1/1 Crashr ...

Editor crashed on exporting a skeletal mesh twice after garbage collection occurs

Issue was occurring with wildly varying repro steps, after speaking to Jurre and enabling gc.CollectGarbageEveryFrame 1 it was easy to conistenty reproduce this issue. note: I was getting this iss ...