Inverted condition issue

Hey newt, I'm opening a new topic to not changing the subject here.

Could you elaborate what's wrong with inverted conditions? I never had any problems with it.

It's been a while, but as I recall "is overlapping" negated was one instance where it gave weird results.

It could vary from not picking to running down the fps.

Hmmm... I actually use inverted "is overlapping" in two projects for sure (maybe more). Never experienced it giving a weird results. It can give FPS drop if it's triggered very often as any other collision condition, but always worked well for me or at least I haven't noticed the wrong output.

Anyway I will keep that in mind next time I'll be implementing this condition. Thanks.

I have now that strange case with overlap and inverted condition, I thought it was my problem but it seems that other people also happens.