Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X
Votes
0
Found in
2019.4.21f1
2020.3
2021.2
2022.1
Issue ID
1384729
Regression
Yes
Console messages show no path to assets in StateGroup when checking dependencies with AssetDatabase.GetDependencies
How to reproduce:
1. Open the attached "bundle_dependencies_demo_project.zip" project
2. In the menu bar select Demo > Calculate Dependencies
3. Check the messages in the Console Window
Expected result: Console displays messages: "Dependencies of (path to the asset in state): (path to asset in StateGroup)"
Actual result: Console messages display only the path of the select asset but not its dependencies path
Reproducible with: 2019.4.21f1, 2019.4.33f1, 2020.3.24f1, 2021.2.6f1, 2022.1.0a10
Not reproducible with: 2019.4.20f1, 2022.1.0a11, 2022.1.0b2
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a11
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.9f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.27f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.35f1