It appears that LumenScene's Hardware Ray Tracing is causing light leaking into a sealed room (which should be perfectly black). This bug does not appear to happen on AMD GPUs. ...
Changing Class for Spawnable objects in Level Sequence did not have any impact on Possesable objects in Subsequence. It's still referencing the previous Class. Also found in Release-5.4, CL: 329753 ...
When a user deletes a Niagara User Parameter within the Niagara System editor window, attempting to create a new parameter with the same name immediately after deletion results in an error. Despite ...
This issue occurs when a static function is created and has a struct parameter that has a delegate exposed to blueprint. When using the helper function in blueprint after having used "Split Struct ...
Consider a C++ ActorComponent containing an instanced TObjectPtr property (which may be standalone or inside a container such as TMap). Now consider a Blueprint Actor containing such a component, an ...
Dark moving noise is visible in hair in the shadows when Lumen screen traces are active. Example of noise when screen tracing is frozen:[Image Removed] Turning off Lumen screen traces using r.Lume ...
ExportMaterialUVDensities() gets the incorrect value where the alpha channel is referenced (e.g. RegisterIndex of the texture is [3] or [7]) because FMeshRenderer::RenderMaterialTexCoordScales() use ...
When a Material uses WorldPositionOffset, the MaterialTextureScale is calculated incorrectly because FMaterialUtilities::ExportMaterialUVDensities() calls FMeshRenderer::RenderMaterialTexCoordScales ...
If you right click on a level node in the reference viewer and choose edit, it will bypass prompting you to save unsaved changes in your current level, silently discarding all unsaved work. ...
SkeletalMeshActor using a PhysicsAsset with custom box shapes may flicker rapidly in Editor when not selected, and also flickers in PIE mode. If occlusion culling is disabled the flickering stops. ...