How can I make Find References In Scene work proper?
I stumbled across this problem a couple of times. Using the "Find references in scene" functionality of an asset not only shows the game objects that use this asset but also many other gameobjects (maybe nested ones?) that do not use this asset.
For example: I am looking for all gameobjects of a scene that have a specific AudioClip referenced in a script. When I select "Find References in Scene" on that audio clip, I get an endless list of gameobjects that all not use this audio clip.
How can I solve this?
Hello,
I noticed that too...
right click on a material and "Find references in Scene" will select like ALL objects in the scene while only 20 or so of them have that mat.
although, it does seem to work properly sometimes, (with simple scenes)
I just don't get what makes that fairly simple function fail ??
That "Find references" function use to work perfectly well. Is it a bug or am I doing something wrong ?
please Unity devs, enlighten us.
I have the same question… it'd be such a useful tool if it actually worked!
There's an issue tracker for this but it was marked as resolved in 2019.1. It's definitely still broken in 2019.2.15f1. This is a really useful feature; does anyone know the best way to bring this problem to Unity's attention so the issue can get reopened?
Answer by funkyboy · Jul 20, 2018 at 09:52 AM
Hello !
I found a potential workaround for this, but the reason is still quite unclear.
The case is this :
I have an object in the scene containing hundreds of parts with mutliple materials.
prefab isn't broken (object is blue)
now I select one material and click on "Find references in Scene"
every objects in the scene will be selected...
now i break the prefab (just deleting/reparenting an object)
again I select one material and click on "Find references in Scene"
just the linked objects will be selected...
(allows me to identify those objects, thne i undo to unbreak prefab)
It works for me in those conditions, havn't tried everything.
bit weird since it used to work every time
(and i tried that on 2017.3.f1, no other version yet)
hey, if you're still here, could you explain this better? This same issue is causing me a lot of headache.
Same problem. It also seems to affect how addressables find dependencies. v2019.4.24f1.