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
-
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
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
- Graphics Compositor breaks Unity rendering when the "Output Camera" is changed to a scene Camera and one Camera SubLayer is active
- The Editor freezes on RenderGraphViewer.Repaint when entering too many characters in search fields without character limits
- Adding a new SubLayer in Graphics Compositor renders BaseLayer darker and makes it flicker
This is a duplicate of issue #1234687