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.
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?
Why does the REMOVE method of map container remove elements have memory leaks?
How to delete some elements correctly when deleting an array loop?
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)
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-95444 in the post.
2 |
Component | UE - LD & Modeling - Terrain - Landscape |
---|---|
Affects Versions | 4.25 |
Target Fix | 4.27 |
Created | Jul 16, 2020 |
---|---|
Resolved | Feb 10, 2021 |
Updated | Nov 28, 2022 |