Search Issue Tracker
Duplicate
Votes
7
Found in [Package]
1.1.0
Issue ID
1167270
Regression
No
Playable Director keeps the old and unused bindings as dependencies after the Playable Asset is changed
How to reproduce:
1. Open tester-submitted project (project_699397)
2. Open the prefab 'GameObjectDirector 1' outside of Unity with a text editor
3. Note that the PlayableAsset and SceneBindings reference the same object
4. Back in Unity Editor open this prefab and change the PlayableAsset
5. Open the prefab again with a text editor and see its serialization
Expected result: prefab does not contain any old bindings that are no longer used
Actual result: prefab retains the old bindings that are no longer used
Reproducible with Unity versions: 2017.4.31f1, 2018.4.5f1, 2019.1.13f1, 2019.2.0f1, 2019.3.0a11
Reproducible with package versions: 1.1.0
Comments (1)
-
GameEver
Jul 23, 2020 20:16
I was struggling with this too! I didn't understand why the memory error was happening until I accidentally looked at the timeline with debug on, and i couldn't believe this. This needs to be fixed.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
- Loading animations are hitching or stopping when using "SceneManager.LoadSceneAsync" to load new scenes
This is a duplicate of issue #1234687