Mesh collidersAn invisible shape that is used to handle physical collisions for an object. A collider doesn’t need to be exactly the same shape as the object’s mesh - a rough approximation is often more efficient and indistinguishable in gameplay. More info
See in Glossary require a GameObjectThe fundamental object in Unity scenes, which can represent characters, props, scenery, cameras, waypoints, and more. A GameObject’s functionality is defined by the Components attached to it. More info
See in Glossary’s MeshThe main graphics primitive of Unity. Meshes make up a large part of your 3D worlds. Unity supports triangulated or Quadrangulated polygon meshes. Nurbs, Nurms, Subdiv surfaces must be converted to polygons. More info
See in Glossary to be properly configured so that collisionsA collision occurs when the physics engine detects that the colliders of two GameObjects make contact or overlap, when at least one has a Rigidbody component and is in motion. More info
See in Glossary are accurate.
There are particular configurations and optimizations that require a Mesh to be read/write enabled. For details on what “read/write” means in this context, refer to documentation on the Mesh API property Mesh.isReadable
.
A Mesh must be read/write enabled if any of the following circumstances are true:
To make a Mesh read/write enabled, the Mesh must have a Mesh.isReadable
value of true
. To apply this via the Editor:
Assets
folder (Project tab) More infoTo calculate collisions with a Mesh collider, the physics system needs to be able to access the Mesh’s geometry. “Mesh cooking” refers to the process of converting a 3D mesh from its original format (for example, FBX or OBJ) into a format that the physics system can read. The cooking process takes the raw Mesh data and builds spatial search structures so that Unity can respond to physics queries more quickly.
You can trigger Mesh cooking in the Import Settings (Import Settings > Model > Generate Colliders) or at run time.
During the Mesh cooking process, Unity can apply various optimizations to reduce the size and complexity of the Mesh (for example: removing redundant vertices, merging overlapping triangles, or simplifying the geometry to reduce the number of triangles). Unity can then load the optimized mesh more quickly and efficiently, which reduces memory use and improves overall performance.
To control which optimizations run, use the Mesh collider’s Cooking Options property (which corresponds to the C# enum MeshColliderCookingOptions
). For an overview of the different cooking options available, see the Mesh collider component reference.
The default Cooking Options are suitable for any Mesh collider that you cook in the Editor and never re-cook at run time. They are also suitable for most Mesh colliders that you need at run time (particularly large or complicated Meshes that only need to cook once). However, you might need to alter the Cooking Options to make collider generation faster if you need to rapidly generate collision geometry at run time (for example, procedural surfaces, or Mesh colliders that deform in response to player behaviour).
To optimize Mesh cooking for Meshes that Unity generates at run time, you can disable the data cleaning steps (Enable Mesh Cleaning, and Weld Co-Located Vertices). However, if you disable the data cleaning steps, you must have another way to validate your Mesh data, to ensure you aren’t using data that those algorithms would otherwise clean.
You can also disable Cook For Faster Simulation to save memory usage.
When you change the Cooking Options, you need to apply read/write permission to the Mesh. For guidance on how to do this, see Allow read and write access to a Mesh.
If a Mesh only needs to provide data for physics calculations and not for rendering (for example, for invisible colliders), you don’t need to import the Mesh’s normals. Meshes without normals require less memory and use less disk space.
To disable normals:
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.