[BUG Report] 'Event on Movement Mode Changed', triggers faster than 'Event Begin Play'

Hi everyone,

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.

Regards,

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…

In theory event begin play should come first. But in my example it seems it doesn’t. The string below always fires first and higher a string be on the screen, later it was fired. First reproduce it, then you will understand. Try printing an array of integers inside a for loop if you doubt on screen printing order.

Regards,

you are right, i just checked it… ive been working too many hours lmao… you could just use a delay on your on movement changed? or from event beginplay → bind event to movementmodechangeddelegate… that way it will only fire after begin play

I’ve tried using delay node before but for some reason, it didn’t solve the problem. But I haven’t tried using delegate yet.

you can even do it in blueprints, theres a node called movement modechanged delegate

Facing this same issue too. Have you solved it?