Sprite Component Reference
Sprite is the most common way to display images in 2D games. By adding a
Sprite component to a
Node, you can display the images in the project's resources in the
You can add a
Sprite component to the node by clicking the Add Component button below the Properties and selecting Sprite from the Renderer Component menu.
Please refer to Sprite API for the script interface.
|Atlas||Auto Atlas which the Sprite display image resource belongs to. (Select In Atlas button after Atlas, this feature is temporarily unavailable and we will optimize it as soon as possible)|
|Sprite Frame||SpriteFrame image resource which is used to render the Sprite. (The Edit button behind Sprite Frame is used to edit the 9-sliced cutting of the image resource, please refer to Use a Sliced Sprite to make an UI image for details)|
|Type||Rendering mode, currently includes
|Size Mode||Specify the size of the Sprite
|Trim||Whether the transparent pixel area is included in the node bounding box, which takes effect only when the Type is set to Simple. Please refer to Auto Trim for SpriteFrame.|
|Src Blend Factor||The source image blend mode.|
|Dst Blend Factor||The destination image blend mode. Together with the above properties, you can mix the foreground and background Sprite in different ways to render, and the effect preview can refer to glBlendFunc Tool.|
After adding the Sprite component, drag the Texture or SpriteFrame type resource from the Assets to the
Sprite Frame property reference. Then, the resource image can be displayed through the Sprite component.
If this SpriteFrame resource is contained within an Atlas resource, then the
Atlas attribute of the Sprite will be set up along with it.
To dynamically replace spriteframe, you need to dynamically load the picture resource before you replace it, please refer to Dynamic loading of resources.
Currently, the Sprite component supports five rendering modes:
Simple mode: rendering the Sprite according to the original image resource. It is normally used along with
Use Original Sizeto guarantee the image shown in the scene is in full accordance with the image designed by the graphic designer.
Sliced mode: the image is cut up into a 9-slicing and according to certain rules is scaled to fit freely set dimensions (
size). It is usually used in UI elements or to make images that can be enlarged infinitely without influencing the image quality into images cut up into a grid to save game resource space. Please read Use a Sliced Sprite to make an UI image for details.
Tiled mode: The image will be repeated to fit the size of the Sprite. If the SpriteFrame is 9-sliced, when the image is tiled, the surrounding width will remain unchanged while the other sections will be repeated.
Filled mode: draws a portion of the original picture in a certain direction and scale, based on the origin and fill mode settings. Often used for dynamic display of progress bars.
Mesh mode: Only support .plist file which is built by TexturePacker (4.0 or higher version) with ploygon algorithm.
Type property selects
FILLED, a new set of properties appears to be configured. So let's explain their roles in turn.
|Fill Type||Fill type selection, including
|Fill Start||Normalized values for filling starting position (from 0 ~ 1, denoting the percentage of total population), when you select a horizontal fill, the
|Fill Range||Normalized values for padding ranges (same from 0 ~ 1). When set to 1, it fills up the entire range of the original image.|
|Fill Center||Fill center point, this property appears only if the
Fill Range Supplemental description
Under both the
VERTICAL fill types, the values set by
Fill Start affect the total number of fills, if
Fill Start is set to 0.5, even if
Fill Range is set to 1.0, the actual padding is still only half the total size of the Sprite.
Fill Start in the
RADIAL type only determines the orientation of the starting fill, when
Fill Start is set to 0, start filling from the x axis positive direction.
Fill Range determines the total amount of padding, which fills the entire circle when
Fill Range is set to 1. A counter anticlockwise fill when
Fill Range is positive, and is filled clockwise when negative.