Crash after removing decal (using set fade out node) during design time and then hitting play

UE - Gameplay - Blueprint - Feb 5, 2019

When calling set fade out on a decal during design time via a custom event that is setup to be called in editor a crash will occur when clicking PIE ...

Data Tables with 'ParticleSysParam' structs cause crash

UE - Niagara - Feb 4, 2019

Data Tables with 'Particle Sys Param' structs in them as variables will crash when opened. ...

Right click mirror option for scale is applied to all axes even when uniform scale is unlocked

Tools - Feb 4, 2019

When using the mirror (axis) option in the details panel, the mirroring behaves unexpectedly when the uniform scale is unlocked. ...

Resolution appears incorrect when using Windows Mixed reality Simulator

UE - Platform - XR - Feb 4, 2019

Resolution appears incorrect when using Windows Mixed reality Simulator. It appears to only take up around 1/4 the available screen space. ...

Weird results in lightmaps after update to 4.21.2

UE - Graphics Features - Feb 4, 2019

Reported by our licensee Gungho. Reproduced in 4.21.2, win10 ...

Unused Foliage Type Causing Unbuilt Lighting

UE - World Creation - Worldbuilding Tools - Foliage - Feb 1, 2019

Foliage components will be unbuilt even after deleting all of the placed foliage in a level. Found in 4.20 CL# 4369336, 4.21 CL# 4753647, 4.22 CL# 4827620 ...

Niagara systems always compile on load.

UE - Niagara - Feb 1, 2019

Navigation Mesh ignores Hierarchical Instanced Static Meshes using "Build Paths" or the "Build" Button

UE - AI - Feb 1, 2019

Hierarchical Instanced Static Meshes are partially ignored after building the navigation mesh. This is causing the navmesh to be generated within all or part the HISM instead of around it.  This ...

Hypotenuse node unexpectedly returns "-nan(ind)" instead of "0.0" if both values passed into the node are "0.0"

UE - Gameplay - Blueprint - Feb 1, 2019

The Hypotenuse Blueprint node currently returns a value of "-nan(ind)" if both values passed into the node are "0.0". This result is correct based on the code that the Hypotenuse node uses, but is n ...