I have a fairly simple landscape material that I’ve been working on and I decided to look at the quad overdraw for some of my plants and discovered that the landscape is bugging out showing all different kinds of overdraw for individual tiles of the landscape. The same thing happens with shader complexity as well. I’ve cut down the landscape material as shown in a picture below and I still experience this issue.
This only happens with landscapes, test levels and the default level don’t have this problem.
You can cut down the material all you want.
If your layer blend has 100 layers and your tile has more than 3 painted layers onto it the cost is high and only going to get higher.
However - and regardless of that fact - it appears more likely that you have something like plants on the landscape which are causing the higher costs based on distance/lod settings.
Before you get to “the engine is bugged” (which it probably is btw, its only gotten worse these past 5 years) - you need to do a test on a level with just a new landscape and a single painted layer.
If that cycles on/off in cost like the video above then you can
*A) be sure its an engine bug
*B) realize that its time to stop using landacape and adopt meshes in its stead 
I’ve created a brand new blank level and the problem still persists. I didn’t even have a material assigned to the landscape yet and the overdraw/shader complexity was tiling in and out in chunks.
I assigned a new landscape material with only a single texture and the problem was still the same.
My first example was relatively simple with only 4 different landscape textures on a single landscape layer. The foliage has some overdraw, but it was still in the green. The landscape itself is the issue here. The tiling only exists on the landscape.
1 Like
You need to check if it is a display issues - meaning perfoemance is fine but the display is broken - or a real issue.
I would check to see if a related ms cost spike shows up on the gfx whenever the tiles abruptly change.
If its only a visual, you can live with it.
If it also guts performance you have evry right to go up in arms about it…
Specifically considering how bad landscape perfoemance is to start with…
Pa: assuming this is a result of Nanite?
