Ray casting

Description

The ray casting commands provided in AGK offer the ability to check whether a collision has occurred between two points. This can be useful for a wide variety of situations, such as testing whether a race car crosses a checkpoint, finding out how close a player is to an enemy and much more.

This example places three sprites on screen with two of them being static and the remaining one moving up and down the screen. A ray cast is performed to check when the dynamic sprite moves between the static sprites. When this happens both static sprites have their color changed to red and when no collision occurs their color is reset.

Getting started

As mentioned previously three sprites will be used in this example. The dynamic sprite will use an image named "gold.png", while the static sprites will use an image named "silver.png".


The set up code defines a virtual resolution of 320 x 480, loads the images gold.png and silver.png, followed by the creation of sprite 1 (our dynamic sprite) and sprites 2 and 3 that are the static sprites. Note that a call is made to the command SetSpriteShape for sprite 1, to ensure a circle is used for collision checks. This line plays an important part, as without it no collision checks can be performed.

SetVirtualResolution ( 320, 480 )

CreateSprite ( LoadImage ( "background7.jpg" ) )
LoadImage ( 1, "gold.png" ) LoadImage ( 2, "silver.png" )
CreateSprite ( 1, 1 ) SetSpritePosition ( 1, 150, 0 ) SetSpriteShape ( 1, 1 )
CreateSprite ( 2, 2 ) SetSpritePosition ( 2, 30, 200 )
CreateSprite ( 3, 2 ) SetSpritePosition ( 3, 260, 200 )

Moving the dynamic sprite

Sprite 1 will move up and down the screen continually. These lines of code deal with the movement and are to be used within the main loop:

if ( direction = 0 )
    SetSpriteY ( 1, GetSpriteY ( 1 ) + 1 )

if ( GetSpriteY ( 1 ) > 400 ) direction = 1 endif endif
if ( direction = 1 ) SetSpriteY ( 1, GetSpriteY ( 1 ) - 1 )
if ( GetSpriteY ( 1 ) < 30 ) direction = 0 endif endif

Initially the variable direction is set to 0. When direction is 0 the sprite is moved down the screen by adding 1 to its Y position, a check is then made to see if the sprites Y value is greater than 400 pixels and when this is true the direction variable gets set to 1. When direction is 1 the sprite is moved up the screen by deducting 1 from its Y position, a check is then made to see if the sprites Y value is less than 30 pixels and when this is true the direction variable gets set to 0 and in doing so kicking off the process of moving down. The end result is that this block of code will continually move sprite 1 up and down the screen.

Performing a ray cast

There are two stages to performing a ray cast, the first being the actual ray cast and the second retrieving information from any collisions. The first step is either carried out with the command SpriteRayCast or PhysicsRayCast. The first command is used for ray casting on non physics sprites, while the second command is used to deal with sprites that have physics enabled. Physics enabled sprites are not being used in this example therefore SpriteRayCast will be used. This command takes four parameters: x, y, x2, y2. The first two parameters control the starting location of the ray cast and the second two determine the end location. In this example a ray cast will be performed between the location of the first static sprite (ID 2) on the left and the location of the second static sprite (ID 3) on the right:

if ( SpriteRayCast ( 30, 200, 260, 200 ) = 1 )

endif

The positions for the start and end location of the ray cast are hard coded to match sprites 2 and 3. If this command returns a value of 1 then we know that a collision has occurred between these points and can then act on it. Please note that sprites 2 and 3 are only present to give a visual marker for the ray that is being cast, their presence on screen has no bearing on the collision tests.

When a collision takes place sprites 2 and 3 will have their color set to red, and when there is no collision their colors will be set to white. The above code is amended to:

if ( SpriteRayCast ( 30, 200, 260, 200 ) = 1 )
    SetSpriteColor ( 2, 255, 0, 0, 255 )
    SetSpriteColor ( 3, 255, 0, 0, 255 )
else
    SetSpriteColor ( 2, 255, 255, 255, 255 )
    SetSpriteColor ( 3, 255, 255, 255, 255 )
endif

When the program runs and sprite 1 intersects this line sprites 2 and 3 will change color to red.

More information is available to us after a ray cast has occurred, for example, it's possible to determine the ID of the sprite involved in the ray cast by calling GetRayCastSpriteID and you can find out the position of the collision by calling GetRayCastX and GetRayCastY. These commands only return valid information if SpriteRayCast or PhysicsRayCast return 1 indicating a collision took place.

Full code listing

Everything is now in place. Here's the final code for our program:

SetVirtualResolution ( 320, 480 )

LoadImage ( 1, "gold.png" ) LoadImage ( 2, "silver.png" )
CreateSprite ( 1, 1 ) SetSpritePosition ( 1, 150, 0 ) SetSpriteShape ( 1, 1 )
CreateSprite ( 2, 2 ) SetSpritePosition ( 2, 30, 200 )
CreateSprite ( 3, 2 ) SetSpritePosition ( 3, 260, 200 )
direction = 0
do if ( SpriteRayCast ( 30, 200, 260, 200 ) = 1 ) SetSpriteColor ( 2, 255, 0, 0, 255 ) SetSpriteColor ( 3, 255, 0, 0, 255 ) else SetSpriteColor ( 2, 255, 255, 255, 255 ) SetSpriteColor ( 3, 255, 255, 255, 255 ) endif
if ( direction = 0 ) SetSpriteY ( 1, GetSpriteY ( 1 ) + 1 )
if ( GetSpriteY ( 1 ) > 400 ) direction = 1 endif endif
if ( direction = 1 ) SetSpriteY ( 1, GetSpriteY ( 1 ) - 1 )
if ( GetSpriteY ( 1 ) < 30 ) direction = 0 endif endif
sync ( ) loop

Conclusion

There are a few key points to remember when needing to perform a ray cast in your games:

It's also worth noting that alternative commands are available for ray casting, such as the ability to perform a ray cast against a group of sprites. It is also possible to perform a ray cast on a single sprite. The commands to deal with this functionality are:

The commands PhysicsRayCastGroup and SpriteRayCastGroup are used in conjunction with the SetSpriteGroup command. This is useful for a situation where you only want to perform collision checks against a certain set of sprites.

When you want to perform a ray cast with a specific sprite use the command SpriteRayCastSingle.