Sorry your browser is not supported!

Searching around the forums I saw that over the years many people have had issues with DBP's sprite collision system.

I was wondering if anyone happens to have a bounding box collision algorithm that works a bit more often than the one used by DBP?

The code below only seems to work 1 in a few hundred times, which is unacceptable for a bullet hell game.



Originally I was going to use sprite collision(), but after that didn't seem to work well, I switched to sprite hit(). After reading up on the differences between the two and looking for an algorithm on the forums for better sprite collision, I decided that I don't need pixel perfect collision, bounding box will do. It is a bullet hell game, there is going to be so much going on they probably won't notice that I am using bounding boxes.

EDIT:
For those who may wonder, 2000 to 2250 is the valid range of sprite numbers for the enemies and 1000 to 1250 is the valid range of sprite numbers for the missiles.

One thing to take into account is that with SPRITE HIT and SPRITE COLLISION, when you use the parameter of '0' it returns the lowest unique sprite identifier being hit. So, if the sprite in question is touching 10 other sprites, the SPRITE HIT and SPRITE COLLISION commands will only return the LOWEST numbered sprite that is being hit, and ignore any others.

@Amd Silver

Assuming sprite one's corners are
x1,y1..............x2,y1
x1,y2..............x2,y2

and sprite two's corners are
x3,y3..............x4,y3
x3,y4..............x4,y4

Then