So is OnCollisionEnter/OnTriggerEnter

[upper kraken]

My MeshCollider looks like this. (I'm using it on '3D text')

It seems somewhat complex(?), but it's not super small or anything relative to the other collider (or in general), so kinda surprised it doesn't work, not even sometimes.

[open dagger]

1. Non convex mesh colliders are not supposed to be moved iirc.
2. Convex mesh colliders could be as precise as any primitive collider.
3. It's likely that you're doing something illegal, like moving or rotating the object via transform, which would cause issues for unity physics to detect collisions correctly.

[upper kraken]

Only the convex one is moving. The other is "catching"them.

And I was moving it via Transform to test, can't remember if I did without (runtime will be AddForce), let me chck

[open dagger]

Rotation also matters. Not just movement.

[upper kraken]

Even with AddForce (not transform) moving them, the MeshColliders don't register an OnColliderEnter (but the Boxes still do).

Also quite confused why the instantiated objects tend to go backwards, and only sometimes forwards, despite calling rb.AddForce(instantiatedObj.transform.forward * shootForce) 🤨 . In theory wouldn't it go the same direction every time? The spawn point isn't rotating or anything.

[open dagger]

Is the mesh collider paper thin?

As for why they're going back, you'll need to debug that.

[upper kraken]

Neither is paper thin. Yeah it's all a bit confusing right now

[open dagger]

You should share some code. And setup screenshots.

[upper kraken]

Increasing the force multiplier seemed to fix that issue for now. I guess I'll just use box colliders.

The MeshCollider is created in script

[open dagger]

You can pause the game, select the object and inspect it in the inspector.

[upper kraken]

This is the moving object in MeshCollider configuration and the 'Catcher' respectively