Depends on the platform. I'm not sure about Worms, but in most artillery games, you can do simple pixel color check. I did this for a Scorched Earth clone.

You can even have a screen size buffer, so that your collision check becomes simply this:

[font=courier new,courier,monospace]if( ScrnBuffer[x][y] != EMPTY )[/font]
[font=courier new,courier,monospace]{[/font]
[font=courier new,courier,monospace] Explosion!!![/font]
[font=courier new,courier,monospace]}[/font]

Maybe this can be another texture, and you draw to it in a different pass than the actual rendering. then you can lok up the pixel/texel's color.


Please give some more details about the platform, graphics API, etc so that we can give you better ideas.

Look into a 2d physics engine. I use chipmunk-physics, but others use box2d. Google 'em

Look into a 2d physics engine. I use chipmunk-physics, but others use box2d. Google 'em

They don't have any collision routines for a pixel map.

You can even have a screen size buffer, so that your collision check becomes simply this:

if( ScrnBuffer[x][y] != EMPTY )
{
Explosion!!!
}
...

The direct sampling approach is also no good because of tunneling. Projectiles will be on one side of a thin barrier on one frame, and the other on the next.

What you need is to cast a line into the grid, from the previous position of the projectile to its calculated next position. The point of collision is the first pixel that it hits along (the one with the smallest T value). Bresenhams line is one way to do this. Test each pixel that the line passes through until you get a hit.

http://en.wikipedia.org/wiki/Bresenham's_line_algorithm

When an explosion occurs, you can remove pixels from your pixel sized grid to damage the level. For characters walking, a ray cast downward will suffice. Let them fall through gaps of 1px (these will be rare though, if you are blowing holes in the terrain with explosions). You can do a brute force iteration over a square area that covers your circle, doing a distance-from-centre test to ensure you don't fill out the corners. Performance here is acceptable, don't try to optimise that yet.

The last thing you need to remember is to use a grid of smaller textures, don't try to do it with a single huge texture, because you have to modify textures when they get holes blown in them. Textures that stayed intact can be left unmodified. For a basic implementation, this is the only optimisation you really need.

[quote name='BeerNutts' timestamp='1340593256' post='4952527']
Look into a 2d physics engine. I use chipmunk-physics, but others use box2d. Google 'em

They don't have any collision routines for a pixel map.

You can even have a screen size buffer, so that your collision check becomes simply this:

if( ScrnBuffer[x][y] != EMPTY )
{
Explosion!!!
}
...

The direct sampling approach is also no good because of tunneling. Projectiles will be on one side of a thin barrier on one frame, and the other on the next.

What you need is to cast a line into the grid, from the previous position of the projectile to its calculated next position. The point of collision is the first pixel that it hits along (the one with the smallest T value). Bresenhams line is one way to do this. Test each pixel that the line passes through until you get a hit.

http://en.wikipedia...._line_algorithm

When an explosion occurs, you can remove pixels from your pixel sized grid to damage the level. For characters walking, a ray cast downward will suffice. Let them fall through gaps of 1px (these will be rare though, if you are blowing holes in the terrain with explosions). You can do a brute force iteration over a square area that covers your circle, doing a distance-from-centre test to ensure you don't fill out the corners. Performance here is acceptable, don't try to optimise that yet.

The last thing you need to remember is to use a grid of smaller textures, don't try to do it with a single huge texture, because you have to modify textures when they get holes blown in them. Textures that stayed intact can be left unmodified. For a basic implementation, this is the only optimisation you really need.
[/quote]

That's correct, but you can generate the lines under the map to match almost perfectly. And, what you'll gain from the physics library is immense time and brain saving.

The implementation you suggest has many difficulties, whereas the physics engine will handle everything movable for you (walking, shooting, colliding, etc.). The main difficulty with a physics engine is handling creating the craters from explosions. But, I'd say even that can be modified via small line-segments. That's how I'd do it at least.

[quote name='speciesUnknown' timestamp='1340625854' post='4952624']
[quote name='BeerNutts' timestamp='1340593256' post='4952527']
Look into a 2d physics engine. I use chipmunk-physics, but others use box2d. Google 'em

They don't have any collision routines for a pixel map.

You can even have a screen size buffer, so that your collision check becomes simply this:

if( ScrnBuffer[x][y] != EMPTY )
{
Explosion!!!
}
...

The direct sampling approach is also no good because of tunneling. Projectiles will be on one side of a thin barrier on one frame, and the other on the next.

What you need is to cast a line into the grid, from the previous position of the projectile to its calculated next position. The point of collision is the first pixel that it hits along (the one with the smallest T value). Bresenhams line is one way to do this. Test each pixel that the line passes through until you get a hit.

http://en.wikipedia...._line_algorithm

When an explosion occurs, you can remove pixels from your pixel sized grid to damage the level. For characters walking, a ray cast downward will suffice. Let them fall through gaps of 1px (these will be rare though, if you are blowing holes in the terrain with explosions). You can do a brute force iteration over a square area that covers your circle, doing a distance-from-centre test to ensure you don't fill out the corners. Performance here is acceptable, don't try to optimise that yet.

The last thing you need to remember is to use a grid of smaller textures, don't try to do it with a single huge texture, because you have to modify textures when they get holes blown in them. Textures that stayed intact can be left unmodified. For a basic implementation, this is the only optimisation you really need.
[/quote]

That's correct, but you can generate the lines under the map to match almost perfectly. And, what you'll gain from the physics library is immense time and brain saving.

The implementation you suggest has many difficulties, whereas the physics engine will handle everything movable for you (walking, shooting, colliding, etc.). The main difficulty with a physics engine is handling creating the craters from explosions. But, I'd say even that can be modified via small line-segments. That's how I'd do it at least.
[/quote]

Physics engines are designed to do one thing well - rigid bodies. If you don't have rigid bodies, attempting to force them to use a different paradigm is not worth the time they will save you. Box2d does not have built in character controllers, and even if it did they would be for use in a rigid body simulation. There is a fine line between sensible code resuse and trying to force a tool to do something it cannot do.

You will spend more time on your line segment hack, and making that support terrain destruction via explosions, than you will save by using the physics engine. You will still have to implement you character controller manually, and you will still need to write the projectile system yourself, to use line segment queries (if you use rigid bodies to simulate projectiles, they will tunnel)

Direct sampling is okay if you have small steps. Of course you can have more sophisticated algorithms, but I was just showing the basic idea.

A bit of context may be useful from the OP. Since small steps could be sufficient enough but could not.

I believe there are techniques where you cast a line that has a thickness equal to the frontal area of the projectile, I've not tried raycasting at all before so couldn't tell you how its done.

http://www.emanueleferonato.com/2012/05/24/the-guide-to-implementing-2d-platformers/

scroll down to the bitmask section