Trying to make a build with addressables.
It always gets stuck on calculate scene dependancy data (cached).
The scene is two rooms in a 2D platformer game.
And the build time looks over >30min before I had to task manager kill Unity.
Is this another new Unity technology that is half cooked?
So we are better to just using the older asset bundles since this one cannot be built.
Same issue here. Adressable Analyze is super slow on Unity 2022.3.16.
Most of the time is stay stuck for hours… only way is to kill the editor.
Was working fine with Unity 2021.3.
Same issue here. We just started experiencing this during development, without having done any updates to addressables or Unity. Tried updating (both), to no avail. The only way to create builds at all is by clearing the cache first (Addressables Groups → Build → Clear Build Cache → Build Pipeline Cache).
See also: Addressables Build Cache makes build absurdly slow
It’s odd that you’d start encountering this issue without any updates! It definitely seems to be caused by a specific change in ScriptableBuildPipeline@1.21.21, used by Addressables@1.21.19
The issue lies in a weird combination between 2022’s internal UnityEditor.Build.Content.ContentBuildInterface.CalculatePlayerDependenciesForSceneInternal_Injected method, and changes to UnityEditor.Build.Pipeline.Tasks.CalculateSceneDependencyData.Run().
Oddly enough, the issue doesn’t seem to appear when I tested these same versions of a Mac, or when using 2021 with this version of SBP and Addressables. Windows seems to be insanely slow at the underlying CalculatePlayerDependenciesForScene method in 2022, which in turn makes the recursive nature of CalculateSceneDependencyData exceedingly slow. I’m sure there’s more to it than that though.
Alternatively to clearing the cache (which doesn’t help with analyze, as analyze seemingly runs multiple builds), you can edit your manifest.json to forcibly downgrade com.unity.addressables to 1.21.17 and com.unity.scriptablebuildpipeline to 1.21.9
This avoids the issue introduced in ScriptableBuildPipeline 1.21.21 when used with 2022 LTS.
You can also try manually fixing the issue introduced in 1.21.21 by following the instructions in this thread: Building addressables with cached elements using ScriptableBuildPipeline 1.21.21 EXTREMELY slow . This method involves using a local copy of the ScriptableBuildPipeline package to avoid the broken upstream.
In theory this issue should be resolved in the next version of SBP, which @unity_shane stated should be released by the end of January. There are multiple threads about this issue currently, so it would be nice to see some sort of official messaging from the Unity team to avoid further frustration from users. I’d expect to see this sort of problem in the Known Issues for an editor version.