Search Issue Tracker
By Design
Votes
5
Found in
2017.3.0f2
Issue ID
978272
Regression
No
Select Dependencies displays assets that are not present in scene
How to reproduce:
1. Open given Unity project
2. With the right mouse button click the "SpeechUI" and select "Select Dependencies"
-- Notice that "Views" and "SpeechUi" became marked
3. Open "SpeechUi" scene
-- Notice that there is no visible presence of the Views prefab
Expected result: Prefabs that are not in scene should not be selected when selecting dependencies
Actual result: Prefab that was in scene is marked when selecting dependencies
Reproducible with: 5.5.6p1, 5.6.4p4, 2017.1.2p3, 2017.2.1p1, 2017.3.0f3, 2018.1.0a7
-
michaelday008
Dec 30, 2019 04:50
Unity 2019.1.10f1 I have an empty scene with literally nothing in it all.
Select dependencies finds a hundred objects and prefabs that used to be in the scene a long time ago but were since deleted...
Strangely I found a workaround. Even though I had deleted all the navmesh data and lightning data and associated folders, the scene apparently still had some hidden reference to them. Once I re-baked the lighting and navmesh in the COMPLETELY EMPTY scene, the references went away...
-
michaelday008
Dec 30, 2019 04:46
Unity 2019.1.10f1 I have an empty scene with literally nothing in it all.
Select dependencies finds a hundred objects and prefabs that used to be in the scene a long time ago but were since deleted...
-
joaobsneto
Sep 28, 2018 19:36
I'm having this problem too. Unity 2018.2.2f1.
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
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- Dynamic text is rendered in the background when it is inside the <font> tag
Resolution Note:
This is by design because there actually is a dependency on the assets. These dependencies simply live in prefab overrides that are no longer visible, but we are building tooling to surface these redundant overrides on prefab instances.
Keeping the behavior as it is right now would allow you to detect these redundant overrides and cleanup your project