Shortcut will still led to create a new function in the macro library. and this makes engine crash with following callstack. Assertion failed: Blueprint->BlueprintType != BPTYPE_MacroLibrary [Link ...
Crash occurs when the user launches a project with a +75 bone skeletal mesh actor in their scene with the Compat.MAX_GPUSKIN_BONES=75 config change, and the default preview render is Shader Model 5. ...
Crash on switching to landscape/paint tab when using a landscape material that has a material function hooked onto the WorldPositionOffset. Working as expected in 4.21 CL# 4753647 Found in 4.22 CL ...
Currently the Dynamic Entry Box has no protection against recursion, leading to a stack overflow and a crash. This issue was reported and tested in 4.25 (CL-13144385). This was reproduced in 4.24.3 ...
Crash using Import Commandlet on FBX that gets "Bones are too small" error when imported manually Error from manual import: Warning The bone size is too small to create Physics Asset 'ButterflyVa ...
Edit MattK: Not reproducible yet If the editor is open and used for a long period of time without being closed, it stores memory use. After building up a significant amount of resources building us ...
According to information from the licensee, the else clause was added to "FSkeletalMeshLODModel::(GetClothMappingData()" at CL 4437969 , but if it is the cloth data existing from 4.20 or earlier, it ...
This is a trending crash coming out of the 4.18 previews. It seems to be related to exporting assets from the editor. User DescriptionsWhen Exporting assets (static meshes) multiple times via RIGHT ...
The customer provided reproduction steps and a trace file that crashes Insights. From the customer: manually placing if (!CurrentGraph) Unknown macro: { return; } nullchecks in RenderGraphInsi ...
According to the licensee, this problem is caused by a variable inconsistency in Cvar. The cause seems to be the difference between the CVar reference when generating RayTracingSceneRHI and the CVa ...