Unreal Engine Issues

Light function materials using WorldPosition do not render correctly to volumetric fog if there is more than one

There is a one-line fix for this in a shader file, see their PR on GitHub:https://github.com/EpicGames/UnrealEngine/pull/10251/files ...

Interactive changes from In-Camera VFX widgets are not transacting to nDisplay until mouse is released

Multiple Post Processing displays are not working in Content Examples - Post Processing

While going through a GPU pass, film setting in post processing isn't working as expected. This does not seem to be GPU specific The displays should resemble the images in the documentation - PPE ...

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

Area Lights casting Specular regardless of material specular value

The rectangle lights ignore the specular value of lit materials and will apply a specular highlight to them regardless of the value. you can compare the result against a standard point light and you ...

Camera Position Node in Light Function Materials does not function once applied to a light

In the material editor, the preview will change with the camera position. Similar to [Link Removed] though the light will still emit when applied. Investigating Regression info ...

Some style properties for Multi-Line Editable Text boxes do not change when setting them in blueprints

Some style properties for Multi-Line Editable Text boxes do not appear to change when setting them in blueprints. ...

Soundscape Palettes with no playback conditions do not activate

Soundscape Palettes with empty playback conditions fail to activate ...

NV12 and NV21 pixel formats are not working correctly

Material functions using Vertex Interpolators called by multiple function nodes will only use the final interpolator result

The interpolator in each function call does correctly compile it's input to a temporary, but as there's only one actual expression node, each call stomps the temporary data so the final CompileInput ...