@L1z4rD89 or anyone.
-
What am I doing wrong with this BPI?
-
Without a tutorial I am unclear what to set an Input and Output (at BPI creator window), or what to put as the Target (when using the BPI message Node)?
. -
Do I need to use a ‘Set Variable node’ after a BPI message node? Or does BPI pass the Input variable > to whatever the Power Output Pin (white) is connected to?
. -
Is Target = the Variable? Or are only “Inputs” variables (which I add at the BPI management window)? (Im unclear what to do when the Target is also the Variable that I want to pass)
-
Why is this Variable read-only, when I made it and checked boxes?
.
.
@TheKaosSpectrum Why? 2020: were you speaking of an older version limitation?
Is it because C++ limitation, cant expose the variable in BP?
Why would Epic give us a selectable setting (Particle), yet not give us a way to change it live in Game using BP - when they know we want to Get/Set everything?
Without knowing your reason, it’s frustrating because Epic gave us a way to add the Override BP (our version of Trail Notify). But it’s not working as shown above. And Idk if there’s a hardcode restriction or if my nodes are wrong??? Please help, ty.