Landscape material Issue

Hi, I am currently working on my open-world landscape, painting materials and stuff, but I have stumbled upon an issue that I couldn’t find anything similar to online. There is some random kind of blacked-out zone across the whole map. It shouldn’t be any type of shadow or anything like that.

The interesting thing is that when I edit the landscape, the affected component makes it disappear, which is even weirder.

This issue occurred after I reworked my material from HeightmapLayerBlend (which was kind of pointless since the textures are simple colors) to WeightBlend, which is definitely more suitable for my case.
So, has anyone got any idea what could be happening?

Hello there @AdamGaming_CZ!

From the looks of your screen samples, that seems like a missing/corrupted layer. Since you recently switched from HeightmapLayerBlend to WeightBlend, the cache may still hold conflicting data.

The first approach would be to re-assign layer and ensure the landspace is using the proper elements. Go to Landscape Mode, check the Paint tab, and review your layer list. There, you can re-assign your assets to force a refresh.

The next step, would be to clear any old shader data. If your landscape is using Nanite, locate it’s actor in the Outliner, navigate to the Nanite section, and click on “Rebuild Data”. On the other hand, if you are not using Nanite, you can check the Build menu on the top bar, then click on “Build Landscape”. Both options should force a refresh of all baked data.

I am not saying it’s happening here, but if you are using RVTs with your landscape material and the volumes don’t fully cover the landscape, that issue will visually present as we are seeing here (this strip can have multiple causes).

Otherwise I agree it’s likely cache-related somehow. Trey a build-landscape/all levels, or even close/reopen the project.

Tried everything, rebuilt plenty of times but still nothing. Also the issue was there long time ago before the transfer from HeightBlend to WeightBlend, i asked about the issue here, but nobody responded.