And when I use the AND gate followed by a NOT, it works just fine. However if I use the NAND gate, it does not.
Basically what happens on the nand gate is that when the report turns false, after a few ticks, it’ll turn true even if it shuold just remain false, with the and not gate it stays on false as it should (this code goes into an event tick node that sets the world rotation and target arm length to the values i’m testing against in the in-range nodes, so once that value is roughly reached, it should always be staying on false)
Also interestingly, the nand gate sets itself to false too soon, e.g. if I use the nand gate there’s a bit of a stutter at the end of the camera motion, whereas with the and not gate it’s completely smooth as it should be.
Ah… I was wondering if it using short circuit evaluation.
The way to know for sure is to open the source in Visual Studio, you can just double click the node ( I don’t have VS just because of space constraints, and I don’t use CPP ).
Can confirm that this is the case, only thing that I can think of is that it’s NAND’ing each individual pair of values? Because typically operators only have two arguments, so I assume there’s some strange behavior happening when there are three or more input pins.
)?