New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: converting from version 2.x/3.x #2
Comments
Hi, we will fix the bug asap :) |
Hi, the bug has been fixed, you can upgrade the tools. |
Thank You @akdcl, updating with |
did this patch/fix landed in the master branch of the repo? using same input (exported.zip from above) and latest commit i am missing some transform...
while the npm version of the converter (@0.0.31) gives for the same input
|
Our use-case involves a library solution (without the proposed converter web-service), executable inside browser for 'on-the-fly' conversion of dragonbones skeletons from old formats to currently used ones. Hope it helps to clarify the previous question. To build the library
|
@mobiledevnetwizzy Hi, the bug has been pushed to master branch, is it still has transform bug with 2.x to 5.x? |
@akdcl aparently yes, but i'm not quite sure because of a clean clone build failing for dragonbones tools.
Adding the following dependencies to
i'm left with the Cloning and building the repo of @bitbay the result is the same (bug present), but it may have to do with that repo and not the Tools itself. |
@mobiledevnetwizzy if you want to build the tools, you can run command like this:
You can read the README.md to find how to build the dragonbones tools. |
I tried to convert an animation exported from Flash using the DesignPanel v3.0.1 to the new v5.5 format, but it seems that one of the two is failing:
I attach two images and the two skeletons with their textures/atlases.
This is how it is expected to look like:
...and this is how it ends up
This is exported.zip from DesignPanel 3.0.1, using the command
$ db2 -t new -i ./exported -o ./converted
i got to this skeleton converted.zip
The text was updated successfully, but these errors were encountered: