Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
18
Found in
2017.3.0b10
Issue ID
970903
Regression
No
Find References in Scene shows objects that are not referencing the asset
Steps to reproduce:
1. Open attached “FindReferences.zip” Unity project
2. Open “Test" scene
3. Find “Disable" asset in Project tab
4. Right-click on “Disable” asset and select “Find References in Scene”
Expected results:
Only objects referencing “Disable” asset are found
Actual results:
Objects not referencing “Disable” asset are also found
Reproduced in: 2018.1.0a5, 2017.3.0b10, 2017.2.0p2, 2017.1.2p3, 2017.1.0a1
Fixed in: 2019.1.0a4
Comments (22)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
MechEthan
Aug 10, 2018 16:51
Are there any workarounds for this? It's frustratingly useless.
I end up having to dig around in the YAML file by hand and cross reference opaque ID strings.
Please consider bumping the priority on this issue!
pixelsage
Jul 19, 2018 20:29
Very useful, yet this hasn't worked ever since I first started using Unity (probably at least since version 4).