Libgdx texturepacker5/7/2023 Split sheet tool.įree texture packer uses mustache template engine. First things first, we need to add the LibGDX tools. Rotation, trimming, multipacking, various export formats (json, xml, css, pixi.js, godot, phaser, cocos2d). We will make a new class to handle texture and call it TexturePart (naming convention is not my forte). Only critical bugs will be fixed.įree texture packer creates sprite sheets for you game or site. Free Texture Packer is an open source tool that allows you to pack multiple images into one atlas for you games or sites. You can see this happening on line 6 below.IMPORTANT: I don't have time to imporove this app anymore. We do this by passing it the current value of our animationStateTime variable. When it is time to render our sprite, we ask our Animation instance for the frame that we need to draw - AKA the Key Frame. To help cycle the animation frames, in our update() method we utilise a variable which accumulates the delta time between frames - animationStateTime. In other words, the duration between each frame is 1/15 seconds, or, 0.0666 seconds. On line 11, we create a new Animation instance and instruct it to animate our sprite frames 15 times per second. The Animation class makes it a breeze to animate our sprites. For our purposes, each AtlasRegion holds a frame of animation for our sprite. Note that AtlasRegion has the same parent class as Sprite - TextureRegion, which we have seen before. As an added bonus, because of the way I configured TexturePacker, we receive them in animation order. Its mostly just visual wrapper over LibGDX TexturePacker classes and. On line 10, we ask the TextureAtlas for an array of all the AtlasRegions (frames) belonging to the invader1 sprite. TexturePacker would define an animation walk in the data file. The utility will help you pack and manage texture atlases for LibGDX game framework. On line 9, we create an instance of TextureAtlas, by passing it the path to our spritesheet.atlas file. The TextureAtlas class deals with de-serialsing that file and provides us with handy methods to get hold of the frames for a particular sprite, along with other useful information. This file contains all of the information about each sprite frame I packed. When I packed my sprites into a texture atlas, TexturePacker generated a file called spritesheet.atlas. TextureAtlas = new TextureAtlas("spritesheet.atlas") // 9.įrames = textureAtlas.findRegions("invader1") // 10.Īnimation = new Animation(1/15f, frames) // 11. Let’s have a look at our create() method and it’s supporting class member variables. I’m not going to delve into the details of how to use the tool, as you can just click the link that I have provided.Īll you need to know for this tutorial, is that I have used it to pack the frames needed for my demonstration of Sprite animation, and, that we can get hold of the frames for that animation as shown in the source code below. LibGDX’s TexturePacker is nothing short of excellent. In this post, I just want to put those two classes to one side and look at what libGDX provides us with for sprite animation purposes.īy the end of this tutorial, we’ll have a simple application which animates a sprite, as shown in the video below. In my previous tutorial, we introduced a couple of new classes - XNASpriteBatch and XNASprite - to help us draw sprites in a more familiar way.
0 Comments
Leave a Reply. |