Unreal Engine Issues

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

[CrashReport] UE4Editor-Engine!UpdateWorldBoneTM(TArray<FAssetWorldBoneTM,TMemStackAllocator<16> > &,TArray<FTransform,FDefaultAllocator> const &,int,USkeletalMeshComponent *,FTransform const &,FVector const &) [PhysAnim.cpp:143]

Generated from CrashReporter ...

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 occurs while clicking through the Landscape Overview Tutorial

Crash occurs while progressing through the Landscape Overview tutorial, after the step "After pressing the Create Button, your level should now have a Landscape Actor inside of it" This is a regres ...

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.

PerInstanceRandom does not work on Instanced Static Meshes spawned at runtime

PerInstanceRandom does not provide a random value when the material is being used on an Instanced Static Mesh that is spawned at runtime, the value is always the same. Regression?: Yes This did not ...

[CrashReport] Tutorial crash UObject::execLetValueOnPersistentFrame()

This is another Tutorial crash that shares a similar callstack with [Link Removed] and [Link Removed], but those specific repro steps have been fixed while this one is still occurring in 4.16.2. On ...

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