Why are multiple terrains slower?

Hi! Ahh, I didn't think about that! Thanks! I'm currently only using one and the same texture for all terrains, no normal maps or anything. I kind of assumed that the texture was re-used, but because there's no "material" used, I guess it isn't.

I'm currently setting the texture by this code:

 SplatPrototype[] terrainSplats = new SplatPrototype[1];
 terrainSplats[0] = new SplatPrototype();
 terrainSplats[0].texture = terrainTexture;
 terrainSplats[0].tileSize = new Vector2(3, 3);
 terrainData.splatPrototypes = terrainSplats;

I'll look into improving this. $$anonymous$$aybe I can work with the "$$anonymous$$aterial" slot that's found in the terrain settings directly ins$$anonymous$$d, so that I can use the same $$anonymous$$aterial for all terrains and apply textures to the material ins$$anonymous$$d of the terrain.

But if I need more detailed texturing through splatmaps I guess there's no other way than to have unique textures for each terrain. I'm also planning to combine it with RTP terrain shaders from the Asset Store later, which will multiply the texture count by a lot.

Another solution would be to use fewer but bigger terrains, but then the main problem is that terrain.setHeights causes a lag and there's no way around that from what I've heard. Really hope Unity improves on that part.

After experimenting some more, I'm afraid this might not be related to texture lookups either. Even after I disable the above texturing code, which makes the terrains completely white without any texturing, I get the same frame rate. Reducing poly count does nothing for the frame rate either.

There just seems to be some strange performance overhead on using multiple built-in terrains that I can't get rid of. This is very unfortunate as it means I'll either have to sacrifice a lot of viewing distance or suffer from lag when generating larger terrain chunks procedurally.