Landscape normal behaves differently on CPU vs GPU

One of our licensees encountered this issue. Landscape normal is calculated differently on GPU vs CPU.

See screenshot below: left is GPU (with Edit Layers enabled) and CPU (Layers disabled)

[Image Removed]

This is a summary of what they discovered about the cause of this problem:

[Image Removed]

They'd like to know if this is by design, and if so the reason behind it. Either way they want a way to get 'correct' normal on GPU since the CPU normal is of higher quality.

1. Open the reproduce project attached
2. Open the map "Main", a post process volume has been setup to display World Normal
3. See how the two landscapes have different normal quality
   The left one is GPU, with Edit Layers enabled. Notice how normals appear 'chunky' in steep areas (top part) and have weird bumps in smooth areas (bottom part)
   Notice how the right one (CPU) yields much better result.
4. You can try reimport Heightmap.png to both of the landscapes, results won't change

Additionally, if you disable Edit Layers of the left landscape, the result won't immediately change, it still inherits normal from previous GPU result. You need to reimport Heightmap.png or do sculpt editing to 'refresh' the normals.

How does TextureRenderTarget2D get TArray<uint8> type data?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

Why does the REMOVE method of map container remove elements have memory leaks?

How to delete some elements correctly when deleting an array loop?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

How do I set a material as a post-processing material?

UMG RichText not appear image when packaged

How would I go about lerping the rotation instead of it snapping when turning (pls dont sue me epic)

What is the difference between Camera and CineCamera?