Ok, I found the issue about the missing refs, but the self ref is still not working properly.
Now the number of refs they keep is correct but they keep a self ref for each one, so 1 correct ref is lost for every bp that received it. I don’t understand why
What message do you see when you mouse over the Self warning?
@ClockworkOcean
this one
so…my friend…that time has finally come..hasn’t it?
Because you don’t like macros?
no no, It was to laugh a bit.
Because I guess I’ll have to delete everything and redo it. Never done a macro before, I don’t know anything about it. Should I be worried?
It feels very like making a function, but the code actually gets compiled into your blueprint graphs, whereas a function is actually a separate object.
I just thought of a way to bypass the self ref in the function, but I still want to try with the macro, also because what I thought is not very elegant perhaps. Anyway, thanks a lot for the help sir!
![]()
good morning @ClockworkOcean
I’m noticing that macro has not exe pins in input/output
Is that normal?
I manually entered the exe pins but now even though I recreate the macro variables in the bp, I have an error on them, and it also says that self is not valid
While waiting for your answer, I solved it by keeping the function library, adding the ref as input, so now I will pass it between the bpi call and the function library call, so I have no errors of any kind. Now everything works, anyway, thank you very much! Maybe I need more time for the macros, to understand all the differences between macros and functions and exploit their potential to the fullest.
Yes, that was also an option ![]()
Generally, functions are better than macros. But it really depends on the situation.






