[BUG Report] 'Event on Movement Mode Changed', triggers faster than 'Event Begin Play'
I was trying to set a component's relative location to a variable by getting its value on the event begin play, then by another event (event on movement change), use that variable. But then I noticed that the variable, sets its value to (0,0,0), (the value that appears after compiling a vector variable). After trying to debug, I noticed a very weird behavior, which was;
The 'Event on Movement Mode Changed', triggers faster than 'Event Begin Play' !!!
Here, I have created a very simple debugging graph to show you where the bug is;
As you can see, the GREEN text triggers faster than the RED one (because its below the red one). I hope you guys will solve this issue soon.
the text on top actually fired first... there is no way event begin play can come after anything else.. it is literally the first thing.. you can also open up the console by pressing ` and there you can see all the strings printed in order....
the strings print from bottom to top on screen
if you explain some more about your current problem i can try to help you...
you can even do it in blueprints, theres a node called movement modechanged delegate
answered Sep 17 '17 at 05:19 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here