Been noticing this for some time, but now I’m pretty sure it’s broken.
For example if you search “Set Material” with the context sensitive.
the Set Material node will not appear, but if you off the context sensitive it’ll appear.
However this node is word by word correct
This is actually ‘by design’. When in ‘context sensitive’ mode, the context menu will only show functions you can do to THIS BLUEPRINT (plus library functions you can use anywhere). Because you can’t call Set Material directly on Actor, t won’t offer it to you. If you drag off a StaticMeshComponent pin (for example) and release, it will offer it to you, because you can call it on that. Similarly, if you made a Blueprint off StaticMeshActor, you would see it in the background context menu, because you can call SetMaterial on a StaticMeshActor.
I hope that helps!
Im wondering if perhaps components variables should be accessible to the owning actor from within blueprint. Ive had an instance where Ive dragged out from self (being a character actor) and it actually created a link to the movement component for me because thats where the functionality pointed to.
Ahh yes it was when linking self to Is Moving on Ground, it created the CharacterMovement node but you cant actually create a Is Moving on Ground from self (being Character). That does seem odd to me since blueprint is obviously smart enough to know about an Actors Components.
Hi Jeremy,
I am not certain whether this behavior in this case is intentional or not, but I agree it does not behave as expected. I have reported this issue.
Thanks!