otayax.blogg.se

1. #Dragonbones pro merging animation files how to#
2. #Dragonbones pro merging animation files install#
3. #Dragonbones pro merging animation files download#

Then you iterate through all of the sprites in the FlxGroup to set their initial properties (such as scale, placement in the world, ect.) as you please. Otherwise, check your animation in DragonBones to find the name and pass it in as a string. Generally you’ll only have one armature, so just pass in the first index of the armatureNames array from the data you got earlier. You also pass in the name of the armature (the animations skeleton). This is because with many different sprites, if you want to check the collisions of the entire “character” then you have to have one large collision box. One thing to note is you also have to pass in a collision box similar to the Flixel Spine plugin. buildArmatureDisplay ( new FlixelArmatureCollider ( 250, 250, 27, 25, 13, 8 ), dragonBonesData. You can do so by declaring a variable and then assigning the new FlxGroup to it which you will generate using the factory. Then you have to create a FlxGroup which will contain all the DragonBones Flixel Sprites. getBitmapData ( "assets/dragonboy_flixel_tex.png" ) ) Build Armature getText ( "assets/dragonboy_flixel_tex.json" )), Assets. getText ( "assets/dragonboy_flixel_ske.json" )) ) _factory. var dragonBonesData : DragonBonesData = _factory.

Then you have to use the factory to parse the animation files that you’ve exported in order to read their data. Then, inside the create function under your FlxState class you have to create a FlixelFactory which generates flixel objects for DragonBones like so: var _factory = new FlixelFactory () Parse Data FlixelEvent import dragonBones.animation. FlixelArmatureCollider import dragonBones.flixel. FlixelArmatureDisplay import dragonBones.flixel. FlixelTextureAtlasData import dragonBones.flixel. DragonBonesData import dragonBones.flixel. Then save it to the assets folder in your Flixel project.įirst, import the packages we'll be using. Once you’re done, go to File > Export and export the animation using Data Version: 5.0 and Image Type: Texture Atlas. For the sake of this tutorial, we’re going to use a premade project that comes with DragonBones called DragonBoy that you can select from the starting menu.

Then create a new animation using DragonBones.

#Dragonbones pro merging animation files download#

You can also download the sample project instead to follow along.

Then create a new Flixel project template with Flixel Tools, and add DragonBones to your Project.xml.

#Dragonbones pro merging animation files install#

Installįirst install the library from haxelib using: haxelib install dragonbonesĪlthough it’s better to install directly from GitHub in order to always keep up with the latest updates: haxelib git dragonbones How exactly do you use DragonBones with Flixel? Well, that’s what I’ll be showing you, so let’s get started. Its DragonBones export should also work with the Flixel backend I’ve created. If you want a truly open source editor which can export to the DragonBones format while also being fully featured, check out the great alternative COA Tools for Blender. *One caveat is that DragonBones is not truly open source (if you care about that sort of thing), only the runtime is. Not only that, DragonBones is a fully featured, intuitive bone animation editor and has Mesh Deformation support just like Spine. Why would one use it over Spine? Well Spine can potentially be quite expensive for new indie devs, and DragonBones is free. Its a tool which allows you to animate static 2D images programmatically (similar to Flash tweening) without having to painstakingly animate each individual frame in a spritesheet.

#Dragonbones pro merging animation files how to#

I’m here to write a post about DragonBones support for HaxeFlixel and how to use it.įirst of all, what is DragonBones? DragonBones is a free *open source alternative to the popular 2D bone animation tool Spine (which Flixel already has support for). Hi there, I’m Troy ( creator and maintainer of the HaxeFlixel backend for DragonBones.