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

  1. 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 ?

  2. A701cd6fc145cac4ec3b0d09ddd6fbb4?d=mm

    AppBite

    Mar 15, 2019 23:15

    Any update on this? I'm using 2018.3.8f1 and "Find References in Scene” will 'find' every object in the scene, even when that texture is only attached to one thing. I don't need this function often, but it previously worked.

  3. Dc1b254760f44d16cd4f684456bf554f?d=mm

    karl_jones

    Oct 02, 2018 09:45

    The fix has not made its way into 2018.3 yet. It will be backported during the beta phase. Keep an eye on the release notes for the exact version.

  4. 89172c3d6482e9ba1f584159111d520e?d=mm

    LorenzoNuvoletta

    Sep 27, 2018 21:53

    Doesn't seem to be fixe din version 2018.2.8f1

  5. 8b209b1cf98078b4c8bf831d3f2520d1?d=mm

    akaivo

    Aug 24, 2018 15:59

    I'm guessing by how it works in our projects that it is showing all the nested gameobjects. Renders the whole feature more or less useless. Would be an extremely useful feature if it was working like expected.

    It feels like it shouldn't be too hard to fix and would benefit a lot of frustrated developers/designers.

    Think about all the wasted man-hours.

  6. 022c156d76ef8c3212a324c252fa9fbe?d=mm

    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!

  7. 132de49dd7da9f497e60e2b5bbc3b9fa?d=mm

    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).

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.