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
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
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
- No option to skip video transcoding when launching a Project
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
MateusWinwin
Nov 22, 2019 17:38
Not fixed... 2019.2.9f1
EyePD
Jul 10, 2019 21:26
This is not fixed in 2019.1.5f1
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...
Cubequad
Jun 23, 2019 12:29
Not working for me in 2019.1.7f1. This is crazy...
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.
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 ?
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.
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.
LorenzoNuvoletta
Sep 27, 2018 21:53
Doesn't seem to be fixe din version 2018.2.8f1
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.