Unreal Engine Issues

Skeletal Meshes have physics collisions lag

Skeletal mesh's physics collision lag behind the actual mesh. It didn't matter if there was just a root bone or multiple bones/constraints. This doesn't happen when using static meshes. The effect ...

Attachment rules in Level Sequencer are broken

The Attach track attachment rules seems to have no effect when selecting "Snap to Target" and playing the sequence. This was reported and tested in 4.23 (CL-8386587). This was reproduced in 4.22.3 ...

Regression in tonemaper sharpen

Networking Engine Tests fail for NotifyParamCorrect on Client

The following errors occur when running the networking engine tests with 2 clients and a dedicated server. LogFunctionalTest: Error: Assertion failed: 'EngineTestNetActorComponent bRepArrayAddNotif ...

Sequencer crashes when scrubbing characters with sub-anim instances and montage slots

I saw a following assertion. Assertion failed: (AdditivePoses.Num() > 0) || (NonAdditivePoses.Num() > 0) [Link Removed] [Line: 1381] This is my quick fix// code placeholder void FAnimInstance ...

Playing as a Pawn that is a Duplicate of a Blueprint Class doesn't create an Attribute Set

Creating a duplicate of a Blueprint class that has an AttributeSet seems to be interfering with the creation of the AttributeSet. ...

Sequence Recorder under "Choose Properties to Be Recorded" shows only "Actor Hidden In Game"

Sequence Recorder under "Choose Properties to Be Recorded" shows only "Actor Hidden In Game" and no other properties. This was reported and tested in 4.22.3 (CL-7053642). This was reproduced in 4. ...

Crash on packaged game. 4.23 will not nativize a class that creates instanced properties inside itself

Description from the user: up to 4.23 properties nativize normally if they are written in C++ with the Instanced specifier. The discerning difference is that that there was no Blueprint Class itsel ...

Masked Mesh has significant performance hit on some android devices

Changing the object being debugged while stopped at a breakpoint has no long term effect if there was no object selected at the start of the breakpoint

The issue is that when we hit a breakpoint with no 'object to debug' set, we will set a flag bResetObjectBeingDebuggedWhenFinished to true, so after you resume execution we'll clear that flag and fo ...