Reference Viewer should show property or properties responsible for reference.

General Feedback & Requests
1

9a7d48c8470503e2f15b0ff8c8a39c35.png
9a7d48c8470503e2f15b0ff8c8a39c35.png904×240 64.8 KB
&stc=1

It would be really nice if the reference viewer showed exactly what the link was between two references. In this example, I see that my anim blueprint is referencing this animation, however, I can’t find out where this animation is actually being referenced from. I’ve searched this blueprint high and low and have no idea what is causing this reference.

2

That would be nice. I’ve tried to use the reference viewer on a few occasions, and every time found it confusing and not very helpful. Maybe I’m missing something, I don’t know. Potentially could be a super useful tool though.

For your problem, have you tried the obj refs console command? That gives more detailed info.


obj refs name=/Path/To/Anim.Anim

Output can be a little overwhelming, but generally you can find the referencing chain you’re looking for in there.

1 Like
3

Aye, that command is my current flow for finding tough but it would be nicer if the viewer can show it within its ui!

4

The reference viewer works off the asset registry data which doesn’t have any more granular info than at the package level (this is how it’s able to work even for unloaded assets). You can use “obj refs” to get much more detailed info but only for loaded references; I’m a little surprised we don’t have that in the right-click menu on a reference viewer tile though. Would be a nice PR :slight_smile:

Cheers,
Michael Noland

1 Like
5

Ayyyeeeeeeeeeeee. D:

6

I have entered a pull request: https://github.com/EpicGames/UnrealEngine/pull/4336

7

Hello,

I know this is an old thread, but the issue still comes up regularly.

Epic added the “Resolve Referencing Properties” option in UE5, but in practice I’ve found it a bit unreliable or incomplete in many cases (especially with more complex assets).

I ended up building a tool to address this for my own workflow, mainly to reliably identify which property (and where) is actually holding a reference. It helped a lot when tracking down unexpected dependencies.

I’ve packaged it as a plugin in case it’s useful to others:

Hopefully this can help someone hitting the same limitations.

Cheers!
CreaTech