What Is a Collider in Unity? Box, Circle, and Capsule Colliders
A Collider is the shape that represents a GameObject in physics. Box, Circle, and Capsule have different costs and shapes; a simple matching primitive is often better than an overly detailed mesh collider. The exercise uses a Capsule character, a Box floor, and Circle/Capsule objects, then tunes size and center in the Inspector. A gameplay Collider need not exactly match the rendered mesh.
ASCENO / UNITY STUDY NOTES · 35
What Is a Collider in Unity? Box, Circle, and Capsule Colliders
Collider trong Unity là gì? Box, Circle, Capsule Collider
The lesson starts with a direct Unity screenshot so the practical action is visible. The nine following figures are language-neutral illustrations; the bilingual text below them carries the explanation. The main topic is collider unity. Figure 1 is practical evidence; figures 2–10 use only shapes, symbols, and visual relationships so they can remain unchanged across languages.
Learning goals
- Explain the concept with a model or data flow.
- Know exactly which Unity window to open.
- Predict the result before pressing Play and find evidence.
- Rebuild a small experiment and debug it methodically.
1. Hands-on practice in Unity
Open the test Scene, select the relevant object, and perform the action described in the lesson. This is a native Unity screenshot that shows where to begin; the steps and meaning are explained in the text below.
2. System illustration
A Collider is the shape that represents a GameObject in physics. Box, Circle, and Capsule have different costs and shapes; a simple matching primitive is often better than an overly detailed mesh collider. The illustration below contains no language-specific text; read it together with this explanation and the concrete steps.
- collider unity | the lesson concept | read the focus and hands-on example | do not infer it from object colours
- Input/setting | the input data or configuration | record the value before changing it | do not change several things at once
- Result/evidence | what must be observed in the Scene, Game, Inspector, or Console | capture the correct panel | a polished image is not evidence
3. Cause → result illustration
Read the arrow direction, relative position, and symbol changes as a causal relationship. The explanation below names each step in text rather than relying on words inside the image.
- Define the question
- Build a small test Scene
- Change one value or reference
- Press Play / run the action
- Read the correct panel
- Compare with the prediction
4. Sequence illustration
Open Unity, select Player/Ground, inspect the matching Rigidbody–Collider pair, then enter Play Mode to observe a collision or trigger.
5. Object structure illustration
Read the object name in the Hierarchy first. If the name does not communicate its role, rename it in the test Scene; a screenshot is useful only when the reader knows what is selected.
6. Configuration illustration
Select the object representing collider unity in the Hierarchy. Read Transform first, then find the relevant Component/field. Record the current value before changing it; Cover the gameplay-relevant area instead of matching every tiny model detail
7. Result observation illustration
The Console is not decoration: use it to verify Use MeshCollider carefully and understand the convex requirement with Rigidbody. If no log appears, check the active object, script compilation, and Console filters before adding more code.
8. Code → state illustration
Do not copy code away from the Scene. Before each line, identify the input object/reference; after each line, identify the state or output that should change.
using UnityEngine;
public class ColliderProbe : MonoBehaviour
{
private void OnCollisionEnter(Collision collision)
{
ContactPoint contact = collision.GetContact(0);
Debug.Log($"Hit {collision.gameObject.name} at {contact.point}");
}
}
9. Experiment illustration
The exercise uses a Capsule character, a Box floor, and Circle/Capsule objects, then tunes size and center in the Inspector. A gameplay Collider need not exactly match the rendered mesh.
- Cover the gameplay-relevant area instead of matching every tiny model detail.
- Use child Colliders when a Prefab needs several distinct hit areas.
- Use MeshCollider carefully and understand the convex requirement with Rigidbody.
- Run again after reverting to check that the result is reproducible.
- Record the input value, action, result, and reason for the change.
10. Failure → fix illustration
- Selecting the wrong object or asset means a correct edit appears to do nothing.
- Changing several fields at once hides the cause.
- Looking only at the Scene while ignoring the Inspector/Console.
- Skipping verification specific to collider unity.
The ASCENO perspective: A good figure must help the reader answer one concrete question. If it does not show what to select, where to look, what to change, or where the result appears, it is not ready for documentation.