Neighbour terrains always null on execution

I created neighbour terrains with the terains tool.

After adding several of them, on my script I'm using the varaibles:

Terrain myTerrain.topNeighbor
Terrain myTerrain.bottomNeighbor...

But all of those variables are null, even when there is a connection. How can that be possible? They all have the same GroupingID, reconnected, and when I draw over it, it seamesly paints from one to another.


What is happening here?

 

Here's a script I add to a center terrain with neighbours around it.
Nothing is printed.

This seems like a bug.

Code (CSharp):

1. var ter = GetComponent<Terrain>();
2.  
3.  
4.         if (ter.topNeighbor != null)
5.             Debug.Log( ter.topNeighbor.name);
6.  
7.  
8.         if (ter.bottomNeighbor != null)
9.             Debug.Log(ter.bottomNeighbor.name);
10.  
11.  
12.         if (ter.rightNeighbor != null)
13.             Debug.Log(ter.rightNeighbor.name);
14.  
15.  
16.         if (ter.leftNeighbor != null)
17.             Debug.Log(ter.leftNeighbor.name);

 

I uploaded a 250kb empty project with a simple setup. And yes, it prints the terrain name perfectly. But no neighbor variable is different from null.

You can download it here.
https://drive.google.com/file/d/1uZxHhutpdVB9vZUNWDuh3wweAlTj_qg-/view?usp=sharing

Here is what I did:

1. Create project
2. Create a Terrain on the sample scene (create 3d object -> Terrain)
3. Edit terrain by painting 3 more neighbours around it
4. Add script (same code as before, adding the Debug.log you mentioned) on Start() and attach it to the center terrain (the first created).
5. Play . Only the terrain name is printed.

I'm using 2018.4.10f . I'm working on a long-term project and we can't move forward due to the Network capabilities that are removed. We are working on that.


Thanks a lot

 

Oh. That's interesting. Thanks a lot. I'll try that.

 

@ChrisTchou Thanks for your suggestion. If anybody is interested, on version 2018.4 it is done this way:
UnityEngine.Experimental.TerrainAPI.TerrainUtility.AutoConnect();

But I'm not allowed to use Experimental code on production, so I'll have to wait until it is connected.

Thanks!

 

I've checked that while not in playmode, connection is reliable but in playmode it takes that time. Why? Can't it just autoconnect when the terrain initialize? Currently it's not robust as terrain tiles can be created at any time.