OnTriggerEnter Not Fired?

I have to wait for the 2020.1 version to test it. Hopefully you are able to push it soon

 

It works fine on my two simple tests.

 

Looks good for me.

 

Great! Excited to see this in!

 

@yant is Unity 2019.3.0b8 Early Feedback the same as official beta 8?

 

nope

 

any progress on the 2020.1 build?

 

Does official beta 8 have your fix built in?

 

Thanks. I'm desperate to test this on 2020! It's been a nightmare to adjust triggers and I keep finding more and more werid cases.

 

Hey, I just wanted to know if this solution (changing internals of physX) will be healthy in the future. I mean someone from PhysX team said the removed trigger code path allowed them to refractor stuff. Will it not be problematic for keeping up with new versions?

What will happen when a refractor or new feature comes, that is incompatible with the old code you've added again?

 

What approach do you think would cause the least issues long term?

 

Thank you for the honest and detailed response. I, too, think that (3) is the right way going forward, and also think that is perfectly reasonable to revert the internal changes in order to alleviate immediate user pain. It was not my intention to imply otherwise.

I was not aware that Unity deviated from stock physX, as I haven't used it I kinda assumed it was a straightforward wrapper.

 

Thank you for your hard work. Please push this patch in beta9 next week if anyhow possible.

 

@UT

Can you, PLEASE, add this warming or note to the documentation of the trigger related events?

There is nothing. The communication of UT with his community is lousy. It's not the first time I discovered something by the fourm that should be announced elsewhere. Just like the problems with Unity and High Sierra (related to APS) and now with Catalina (related to Android NDK). USE THE BLOG FOR SOMETHING USEFUL AND INFORM!

 

This is beta. It's not meant for any kind of production. Docs is for official release.

 

Thank you for the notice. Now I can adjust the schedule.

 

any idea for which 2020.1 version will it be?

 

From Unity 2020.1.0a12.

 

ouch

 

@yant a little bit off topic, but does collision resolution somehow depends on frame rate? I am using Physics Scene and manually calling Simulate. And I've noticed that if I call Simulate like 20 times a frame (my implementation of time warp) all collisions become unstable and give unpredictable results (huge forces and velocities as result). While using it with normal rates (2-3 per frame) everything works as expected. I am applying all forces before calling physicsScene,Simulate() and calling it with fixed timeStamp (0.02). I can't find anything that can cause such results. So the second question: are there anything I should pay attention when implementing "time warp" with the Physics scene?

 

Nevermind, I found the issue. Due to precision error sometimes very small number (like 1e-09) was passed to physicsScene.Simulate(); instead the fixed timestamp, which caused these problems.

 

Same issue in Unity 2019.2.11f1

 

Hey there, oh sorry my mistake then.. I thought this thread was about a bug issue.
I have some weird issues with OnTrigger events. I have a script and a sphere collider (with IsTrigger checked) attached onto the game object, but when other game objects with colliders attached on them enter the sphere collider the OnTriggerEnter method is not fired.

I never had this type of problem before, so not sure what's the issue. I looked up and down and can't figure it out what could be causing this, so thought maybe this was a bug.

 

I have the same issue. How fast is you sphere collider with trigger moving? I checked Continous detection but the weird part sometimes trigger gets released, sometimes not.

 

The object with Sphere collider is a turret, so it does not move, only the objects that enter the Sphere collider (enemies), so Sphere collider is like a sensor for the turret, but some enemies move really slow and I tried to move the object manually into the trigger, just doesn't detect anything
My enemy objects are without rigidbody component as I'm making a game for mobile, would really slow down the frame rate I think, a lot of rigidbodies, although I tried with rigidbody as well, just to check, it didn't work either. :/

 

kinematic rigidbody + static triggers should work (as long as you move the objects through rigidbody, not transform)

otherwise if you don't have many spheres you can do sphere casts instead of triggers

(or use DOTS physics)

 

Any moving collider should have a Rigidbody, otherwise it will be treated as a static collider (and two static colliders doesn't send trigger messages). Attach a Rigidbody and mark as kinematic.

Also, please keep that thread focused on the main topic, create a separated thread if you need further help on that. We are in the 2019.3 Beta threads, any issues with previous versions doesn't belong here.

 

Hi @yant, just writing in to say the trigger-to-trigger detection behaviour is indeed back to normal with 2019.3b10. Thanks for realizing the importance if this and reacting so quickly!

 

Is it expected GameObjects without trigger colliders should call the OnTriggerEnter method in that object.?
This is happening.

Regards,

 

I've been told that OnTriggerEnter in scripts on nonTrigger objects have been catching messages for a considerable period of time.
Is this the designed behaviour ?
If so, the documentation should be revised.

The docs https://docs.unity3d.com/2019.3/Documentation/Manual/CollidersOverview.html
quote :

>> The scripting system can detect when collisions occur and initiate actions using the OnCollisionEnter function. However, you can also use the physics engine simply to detect when one collider enters the space of another without creating a collision. A collider configured as a Trigger (using the Is Trigger property) does not behave as a solid object and will simply allow other colliders to pass through. When a collider enters its space, a trigger will call the OnTriggerEnter function on the trigger object’s scripts.

Regards,