You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to import .json from dragon bones?
-Currently we can export from COA tools > to Dragon Bones > to Spine.
*Dragon Bones has a "Spine 3.3" importer.
*If COA tools could import .json data from Dragon Bones, plus we could already have a file in all 3 programs without any problem.
Is it possible for COA tools to have a Dragon Bones importer in the future or is it something very difficult to implement? If not what parts could I investigate to solve it.
Another possible way would be to see what data has the .blend and .json of dragon bones to make an external conversion with some script.
I want to make assets in COA tools for games, and it is interesting that the user can edit the animation using the program that is convenient for him (COA Tools, Dragon Bones or Spine) and use it in the engine he needs according to his needs (dragon bones, creature, spine).
The text was updated successfully, but these errors were encountered:
Would it be possible to import .json from dragon bones?
-Currently we can export from COA tools > to Dragon Bones > to Spine.
*Dragon Bones has a "Spine 3.3" importer.
*If COA tools could import .json data from Dragon Bones, plus we could already have a file in all 3 programs without any problem.
Is it possible for COA tools to have a Dragon Bones importer in the future or is it something very difficult to implement? If not what parts could I investigate to solve it.
Another possible way would be to see what data has the .blend and .json of dragon bones to make an external conversion with some script.
I want to make assets in COA tools for games, and it is interesting that the user can edit the animation using the program that is convenient for him (COA Tools, Dragon Bones or Spine) and use it in the engine he needs according to his needs (dragon bones, creature, spine).
The text was updated successfully, but these errors were encountered: