Unreal Engine Issues

Fix PrimitiveComponent overlap indirection

When doing overlap tests in PrimitiveComponent, UWorld->ComponentOverlapMulti is used. The callstack for that ends up looking like this (callstack is inverted, highest level on top): UWorld::Compo ...

Regression: "Object Position" node in Light Function materials did not compile up to UE 5.0. Starting with 5.1, it compiles but outputs garbage values

Up to UE 5.0, when the "Object Position" node is used in the Material Editor as part of a material with Light Function domain, attempting to compile the material results in the following error: "[SM ...

Unable to compile script plugins against 4.16.0

A bug in UBT is preventing the authors of SkookumScript from submitting their 4.16 plugin to the marketplace. ...

[GPU Lightmass] bake artifact w/ two actors of same static mesh

As per a bug report from Pixomondo: if there are two static meshes in the scene and one has a rotation, it gets a GPULM bake artifact as if it is intersecting with the unrotated version of itself. S ...

Vive Trackpad X and Y always return 0

Platform-specific input for pad axis in 4.24 leads to missing value in VIVE. in 4.23.1 this is not reproduced. ...

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 ...

Crash upon editing a GameplayTagQuery inside of a DataAsset

When a GameplayTagQuery variable is edited from inside of a DataAsset, the editor crashes when the changes are saved. This could be related to a bug that was fixed previously: [Link Removed] Regres ...

Packaging with Nativize Blueprint Assets Causes Uninitialized Defaults

If you use "Set Array Elem" on a vector array but leave "Item" at the default value of (0,0,0) then you'll end up using a temporary uninitialised vector instead of (0,0,0) when it's nativized. Work ...

Post processing bloom threshold activates when the threshold is >0 instead of >-1.

Sequencer frame range progression is not continuous

The end of the level visibility section places a DeterminismFence. This causes the issue. The fence clips the frame range and produces a discontinuous frame ranges, e.g. 23201~24000, then 24001~24 ...