2019.3 b4 OnTriggerEnter not firing?

[SynapticBytes]

Hi folks,

I’m new to Unity and working through the game dev course from GameDevHQ which came with the Humble bundle. It uses the OnTriggerEnter event to test player/enemy/bullet collision. I have installed 2019.2 and 2019.3b4 and have been using the beta build to learn so I start learning with the newer features.

It appears though this beta is not firing the OnTriggerEnter event (and maybe the other trigger events too). I made a new project in both 2019.2 and 2019.3, positioned a sphere above a cube both with triggers, the sphere with a RigidBody, and the sphere with gravity. It drops onto the cube. In 2019.2, it logs entering the OnTriggerEnter event, but in 2019.3b4, nothing is logged.

Is there some change I have to make int eh new version, to activate triggers, or doe sit look like something is broken?

Thanks.

[Peter77]

This came question came up earlier:

OnTriggerEnter Not Fired?

When update unity version, our project seems having this issue. Two triggers can't fire an ontrigger event when colliding. I'm pretty sure every settings are correct. Both of them have their rigidbody and it just works fine in old version. When I try make one of the trigger to collider, the event fired. Just two triggers won't call the OntriggerEnter.[4803170--459431--1.png] [4803170--459434--2.png]

Unity staff replied with:

@Unity staff

This is probably the most visible regression in PhysX 4.1 that we knew about for a while. It’s by design, as the team wanted to clean up some trigger code that was otherwise imperfect

OnTriggerEnter Not Fired?

This is probably the most visible regression in PhysX 4.1 that we knew about for a while. It’s by design, as the team wanted to clean up some trigger code that was otherwise imperfect. I guess it is great now J. Nvidia recommends to duplicate trigger colliders. I’m closely watching this space, and if it turns to be a seriously painful topic, we can still roll out an optional workaround that would return the old behaviour back, at some extra cost.

After many “but we need this” replies, Unity staff wrote:

@Unity staff

I see now how important it is, will be coming with a proposition of a solution in the following weeks.

OnTriggerEnter Not Fired?

I see now how important it is, will be coming with a proposition of a solution in the following weeks. Thanks for your patience and care for the physics.

PhysX 4.1 in Unity - experimental builds page-4#post-5007686

I recommend not use to an alpha and beta version of Unity to learn, as these are expected to contain broken functionality. Use the Unity version the tutorial is made for instead and you’ll dodge quite some frustration.

[SynapticBytes]

Thank you for the detailed reply and pointer to the other thread, which I have now read. I did try searching before posting but my GoogleFu failed me. I’ll keep an eye on what the upcoming solution proposes, as trigger-trigger collisions was something I used often years ago when I was doing Shiva development, so losing the functionality does seem a bit of a blow.

This is bad timing given the Humble Bundle, as others going down the same path as me will also hit this roadblock If they like to live on the bleeding edge. I understand the logic of your suggestion of using stable releases for learning. I did consider my options before starting as to which version to use, but looking at the roadmap and the history of changes in Unity, I didn’t want to spend time committing old ways of doing things to muscle memory, and then have to change once I become proficient. Still, with Unity Hub making it easy to swap between versions, I guess it’s not a big hurdle. Unfortunately downgrading a version doesn’t look as easy as upgrading, so I guess I have some re-cosing to do for now.

Thanks again.