jonathan bard 00bb42a672 * Added detection of discrepancies between the landscape material instance's TerrainLayerWeightParameters and the landscape component's weightmap allocations. A recent change (18095319) introduced potential issues with static parameters within landscape component's "parent" material instance constants (the parent MIC of all landscape components from a landscape proxy sharing the same weightmap combination). Loading the map would register these invalid MIC in the proxy's MaterialInstanceConstantMap with a valid layer allocation key, preventing the landscape component from ever "fixing" its MICs until the layer allocation key changed (e.g. by painting with a previously unused layer on a component). When such errors are detected, we now regenerate all of the proxy's material instances in order to update the material and its TerrainLayerWeightParameters with the proper weightmap allocations ...

* Renamed visibility layer name to "__LANDSCAPE_VISIBILITY__" to centralize/simplify the handling of that special layer's name
* Fixed issue with FixupWeightmaps(), that could trigger invalid weightmap usage validation errors when detecting and deleting unused paint layers in components
* Removed deletion of layers with a null layer info in PostEditChangeProperty since it's done, and in a better way (for the base weightmap allocations and the edit layers ones), in PostRegisterAllComponents's FixupWeightmaps

#jira UE-136054
#tests editor, full QA pass by tim.gautier

#ROBOMERGE-OWNER: jonathan.bard
#ROBOMERGE-AUTHOR: jonathan.bard
#ROBOMERGE-SOURCE: CL 18394875 via CL 18394909 via CL 18394912 via CL 18395077 via CL 18395102
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v896-18170469)

[CL 18395111 by jonathan bard in ue5-release-engine-test branch]

2021-12-07 10:18:26 -05:00

..

Private

* Added detection of discrepancies between the landscape material instance's TerrainLayerWeightParameters and the landscape component's weightmap allocations. A recent change (18095319) introduced potential issues with static parameters within landscape component's "parent" material instance constants (the parent MIC of all landscape components from a landscape proxy sharing the same weightmap combination). Loading the map would register these invalid MIC in the proxy's MaterialInstanceConstantMap with a valid layer allocation key, preventing the landscape component from ever "fixing" its MICs until the layer allocation key changed (e.g. by painting with a previously unused layer on a component). When such errors are detected, we now regenerate all of the proxy's material instances in order to update the material and its TerrainLayerWeightParameters with the proper weightmap allocations

2021-12-07 10:18:26 -05:00

Public

Merge from Release-Engine-Staging @ 17791557 to Release-Engine-Test

2021-10-12 21:21:22 -04:00

LandscapeEditor.Build.cs

Touch up of landscape mode styling.

2021-09-20 09:23:33 -04:00