1: Getting Started
2: Building Logic
5: Game Mechanics
6: Advanced Topics
7: Testing & Tuning
8: The Last 10%
M1: Mobile - Intro
M2: Mobile - Basics
M3: Mobile - Services
M4: Mobile - Publishing
B: How-To Guides
3.0 Drafts (In Progress)
Continuous Collision Detection (CCD)
What is Continuous Collision Detection?
The physics engine in Stencyl (Box2D) handles collisions between objects, which prevents your characters from walking through walls.
In some cases, however, fast-moving actors, such as bullets or falling objects, can pass right through a wall or floor. That's where CCD comes in.
In the physics engine, collisions are detected every frame at the point where the object moves to. If the object moves into another object or a tile (as illustrated by the purple area in the image), then the physics engine pushes it back to where the collision happened initially.
You never actually see what happens in the middle image, but that is what is happening behind the scenes. On the other hand, if you have a ball that is moving really quickly towards a platform, then it's possible that the two objects never actually intersect and the engine doesn't detect the collision. When this happens, the ball will pass right through. This is called tunnelling.
The way physics engines generally solve this problem is to allow for what is called Continuous Collision Detection (CCD).
What this means is that when an object moves during a frame, it actually checks all the positions between where it started and where it ended up. If the engine detects any objects in this path, then the engine detects a collision. This is shown in the next image, where the purple area is the object's path.
As you might imagine, checking that entire area is more processor intensive than checking a single spot every frame. This is why Continuous Collision detection is off by default, and should only be turned on if needed. Leaving it on if you really don't need it, especially with large numbers of objects, will slow your game down.
How do I turn it on?
1) Use the Actor Physics Setting
Located under the Physics > Advanced page for an Actor.
2) Use the Block
The block's located under Actor > Properties > Misc
When should I use it?
This is a bit trickier. As mentioned above, enabling Continuous Collision Detection can strain on your processor (particularly on mobile), so you should use it sparingly. You should only enable it on fast-moving objects, such as bullets or things that are falling.
If you see objects passing right through walls or floors, and you checked that their collision shapes are in order, then this is something to try.
You can test whether enabling continuous collision detection is necessary by first slowing down your object and seeing whether it collides as you'd expect. If it collides with walls when moving slowly, but not when moving quickly, then you need to enable it.
Tips and Tricks
Preventing a Framerate Drop
When you have a large number of Actors on screen that are constantly colliding with one another, or with tiles, your came could experience a framerate drop. The way to resolve this issue is to turn off Continuous Collisions for each Actor Type (on their respective Physics pages) and to add a code block with the code shown below to any movement Behaviors your Actor Types are using.
box2D.dynamics.B2World.m_continuousPhysics = false;
Challenge: Replicate the "tunneling" problem
Want to test your complete understanding of CCD?
Create a game that replicates a scenario that requires CCD to solve. Think about the conditions required for "tunneling" to happen.
Last Updated: 2013-01-29 by Jon
16569 have read this article
Disclaimer: The Stencyl Team does not actively monitor comments on articles. If you're seeking help for your game, please ask a question on the forums. Thanks!