Here is a basic blueprint script. Even though they are not conneted by execution pins, “Test Var” Bollean is both true and false at the same time.
And the result is:
If you think creation order of the events are might be important
This gives the same result.
I would like to understand how this happens.
And you are 100% sure the initial value of the bool is not false?
Yes, to be sure
Here is the modified version
and results:
Might still have something to do with the order the compiler outputs the bytecode in. Try the DISASMSCRIPT BlueprintName command in the editor console and see where the output differs.
I believe it runs both, which sets it to false and then prints, have you tried putting a string after the Set to false that says for example “Setting to false” and seeing the order of running?
Also why are you separating the inputs like that if they branch at a boolean anyway?
Hello GenarAlt, Welcome to the Forums.
This reminds me of the discussion around short-circuiting. Just wanted to link that as you might find it interesting.
Another element you could add into your experiments: If you create a ‘Delay’ node with a time of ‘0’ it will delay for one frame.
