Quick answer: Use LayerBlend nodes set to LB_WeightBlend consistently, add a base layer to fill remaining weight, and ensure the layer info objects are weight-blended so the totals normalize.
Washed-out landscape painting means layer weights aren't summing correctly. Consistent weight-blend setup and a base layer fix it. Here is how.
How to fix it
1. Use consistent LayerBlend type
In the landscape material set every layer in the LandscapeLayerBlend node to LB_WeightBlend (or height-blend) consistently; mixing blend types corrupts the normalized weights.
2. Add a base fill layer
Include a base layer that absorbs the remaining weight so areas you have not painted fall back to it instead of leaving total weight below one and washing the result out.
3. Check the layer info objects
Ensure each paint layer has a weight-blended Layer Info object assigned; a non-weight-blended info object on a weight-blended material breaks normalization across layers.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every Unreal Engine error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
A crash you can name from its stack trace is a crash you can usually fix in minutes.