Unreal Engine Issues

Using a Dynamic Material Instance on a Nanite Landscape doesn't work

Networked root motion montage with rotation fighting smoothing

A licensee is reporting a sim proxy is playing a networked anim montage with root motion, that the rotation changes will fight between what's produced in ::SimulateRootMotion and ::SmoothClientPosit ...

SubVersion: MakeWritable files prompt for checkout on every save

Nanite and mobile landscape don't have support for dynamic materials

On a landscape actor with Nanite landscape enabled, set the bUseDynamicMaterialInstance property on a landscape proxy and setup a BP to call  SetLandscapeMaterialTextureParameterValue / SetLandscape ...

Blueprint diff tool displays diffs for animation blueprints with no changes

From UDN: [Link Removed] ...

Ensure/failure when changing the class of a scene component that has bVisualizeComponent enabled

Failure occurs at compile time during GC when the replacement component that we create is being destroyed. This component includes the BillboardComponent instance that's attached to the scene compon ...

Separate translucency rendering and material BumpOffset UV issues

It appears as if the primary screenpercentage is being sent as the screen size to separate translucency materials, even though separate translucency has its own screenpercentage (r.SeparateTransluce ...

Overriding a struct member field's default value on a BP-added component in a BP asset will no longer allow the user to edit that struct member on instances of that BP's component if the member is deprecated.

Properties that are deprecated are (incorrectly) not currently being propagated to instances by the duplication logic that we use to instance BP-added components as part of Actor-based BP constructi ...

Reintroduce UE4 Material Layer drag & drop behavior in UE5

This behavior has changed from UE4 to UE5 due to a fix to an unrelated bug ([Link Removed]). Reintroduce the old behavior without causing a regression that reintroduces Ben's fixed bug. ...

Deprecating a non-const blueprint interface function replaces the implementation of the event with an empty custom event

This behaviour is only observed when implementing the function as a custom event from a blueprint interface. This behaviour is not observed in actors where the blueprint interface function is implem ...