Blueprint Macro Delay bug
When using delays inside macros, if the same macro is used in two places (A nad B) and B is executed while A is waiting for delay to end, then B is 'canceled' as soon it gets to the delay node.
I'm not sure but i think this problem did not happen to me in 4.12. I made a youtube video to better show the problem.
asked Sep 03 '16 at 11:44 PM in Bug Reports
Thank you for reporting this issue. I do believe this behavior is intended due to the way delays work but I placed a bug report in seeing as the behavior is different from 4.12.5. You can find the bug report here and track it for updates.
Have a nice day!
answered Sep 06 '16 at 03:54 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here