My setup above:
the first 2 variables (new incoming | which loop new) are 1 & 2 → not equal = FALSE
the 2nd 2 variables (new variation | current variation) are 1 & 1 —> equal = TRUE
I’d expect the AND node to send FALSE - since not both nodes are TRUE
but it sends TRUE! how come?
I’m simply looking to send True only if both conditions are True, and false otherwise.
Are you extremely sure that’s the value of your variables? Have you tried it with PrintString (without relying on what the blueprint debugger tells you)?
I’d be careful with that 100% AND is only true if both of its input pins are true.
Just to confirm… I can see that you are using the False pin of that Branch, is that what you want? That’s like saying NOT AND.
Here is a video example of showing that one value is 1, the other is 2,
but the condition of them being equal comes out as TRUE //
and yes I basically only want to continue if it’s False.
I have a
Loop Number
Variation Number
So if both NEW loop number + variation number match the CURRENT ones - it means “don’t do anything”
If NEW loop number or NEW variation number changed, then DO something.
As mentioned before, please don’t rely on the blueprint debugger. Just print out all float values, and you’ll see that they are different from what the debugger tells you.
The two tasks which update the variables and then execute the AND function were not executed in the right order, even though I set it to.
That caused the AND to be calculated before the variable was updated.
The debugger was showing things correctly, just didn’t take into account when the AND was calculated and showed the final result.
Thank you all for your help and sorry for this being actually my mistake !