Landscape Paint Weight Blending is broken

Summary

After this recent patch with the newly added Advanced paint layers, Landscape weight blending is behaving differently as before, where painting using a landscape brush would fully use its weight alpha. Now it seems to be using only half of it, its affected all my maps that are using a custom landscape.

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

Insert a custom landscape material that has basic weight blending and select any paint layer, and paint on the landscape

Expected Result

Painting with a different landscape layer should replace the current landscape layer’s weight alpha, instead of blending both alphas halfway.

Observed Result

Painting with a different landscape layer blends all weight layers together instead of fully weight blending.

Platform(s)

All.

Upload an image


Additional Notes

The second image is the desired result. Materials should completely override each other when painted over one another.

Managed to solve it?

No, unfortunately.

I’m also having the same issue

1 Like

A ton of people are, as well as HLODs not working. Glad it isn’t a “me” problem!

How many expected days should we be waiting for the fix?

FORT-1018114’s status has changed to ‘Ready for QA’. A member of the QA department is investigating the issue.

2 Likes

Tried to report this in another post here as well

I need this fixed, badly. Already started the project using UE 5.7 and this is the only thing I’m having issues

So it’s the end of January 2026 and this bug is still an issue.

I’m honestly struggling to understand how problems like this can persist for so long — especially as the engine continues to evolve and new features are added.

Coming from tools like Houdini and other more robust DCC software, Unreal 5 is brilliant in many ways… but stability-wise it often feels like it’s being held together with hope and a prayer. I’m running into crashes / instability far more than I’d expect at this stage, and it’s seriously impacting workflow.

Is there any confirmed fix or reliable workaround for this yet?