Sprite depth

Description

The order in which sprites are drawn is controlled either by the order in which they are created or by altering their depth property. Understanding how this works is important for games that rely on multiple layers of sprites being displayed.

This example takes a penguin sprite:


And a football sprite:


And demonstrates the impact of load order and controlling sprite depth using the in-built commands.

Load order

This block of code creates a sprite using the penguin image and then creates a sprite using the football image:

LoadImage ( 1, "penguin.png" )
CreateSprite ( 1, 1 )
SetSpritePosition ( 1, 100, 300 )

LoadImage ( 2, "ball1.png" ) CreateSprite ( 2, 2 ) SetSpritePosition ( 2, 125, 300 )

At this point the penguin sprite will be drawn first, followed by the football sprite:

The code is now adjusted so that the football sprite is created first and the penguin sprite second:

LoadImage ( 2, "ball1.png" )
CreateSprite ( 2, 2 )
SetSpritePosition ( 2, 125, 300 )

LoadImage ( 1, "penguin.png" ) CreateSprite ( 1, 1 ) SetSpritePosition ( 1, 100, 300 )

This will result in the football being drawn first and then the penguin:

Controlling the draw order

Altering the order in which sprites are created isn't always going to be the best approach for controlling draw order. There may be situations where you want to have some sprites drawn at the front or nearer the back and be able to handle this whilst the game is running. To do this use the command SetSpriteDepth. This command takes two parameters - the ID of the sprite and a value controlling the depth, which is by default a value of 10. Lowering this value will force a sprite to be drawn nearer to the front of the screen and increasing this value will send the sprite to the back of the screen.

The first example code showed the penguin being loaded first, followed by the football, resulting in the penguin drawing first and the football being drawn last. To swap the order of drawing, without adjusting the load order, the SetSpriteDepth command can be used:

LoadImage ( 1, "penguin.png" )
CreateSprite ( 1, 1 )
SetSpritePosition ( 1, 100, 300 )

LoadImage ( 2, "ball1.png" ) CreateSprite ( 2, 2 ) SetSpritePosition ( 2, 125, 300 )
SetSpriteDepth ( 1, 0 ) SetSpriteDepth ( 2, 1 )

The penguin has its depth set to 0, meaning it will be drawn last, and the football has its depth set to 1, resulting in it being drawn first:

Finding the depth of a sprite

To retrieve the depth of a sprite call the command GetSpriteDepth, for example, this code will find the depth of sprite 1 and 2:

depth1 = GetSpriteDepth ( 1 )
depth2 = GetSpriteDepth ( 2 )

Full code listing

The final program has the penguin created first, followed by the football. Within the main loop, whenever the user clicks or touches the screen the draw order is swapped around. Here's the final code for our program:

SetVirtualResolution ( 320, 480 )

CreateSprite ( LoadImage ( "background3.jpg" ) )
LoadImage ( 1, "penguin.png" ) CreateSprite ( 1, 1 ) SetSpritePosition ( 1, 100, 300 )
LoadImage ( 2, "ball1.png" ) CreateSprite ( 2, 2 ) SetSpritePosition ( 2, 125, 300 )
do Print ( "Click or touch the screen to change" ) Print ( "the order in which sprites are drawn" )
if ( GetPointerPressed ( ) = 1 ) if ( state = 0 ) SetSpriteDepth ( 1, 0 ) SetSpriteDepth ( 2, 1 ) state = 1 else SetSpriteDepth ( 1, 1 ) SetSpriteDepth ( 2, 0 ) state = 0 endif endif
Sync ( ) loop

Conclusion

Being able to control the order in which sprites are drawn is an important task and as seen in this example, AppGameKit Studio provides the ability to control this whether it be through the load order of sprites or the SetSpriteDepth command.