Search Issue Tracker

Fixed in 2019.1

Fixed in 2018.3

Votes

18

Found in

2017.3.0b10

Issue ID

970903

Regression

No

Find References in Scene shows objects that are not referencing the asset

Scene Hierarchy

-

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 (16)

  1. 4fa85ad1215b84d57a1f5c1085255659?d=mm

    _watcher_

    Feb 25, 2020 10:14

    NOTE: for people complaining that this bug still exists in 2019.3, read the bug report full body message. That might be fixed.

    What is not fixed in 2019.3 is that if you rightclick an asset in project window and select "Select Dependencies", the results shown in Hierarchy window list objects that have no dependencies to the target object.

    If you want that fixed, file a new bug report. Cheers!

  2. 3397e68ad576561a47b6817e99101b13?d=mm

    QuincyC

    Jan 20, 2020 16:30

    This is NOT fixed in 2019.3.0f3, which is making my job really hard right now.

  3. 4b7de6d36068f703fc18475853caf1bf?d=mm

    Robdon

    Dec 13, 2019 12:19

    So this has been open since 2017, and it STILL doesn't work.
    Tried in version: 2018.4.13f1

    Have to say, that's a spectacular fail from support when they can't even make a simple search routine work :(

  4. 73064b9cb0c67721ed65ad5c442551d0?d=mm

    EyePD

    Dec 05, 2019 21:52

    This is not fixed in 2019.2.15f1

  5. 882056d85986aba6e63907e1cdae90d7?d=mm

    MateusWinwin

    Nov 22, 2019 17:38

    Not fixed... 2019.2.9f1

  6. 73064b9cb0c67721ed65ad5c442551d0?d=mm

    EyePD

    Jul 10, 2019 21:26

    This is not fixed in 2019.1.5f1

  7. 372c5f32b49c3b001b542d3e418860f1?d=mm

    Cathero

    Jul 05, 2019 15:50

    Frustratingly enough, not only does this not work (as in "provide a correct result") with Unity 2018.3 here, but on top of that it also ends up *fully freezing Unity for several minutes* on some scenes, before eventually unfreezing and displaying a result (which is, of course, a completely wrong and pretty much unusable result anyway, as described in the issue).
    Freezing Unity for several minutes is just really not helping...

  8. 67cf7af260a819ff686d1a74aa00a966?d=mm

    Cubequad

    Jun 23, 2019 12:29

    Not working for me in 2019.1.7f1. This is crazy...

  9. Ec885e30e43007d37c344dadb10b4f96?d=mm

    TWObitEDD

    Mar 28, 2019 18:32

    This resolved status is frustrating to anyone not using 2019.

    Millions of people are in full production and the fact that this issue isn't even something I can even draw attention to is un-professinoal.

  10. 94763840afb0987f6d859a92de90fe13?d=mm

    Rafarel

    Mar 24, 2019 10:38

    So the issue is Fixed in Unity 2019.1, but it will be fixed on a 2018 LTS version I guess ?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.