Mesh colliders match the shape of a Mesh exactly, for extremely accurate collision simulation.
The Mesh collider builds its collision geometry to match an assigned Mesh, including its shape, position and scale. The benefit of this is that you can make the shape of the collider exactly the same as the shape of the visible Mesh for the GameObject, which creates more precise and realistic collisions.
The precision of a Mesh collider comes with a higher processing overhead than primitive colliders (such as the Sphere, Box, and Capsule colliders). For this reason, it is best practice to only use Mesh colliders for colliders that do not otherwise require a high amount of processing power, or for collisions where primitive colliders or a compound collider would have a greater overhead. A good approach is to use Mesh colliders for static scene geometry, and compound colliders for moving GameObjects.
In most cases, Mesh colliders offer a similar solution to compound colliders: their primary purpose is to provide accurate collisions for items with complex shapes. When considering the benefits and limitations of Mesh colliders, you are usually comparing them to compound colliders.
The main benefits of Mesh colliders are:
However, Mesh colliders also have some significant limitations:
The decision is always unique to your project, so you should test each configuration and use the Physics Profiler to understand the efficiency of your collider setup.
Mesh colliders behave differently based on whether they are marked as concave or convex. By default, PhysX considers Mesh colliders to be concave.
In mathematics, “concave” and “convex” are terms used to describe shapes:
A convex shape only has lines that curve outward (for example, a ball). Any line segment connecting two points on its boundary remains entirely within the shape. A concave shape has at least one “cave” or indentation where the boundary curves inward (for example, a banana). Line segments connecting two points on its boundary might sometimes cross space outside the shape.
Concave colliders have some limitations: Concave Mesh colliders can only be static (that is, they have no physics body) or kinematic (they have a kinematic physics body). See Collider types for more details. Concave Mesh colliders can only collide with convex colliders. If two concave colliders make contact, no collision occurs.
If you have two concave Mesh colliders that need to collide, you can do one of the following, depending on how accurate your collision needs to be:
If you do not need accurate collisions to take place in the concave parts of the shape, mark one of the Mesh colliders as convex in the Inspector (enable Is Convex). This generates a new convex collider shape called a “hull”, which is like the assigned concave Mesh but with any concave lines filled in, to make them convex.
If you need accurate collisions to take place in the concave parts of the shape, use a compound collider made of convex colliders.
The Mesh that you have assigned to the Mesh collider should ideally not change shape at runtime.
Every time the Mesh changes shape, the physics engine needs to recalculate the Mesh collider geometry, which causes a substantial performance overhead. For this reason, you should not modify the geometry of a Mesh that a Mesh collider is using. If a Mesh needs to both collide and change shape at runtime, it is usually better to approximate the Mesh shape with primitive colliders or compound colliders.
衝突メッシュの面は片面です。つまり、ゲームオブジェクトは 1 つの方向から衝突メッシュを通り抜けことができますが、他の方向からは衝突することになります。
For details about the underlying algorithms and data structures that Mesh colliders use, see the Nvidia PhysX documentation on Geometry.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.