Unreal Engine Issues

UMG materials do not correctly access material parameter collections (all of the values are black)

Edit MattK: The reason they do not work is that material parameter collections are updated inside of a uworld that slate doesnt have access to. We just need to figure out a way to update the necess ...

ParticlePosition doesn't use Previous values

FHLSLMaterialTranslator::ParticlePosition does not return Previous information when request which can result in bad motion vector calculation. ...

Utility functions in UEdGraph_ReferenceViewer are no longer exposed

A number of utility functions are provided in UEdGraph_ReferenceViewer for building menu extenders. This class was originally included in the engine as part of the ReferenceViewer module, but was re ...

Crash adding animation blueprint to skeletal mesh while sub graph input is linked

Crash occurs when setting post process animation blueprint while the anim bp has a Sub Graph Input linked. This crash doesn't occur if the node is not connected. ...

Mover MoveDirectionIntent can be 0 due to interpolation

If two states have MoveDirectionIntent vectors that are opposite to each other, interpolating between these states can result in MoveDirectionIntent being 0. This may cause issues for animation blue ...

Blueprint inherited from StaticMeshActor will fail to compile if StaticMesh is NULL

Some developers reporting incorrect Preview in VR resolution for Steam VR

VR Preview Window is the wrong resolution, just showing the top left portion of the entire view. Somewhat similar symptoms to -[Link Removed]-, not exactly the same though.   This issue has not be ...

Stop using power of 2 RTs for landscape edit layers

Result : all the RTs allocated for edit layers (in global merge mode) will be padded to the next power of 2 for no good reason, which can lead to out-of-VRAM (as reported by [Link Removed]) ...

Modifying an H/ISM instance will cause selection highlights to be inaccurate

Exposure Is More Extreme In High-End Mobile Preview Modes

In high-end mobile preview modes the exposure will return much more exaggerated results. This is related to the new default tone mapper settings since changing r.TonemapperFilm to 0 solves the issue ...