What are the necessary settings to prevent objects passing through each other at high speeds?

I looked into this problem about a year ago, didn't find an ideal solution then, i did find a sort of hack involving raycasting and prediction that filled the gap for now, but it's hardly optimal.

I'm sure unity has had some updates, i think it's worth another try;

Assuming i have a wall, made of non-kinematic physical objects with rigidbodies (Or possibly it is a static wall without a rigidbody, different use cases) and that the other object is a flying physical projectile with a non-kinematic rigidbody;

What settings can i use to ensure that these objects always collide, and thatno matter how thin the wall is, or how fast the projectile is moving, one never goes through the other without registering a collision?

This seems like a feature any good physics engine should have, i'm saure PhysX must have support for it.

 

Change collision detection mode on the Rigidbody(s) from discrete to continuous. More overhead, but better collision detection.

 

thank you, this seems to work now. i'm pretty sure it didn't when i last tested

 

If it's two Dynamic Colliders, you have to set one of the object's Rigidbody Collision Detection to Continuous, and the other object's Rigidbody Collision Detection to Continuous Continuous Dynamic.
If it's one Static Collider and one Dynamic Collider, set the object's Rigidbody Collision Detection to Continuous.

PS: Static Collider means a GameObject without a Rigidbody. Dynamic Collider means a GameObject with a Rigidbody.

It's worth noting that Continuous and Continuous Dynamic collision detection modes have an impact on the Physics performance.

Hope this helps.

 

Wooah! This was informative.

 

I know this is an old thread, but I had this problem and it drove me insane. So here is what solved it for me: If a collider has the isTrigger boolean as true, it will not interact with other collider's physics. In other words, if a collider is a trigger, it will raise whatever flag is required for the OnTriggerEnter function, but will not "push" the other collider away and it will not be pushed back.

TL;DR: Set your collider parameter isTrigger to false or add another collider component that is not a trigger
Finish the tutorials, kids. They're that long for a reason.

 

How would this apply to detecting collisions on a part of an animation? I have a similar problem as OP does, but instead of a high-speed physics projectile, it's a fast moving sword. In one frame of the swing, the sword has not yet collided with the other sword, but in the next frame, it is already past the sword. Though there are continuous kinematic rigidbody trigger colliders on both swords, I imagine this does very little if the movement of the swords is through an animation instead of the physics engine.

I have more details here: https://forum.unity.com/threads/parryable-attack-animation.590581/

 

That is true, at this point you will want to use a Raycasting system that extends out of your sword, Since update goes once per frame you could always add the sword swing raycast into a Coroutine and have it occur as often as you'd like.

 

If you want physics to apply to your sword, I recommend having your sword as a separate physics game object. You can then use rgidbody.moveposition and rigidbody.moverotation to interpolate it to your animation source.

My swords detect each other, but still, have a problem of "popping through" each other.

 

..........
Thank you for this help

 

I know this post is old but it't help me a lot

 

Thank U so MUCH it helped me alot

 

its not working in my case

 

Are you using mesh collider for your dynamic body.
If so CCD will not work anyway.
It is super important truth that is somehow not exposed enough.

 

In Unity 2020 go to Edit -> Project Settings -> Physics to make essential tweaks to Physics settings.

For me, what worked was to change the Default Max Depenetration Velocity. This is like the force that the collider pushes back against the item colliding into it. My issue was that I used a Rigid Body vs a Static Collider (Capsule). Because the Default Max Depenetration Velocity was set to just 10, my high-speed object was passing through the collider. I changed to 1000 and the collider became much more aggressive towards the invader . All good now.

 

Thank you, this did it for me!

 

Fantastic thank you, I've been trying everything to get this to work and was not aware of this setting This has resolve my issue perfectly.

 

Thank you so much

 

Thank you!

 

I have tried all of the above approaches, and I'm still having the same issue.
I am making one of those children's toys, where it's a box with a glass top, and a ball inside, and you tilt the box to navigate a maze inside with a ball. It works great, the problem is that if the ball is at one end with the box tilted, and you quickly switch to tilting in the opposite direction, the floor changes from roughly 30 degrees positive, to 30 degrees negative. At the far ends of the box, this is a drastic change in location, so all of a sudden the ball is underneath the floor, and falls forever.
Again, I've tried all of the above steps.
Changing max depenetration velocity to 1000, or even 1000000 did nothing.
Changing the collision detection modes of the ball, and the floor, all did nothing (I've tried many combinations now).
I have tried adjusting the rotation of the board object directly, and I have also made the empty containing all the board objects a rigidbody, and changed it's rotation by ridigbody.moverotation. Neither worked (although the second is causing additional problems now).
I have also tried making the box collider of the bottom massive downwards, but all the ball has to do is pass through the top, so the same problem happens, and it just keeps falling.

All I want is for the ball to NEVER be able to pass through these objects like the floor and walls.
Any help would be greatly appreciated!

 

Hi, Have you tried to put your function (controlling box tilting) into FixedUpdate() with Time.fixedDeltaTime? I seem to have similar issue as yours and FixedUpdate solved my issue. I am making a toy grabbing machine, where a mechanic claw is attached to a chain of rings. The rings are made of compound colliders and they always break through each other when I swing the chain around. As soon as I put my ring movement control function into Fixedupdate(), all issues are gone. I can have crazy swing speed with drastic change of direction, no need to change discrete collision detection to continuous. The move function was in Update() before and it runs like 200 per second. Physic collision works around 50 per second by default (you can change that in edit - project setting - time - fixed time step). I believe your ball falls through the floor because physic calculation is way behind how fast the function is called. Hope this helped your problem!

 

I think sometimes there is just no other way other than to decrease fixedTimeStep. I personally set it to 0.005 for my game and it doesn't cause any performance issues at all. Also to avoid objects passing through each other i believe you should avoid using movePosition or moveRotation because it isn't adding any force or velocity to the object just teleporting it to position instead. And ofc all the physics operations should be moved to FixedUpdate and forces of mode Impulse/VelocityChange or direct modifications to velocity should be multiplied by Time.deltaTime if you apply them continuosly and want them to scale with fixedTimeStep

 

Thanks A lot It Work A lot

 

Anyone who still has this problem... for me it was fixed with changing Edit -> Project Settings -> Time - fixedTimeStep to 0.01333 (75fps).

 

Thanks Worked for me