OnCollisionEnter2D and OnTriggerEnter2D in Unity - Performance & Optimization

Performance: OnCollisionEnter2D and OnTriggerEnter2D

MEDIUM IMPACT

This affects the physics simulation and event handling performance during gameplay, impacting frame rate and input responsiveness.

Detecting when two objects touch in a 2D game

Unity

void OnTriggerEnter2D(Collider2D other) {
    // Simple trigger used for overlap detection
    Debug.Log("Trigger entered by " + other.gameObject.name);
}

OnTriggerEnter2D only detects overlaps without full physics collision response, reducing CPU work.

📈 Performance GainAvoids physics collision resolution, lowering CPU usage and improving input responsiveness.

Detecting when two objects touch in a 2D game

Unity

void OnCollisionEnter2D(Collision2D collision) {
    // Heavy physics collision used just to detect overlap
    Debug.Log("Collision detected with " + collision.gameObject.name);
}

Using OnCollisionEnter2D triggers full physics collision calculations and response, which is costly if only overlap detection is needed.

📉 Performance CostTriggers physics collision resolution and multiple reflows per collision event, increasing CPU load and reducing frame rate.

Performance Comparison

Pattern	Physics Cost	CPU Usage	Frame Impact	Verdict
OnCollisionEnter2D for overlap detection	High (full collision resolution)	High	Can cause frame drops	[X] Bad
OnTriggerEnter2D for overlap detection	Low (simple overlap check)	Low	Smooth frame rate	[OK] Good

Rendering Pipeline

Physics events like OnCollisionEnter2D and OnTriggerEnter2D are processed during the physics update step before rendering. Heavy collision calculations can delay frame updates and input handling.

→Physics Simulation

→Script Execution

→Rendering

⚠️ BottleneckPhysics Simulation stage is most expensive due to collision detection and resolution calculations.

Core Web Vital Affected

INP

This affects the physics simulation and event handling performance during gameplay, impacting frame rate and input responsiveness.

Optimization Tips

1Use OnTriggerEnter2D for overlap detection without physical collision response.

2Avoid OnCollisionEnter2D unless you need physics collision effects.

3Keep colliders simple and limit physics checks to necessary objects.

Performance Quiz - 3 Questions

Which method is more efficient for detecting simple overlaps without physical collision response?

A OnTriggerEnter2D

B OnCollisionEnter2D

C Update() with manual distance checks

D FixedUpdate() with raycasts

DevTools: Unity Profiler

How to check: Open Unity Profiler, run the game, and look at the Physics and Scripts sections to see CPU time spent on collision events.

What to look for: High CPU usage spikes in Physics or Scripts during collision events indicate costly OnCollisionEnter2D usage.