Addressable Terrain Issues

Hi, I recently adopted Addressables as a means to load scenes. For the most part performance is very good, and implementation is very simple.

However I'm having issues with Unity terrains. Most of the scenes I'm additively loading contain a terrain, and for some reason these are causing noticeable hitching.

I've tested loading terrains within scenes with Addressables.LoadSceneAsync and as part of a prefab with Addressables.LoadAssetAsync and get stuttering with both. I don't get any such stuttering with massive amounts of textures or meshes. Even if the terrain is disabled within the scene I get a hitch, or if I'm simply loading it without instantiating within the scene.

Are terrains just not suitable for addressables? Is there something I'm missing? Tested with 1.8.4 and 1.13.1. Any help would be appreciated, thanks.

 

Hi @DavidUnity3d, thanks for the response. Actually this is the exact solution I ended up with.... load scene via Addressables.LoadSceneAsync, then once I know that's complete load nothing but the terrain via Addressables.InstantiateAsync.

Interestingly, even with no change the terrain just seemed to hitch things up when being loaded alongside the scene. I even tested scenes that had literally nothing but a terrain element. Terrains just don't seem to like Addressables.LoadSceneAsync.

I had to drop the terrain complexity to get truly hitchless loading. Right now each terrain has a heightmap res of 1025x1025. I would like to use my originals of 2049 but hitching occurred. Interestingly, having higher resolutions texture resolutions doesn't cause the same issues, I can go pretty high with those, and loading more than one splat per terrain. So I'm guessing it really is about preparing the heightmap data.

As a last resort I could probably break up each terrain into even smaller chunks, but that's a bit of authoring I'm not ready to commit to yet.

 

Hi all, I'm having a new issue with addressables and terrains (edit, maybe issue found below).

So previously I had set it up as outlined above, async load a scene, then Addressables.InstantiateAsync a terrain. A little bit of a hassle but it worked fine.

I recently upgraded to a newer version of Unity and now whenever I attempt to Addressables.InstantiateAsync directly on a terrain asset or Addressables.LoadSceneAsync on a scene containing a terrain asset the Unity editor crashes. Builds also crash in the same way. I'm at a loss here, thanks.

Unity beta 2020.2.0b8.3329 > 2020.2.21f1

Edit: So I may have narrowed it down. My master scene contains terrains. I think there might be an issue with the incoming terrains attempting to share IDs and autoconnect to these existing terrains.