Unity 6 Trigger detection totally broken !

In unity 6 we have faced too many problem with physics such as broken ragdolls, character joints configurable joint etc also one very big problem that trigger detection always returning true no matter what !

1 Like

Heya! Could you please elaborate on this issue a bit?

During 2023.2 life cycle trigger reporting was slightly tweaked to properly pair enter/exit/stay events in the same way as collision events do.

Ok the problem happenes randomly "I don't know how or why for now ! " and when it happen the ontriggerstay always returns true detection between objects that donsen't even get closer to each other and won't return false until all the rb's in the scene are disabled and I mean all of them !, the only fix I found now is to restart the editor and once in a while I need to do a complete reimport ! It starts with U6 before I was using 2022.3LTS and it was fine.

I see, could you give a rough description of the scene where this happens intermittently. What is the setup in your scene?

I'll do some tests on my end to try and track this down.

Cheers,
Alex

In my case, OnTriggerStay is continuously called even colliders are far away. It is randomly appeared, and disabling and re-enabling collider solves this issue temporarily.

Unity 6 seems extremely buggy on Physics system. (Tested on Unity 6000.0.3f1)

1 Like

Another problem is when you disable a trigger when you are in the stay state it won't change !


Absolutely !

@MohamedTun @alexrvn
Any news for this issue? It is still broken on Unity 6000.0.5f1.

[quote=“Kichang-Kim”, post:5, topic: 947519]
In my case, OnTriggerStay is continuously called even colliders are far away. It is randomly appeared, and disabling and re-enabling collider solves this issue temporarily.

Unity 6 seems extremely buggy on Physics system. (Tested on Unity 6000.0.3f1)
[/quote]
I successfully created reproducible project and reported it.
https://discussions.unity.com/t/950439

1 Like

Still happen on Unity 6000.0.10f1.

Very random and hard to trigger, I need to restart the editor when the issue happen

1 Like

I can confirm that too ! Unbelievable !!!