Connecting different terrain heights?

I'm using the 2018.3 Beta to create a large slope made from multiple connected terrains. I'm having an issue where these terrains all have the same base height, meaning I can't have terrains next to eachother and use the smoothing tool to close any gaps



Here the terrain on the right has a y position of 200 and a height of 0, the terrain on the left has a position of 0 and a height of 200.

Is there any way to get them to align properly?

 

Set the terrain with the height offset down again and use a script to adjust the height data to match the offset (+200) (https://docs.unity3d.com/ScriptReference/TerrainData.GetHeights.html & https://docs.unity3d.com/ScriptReference/TerrainData.SetHeights.html)

 

My solution when I was working on this was unfortunately to just take the generation outside of Unity then check what each cell (terrain) lowest and highest point was and do it manually (to maximise resolution). Because if this isn't done, the terrain slowly loses precision on height. Would just try automating that if you can't find a workaround.

If you can get away with a single higher resolution terrain it'll save tears in the long run.

 

I tried this but the heightmap values are normalized values between it's lowest and highest point meaning I can't go above it's predefined maximum height.

 

You should be able to calculate the appropriate values with https://docs.unity3d.com/ScriptReference/TerrainData-size.html or https://docs.unity3d.com/ScriptReference/TerrainData-heightmapScale.html not sure which one

 

Thanks for your help but I couldn't get it working the way I wanted. For now, all terrains are using the same max height which is working fine. This is ofcourse not ideal because as soon as new terrain parts are added that need to be higher than 2000 problems will occur.

 

What if one could just convert a heightmap-based terrain to a mesh-style terrain -- Then one could use a mesh+polybrush sculpting approach to particular terrains here.

The only difference would be how the two render (to an extent), but it would make this extra-hacky programming a moot point. This hacky way of programming is what screwed Unity's editor in the past. :/