That’s the culprit - read the tooltip of the node to find out what it really does. It cannot be used to communicate reliably if there’s more than one actor of class.
value from widget inside a widget → called to the Blueprint A
This is a bit of a vague description so I’ll need to assume some things:
- in the widget:
Pressing a button sets an integer value and calls a new event dispatcher:
- in the actor owning the widget component:
We find which 2d widget the component is holding onto, and bind the above-mentioned dispatcher to a custom event in the actor:
Alternatively, if it’s the actor who wants to pull a value from the widget instead:
Both will work, but work slightly differently.
to control the scalar parameter value on material from another Blueprint B.
Now, this is new. We’ve now sent a value from a widget component to the actor A.
- what is actor B?
- what is its role and purpose?
- where is it?
- is there even any need for sending the widget value to actor A in the first place, only to propagate it further to another B actor?!
Perhaps there’s no need to be cryptic about it. Maybe you could tell us what you’re making? It generally makes it an order of magnitude easier to suggest a tangible solution that fits your needs.
What is happening? We move a slider in an actor’s widget and send its value to another actor’s material to simulate light direction? How close am I?! 