Unreal Engine Issues

Statistics Window does not show spawned objects with "All Objects" filter during PIE

Actors created during PIE are not shown with the "All Objects" filter in Statistics window. Licensee also reports Texture Stats not working with "Selected Actors" filter during PIE ...

Flickering Meshes after removing HISM instances

Removing HISMs in a packaged project causes meshes to remain and flicker in a packaged project. (Inclusive Nativization is enabled in test project, but issue occurs with nativization disabled as we ...

Project crashes when auto save completes after copy/pasting emitters multiple times in a system

Project crashes when auto save completes after copy/pasting emitters multiple times in a system Encountered same crash testing Blend_Attributes_System and ExpressionsExample_System. Doesn't seem to ...

FPlatformOutputDevices::GetAbsoluteLogFilename() not returning correct path when running multiple application instance

uasset file not deleted when delete skeletal mesh

Crash when converting a Landscape to a Blueprint Class

The Editor crashes when attempting to convert a Landscape into a Blueprint Class. Looking back to //UE4/Release-4.24 cl 11590231, this option seems to be unselectable (see attached image), which lea ...

Static lighting isn't bouncing when using Layered Materials

Static lighting will not bounce on the ceiling when using a Layered Material. The Material Attributes Layers node is used which doesn't appear in 4.24.3 so this isn't a regression. This was report ...

Compiling with VS2019 16.6 later causes garbled characters in output window

Using old behavior by applying true to NMakeUseOemCodePage property solves this issue.  in VCProject.cs​// Project globals (project GUID, project type, SCC bindings, etc) { VCProjectFi ...

Volumetric Translucent Shadow does not work

Async Task nodes placed in editor only modules should not issue a warning if the proxy class is set to something in the game module

Because the proxy class is set to something within the game module, no warning is placed on the node as the outer package ends up being a valid Runtime module. This should actually be a warning in ...