Errors when trying to manually adjust landscape heightmap

[Ben_93]

Hi All, 

This is my first time of using the landscape material in 2.15, but I seem to be having issues trying to make manual modifications to the heightmap. The heightmap itself is generated from Gaea and have used this method previously in 2.14 with no issues. The problems are: 

1. If create another landscape layer to use for adjustments, when I try to use a brush to adjust the heightmap it has no effect

 

2. If I try to adjust the heightmap of the base layer (with the imported data from gaea) then no matter the opacity, blending or height of the paint brush it makes a hole in the terrain.

 

 

Here is a screenshot of the imported terrain settings:

Im sure im doing something silly and missing something obvious but if anyone can help me get to the bottom of this I would very much appreciate it!

 

Many thanks, 

 

Ben

 

[bmyagkov]

Hello!

@Ben_93 to be able to make some additional modification within using second map (the one that you created manually) it's should be switched from "alpha blend" to "additive" blending mode on parameters tab in "heightmap" section here:

Thanks!

[Ben_93]

Hi, thanks for your response!

I already have set this second landscape map to additive and still nothing happens when trying to modify the heightmap

 

[thomalex]

Hi @Ben_93!

What happens if you enable the Rendering Profiler and check the Terrain Reload Tiles and Terrain Reload Bounds counters when painting over the terrain (while having it in the Additive mode)? Do they change?

[bmyagkov]

@Ben_93 You may also need to change the default render order value from zero to 1 or 2 and after that the additional map should be displayed on top of all the other maps which will allow you to make manual changes

[Ben_93]

Thanks both for getting back to me - I can confirm changing the render order from zero was the solution. I thought it is was something small and silly!

 

Many thanks, 

 

Ben

[bmyagkov]

1 minute ago, Ben_93 said:

Thanks both for getting back to me - I can confirm changing the render order from zero was the solution. I thought it is was something small and silly!

 

Many thanks, 

 

Ben

You're welcome!