We noticed that we get an error when attempting to instantiate a prefab variant from a group marked to Pack Separately. The base prefab is in the same group, but since they are packing separately, the base prefab is not getting loaded as a dependency when we try to instantiate the prefab variant. Exception encountered in operation Instance<InstanceProvider>(Resource<GameObject>(TestObject Variant.prefab): Dependency operation failed with System.Exception. If I manually load the base prefab before attempting to instantiate the variant, it instantiates just fine. Prefabs that contain another asset bundled prefab nested inside them seem to fail similarly, although the error is different. They complain that the path to the prefab's bundle is invalid, even though it definitely exists in the Streaming Assets folder. Exception encountered in operation Resource<IAssetBundleResource>(nestedprefab.prefab_f14b9602375de526961ef704004adeaf.bundle): Invalid path in AssetBundleProvider: 'StreamingAssets/aa/Windows/StandaloneWindows64/packedassets_assets_assets/loadableassets/nestedprefab.prefab_f14b9602375de526961ef704004adeaf.bundle'. How much support should we be expecting for nested prefabs and prefab variants in Addressables right now?