Search Issue Tracker

Won't Fix

Votes

2

Found in [Package]

1.3.3

Issue ID

ADDR-1050

Regression

Yes

[investigation needed] GameObject Animators become not valid when instantiated via Addressables after a Scene reload

Package: Build Pipeline - Addressables

-

Reproduction steps:
1. Open the provided project "case_1223207-steel-flood.zip"
2. Enter Play Mode
3. Press "ESC" -> "Quit to menu" -> "Start" -> Select a load slot

Expected result: GameObjects with Animators are not made invalid when instantiated via Addressables after a Scene reload
Actual result: GameObjects with Animators become not valid thus disabling the Animations when instantiated via Addressables after a Scene reload

Reproduces on: Addressables 1.3.3 (2019.3.4f1), Addressables 1.6.2 (2020.1.0b1, 2020.2.0a2)
Does not reproduce on: Addressables 1.2.4 (2019.3.4f1), Addressables 1.2.4 (2020.1.0b1, 2020.2.0a2)
Could not test on 2018.4.18f1 due to package errors in the Console

Notes:
-The issue does not reproduce in Build
-Making a New Addressables Build does not solve the issue
-Error message printed in the Console window:

The Animator Controller (FirstEnemy) you have used is not valid. Animations will not play
UnityEngine.ResourceManagement.AsyncOperations.AsyncOperationBase`1:<.ctor>b__27_0(AsyncOperationHandle)
DelegateList`1:Invoke(AsyncOperationHandle) (at Library/PackageCache/com.unity.addressables@1.3.3/Runtime/ResourceManager/Util/DelegateList.cs:69)
UnityEngine.AsyncOperation:InvokeCompletionEvent()

  1. Resolution Note:

    The issue is actually not related to bundle dependencies.

    According to the last user comment in the FB of ADDR-1293, the issue is caused by duplicated assets in memory due to a "design flaw of how asset bundles work".

    Issue should be reassigned to animation team for confirmation. Closing ticked.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.