Unreal Engine Issues

Crash when enabling r.PSOPrecache.Resources due to check() in FSkeletalMeshObjectGPUSkin::GetUsedVertexFactoryData

The game crashes because of a nullptr SkinnedMeshComponent in  FSkeletalMeshObjectGPUSkin::GetUsedVertexFactoryData when r.PSOPrecache.Resources is enabled and a skeletal mesh is loaded due to a new ...

Fix deadlock between sk component and sk build or import

Fix deadlock when skeletal mesh component is shown in the detail panel with physics body section category open and the skeletalmesh is re-importing or doing any other asyc task that need the game th ...

[Interchange] Time zero bind pose do not support multiple bind pose for the same bone

If you import a model containing multiple mesh using the same bones but with different bind pose, the time zero skin result will be wrong. ...

GeneratePsyms fails with installed builds due to missing dymp_syms tool and incorrect path space handling

Uncovered while testing [Link Removed] ...

[Interchange] Bone name space are replace with underscore, legacy fbx rename with dash

This bug is critical since it can broke bone name reference between [animations, physics asset, curves, ...] and skeletal mesh bone name ...

Mobile Depth of Field blurry eveywhere

user reports I investigated the problem throught the frame capture tools and found that on a real device (iPhone 15 Pro in my case), the depth texture for the SunMask pass is not set (a dummy black ...

Circularly referenced blueprints cause stack overflow in a package game without IOStore

Crash in FPipelineFileCacheManager::RegisterPSOStats

The game can crash when one thread clears RunTimeToPSOUsage while another thread is expecting it to contain a PSO it is registering stats for. Thread A:  calls CacheGraphicsPSO() Thread B:  calls C ...

When adding the UIRenderer to the Movie Render Queue, the rendering output is a difference in PIE and MRQ.

UI rendering in PIE and UIrenderer rendering in MRQ produce different output results. This is because when dealing with fades in the UI, the rendering results should not be different.  Workaround ...