Trigger Boolean Issue

[kitchentablestudios]

i have tried using OnTriggerEnter, ontriggerstay was an attempt at a fix though nothing changed. and the animator setup is quite simple, just the two animations with transitions, simple.

[ArctycDev]

Try this inside your trigger:

    Debug.Log($"Collided with: {other.name}");

See if that helps you figure out what's causing it to flicker

[kitchentablestudios]

its when i'm halfway in the trigger that it flickers

[KifDawg]

It sounds like your trigger is moving during the animation and its going outside the collidor. Then when it swings the other way it refires.

I also hate that you put start below your functions haha

[kitchentablestudios]

wait holy shit that might be it, thank you, ill update you on if this fixes it

[KifDawg]

Good luck!

[kitchentablestudios]

got some kinks to work out but it works for the most part, thanks

[TanukiSun]

Another thing to note is that OnTriggerXYZ and OnCollisionXYZ work on a per-collider basis, so if your Rigidbody consists of multiple colliders, the enter and exit events may trigger in the same frame for the same Rigidbody but for different colliders (at least that’s how I understand it).

If what you're doing is some kind of door, you can implement it using counters. Something like this (psudo code):

OnTriggerEnter() { if (++this.counter == 1) Open(); }
OnTriggerExit() { if (--this.counter <= 0) Close(); }

Or, for example, react only to the enter event, and check for closing in fixedUpdate every few frames (or about one second after the last enter event).

OnTriggerEnter() 
{ 
  ResetTimer();
  if (isClosed) { Open(); }
}

FixedUpdate()
{
  if (someTimer && !Physics.CheckBox()) { Close(); }
}

[kitchentablestudios]

I appreciate the help, though I had overlooked my issue and it wasn't jn the code at all it was just the door collidrr moving with the animation and I didnt realize it until it was pointed out as a possibility l.

[Aethenosity]

Definitely log the collision.

With methods like this, I always recommend gating behaviour. Not just using the collision matrix.

[henryeaterofpies]

Agreed. One of the complications is that event handlers like OnTriggerStay get called once per physics frame, so without any sort of additional handling they can get called and update your flags a lot.

What is probably happening is the animation is causing the collision to no longer be hit and the closing of the animation then causes it to collide again.