Hi everybody! I need to generate atlas files by directories! How to make this? For example, I have two directories with textures "Head_Textures" and "Body_Textures", so I need to get two atlasses for each of directories! Is this possible in Spine?
Runtime status: meshes, FFD, skinning
Sure, just run the packer twice. You can run it from the menu, you don't have to create an atlas when you export data. Doing that is just a convenience.
Ok! I created two atlas textures for each directory! And I have two .atlas files! I use Unity! But I can't use both .atlas components in one animation object, because there is only one field for Atlas in Spine Data Component! I want to use two atlases in one animation!
I can use two or more materials in one Atlas Component, but how to combine two atlas files in one? Or what I should do?
You said you wanted 2 atlases, so I told how. 
If you want one atlas, then point the packer at the parent directory. You will end up with 1 atlas that has 2 pages (if you have 2 subdirectories). Check Combine subdirectories if you want to try to pack all the images on a single atlas page.
spine-cocos2dx has been updated to use cocos2d-x-3.1alpha0. It doesn't have meshes yet though.
Nate ：spine-cocos2dx has been updated to use cocos2d-x-3.1alpha0. It doesn't have meshes yet though.
Just a heads up looks like you've not updated the Example Spine project to reference the correct cocos2dx project file for iOS (unsure about others).
Just a suggestion the cocos2dx folder in example maybe should be renamed to cocos2d-x to reflect the real cocos's folder and as mentioned above should reference cocos2d_libs.xcodeproj in build folder rather than cocos2dx.xcodeproj which doesn't exist.
Keep up the great work, can't wait for meshes to be done
Hi nate, I saw you're working on spine-cocos2dx runtime with updating cocos2d-x version 3.
I'm worried about how spine-cocos2dx support past version of cocos2d-x.
our project is decided to stay on version 2, because we have tons of code extending cocos2d-x to improving its functionalities.
there's about a hundred classes extending cocos2d-x, and it is hard to do make all that classes working on version 3 stable.
I do need support cocos2d-x version 2.
have any plans?
The folder in the cocos2d-x ZIP is named cocos2d-x-cocos2d-x-3.1alpha0.
The iOS and Android example projects are till for v2 and haven't been updated, I'll do that last. I considered deleting them until that was done but then figured that would make more work if someone wants to get to it first.
kzerse, from a few small polls, it seems most users wanted cocos2d-x v3. It is a lot more work to support multiple versions of the same libraries. With 18 runtimes, even just twice as much work is significant. I would rather not officially support older versions if at all possible, especially if only a handful of users need it. If you need to upgrade for new features (meshes, FFD, skinning) then I would suggest back porting those features to the v2 runtime. spine-c does most of it for you, it is only rendering that needs to be implemented. If the existing runtime is working for you, maybe you don't need to use the latest runtime?
When we purchased your product, we heard your plan to add new features including meshes of Spine-Runtime through your forum and Trello board. Of course, we’d want to benefit such new features, so we started game development, utilizing your product actively as soon as the meshes implemented in Spine Editor. Since we had no knowledge that you would drop the support for Version 2, and have been using new features a lot, we need support for V2. (As you know we can’t just version up the engine and we believe there will be many more clients like us as your current customers start utilizing your updated version and realizing your drop of V2 support)
Anyway, if the whole support for V2 is too much burden for you, we are willing to help out and to bear the burden with you together. We can implement the porting for Version 2 but after this initial implementation, the maintenance should be your work to do. Since the changing points of Editor should be reflected in Runtime, I’m afraid that we can’t do the maintenance work. Let us know if it’s possible for you to maintain it once we implement it? Our initial implementation work will also include bug fix
Thank you for your consideration and hope to hear from you soon. Also, if you’d like to discuss this unofficially, please feel free to contact me directly (<removed>)
hi again! I have another problem! I create Spine Project in Spine PRO in WIndows 7! But when I try to open this project on Mac, i Have an error "Error occurred when reading project file"! What I can do, to open this project on Mac?
And one more question! Some projects in Spine have problem when importing in Unity! The error is
Error reading atlas file for atlas asset: bonusAtlas
The requested value was not found
How to fix this error?
OlegDustcase, please start your own thread to discuss your issues so that this thread can remain on topic.
kzerse, if it is unavoidable, I can create a spine-cocos2dx-v2 runtime. This would be a Git repository separate from the spine-runtimes repository. I will do this once the cocos2d-x runtime has meshes, FFD and skinning. I will post in this thread to let you know. Once created, any effort you can provide to help port features from spine-cocos2dx to spine-cocos2dx-v2 would be very much appreciated.
I wanted cocos2d-x v2.
cocos2d-x (v3) has meshes, ffd and skinning! I'll port this to a v2 runtime soon.
Thank you for your support. I will help if there’s anything I can do for this.
4 天 后
cocos2d-x versions 2.2.3, 3.0 and 3.1alpha1 are now supported:
https://github.com/EsotericSoftware/spi ... e-cocos2dx
spine-cocos2d-iphone has been updated with meshes, FFD and skinning! It also gets blocks for AnimationState listeners. Only cocos2d 2.1.0 is supported, but 3.0 and 3.1 will be coming very soon.
There is now a spine-cocos2d-iphone available for cocos2d-iphone 3.0. I will do 3.1 later when it is more stable. It isn't so different from 3.0 anyway. For now I need to move on to the other runtimes!
Hi , nate, I'm writing runtime code by myself for own engine. When parse skinned mesh ffd , found a strange json data.
The skinned mesh apply ffd , the ffd vertices count sometimes is even number, sometimes is odd number.
In my case , I bind two bones for skinned mesh and apply ffd , the result I get ffd vertices count is 9
I don't know whether it is a bug, In my mind, the ffd vertices must pair of x and y coordinate shows, so must be even number
thanks
They are x,y pairs but "offset" is how many entries are zeros at the start. Also, zeros at the end are not output.
- 已编辑
Nate ：They are x,y pairs but "offset" is how many entries are zeros at the start. Also, zeros at the end are not output.
:happy: Thanks for answer, understand ! That means ffd vertices may not ouput 0 data at the end
I got data like below
"head": {
"head": [
{
"time": 0,
"offset": 4,
"vertices": [ 0, 0, 0, 0, 0, 0, 0, 0, 0 ]
},
{
"time": 0.3333,
"offset": 2,
"vertices": [ 10.57, -9.6, -14.2, -1.48, 0, 0, 0, 0, 0, 0, 0 ]
},
{
"time": 0.6666,
"offset": 4,
"vertices": [ 0, 0, 0, 0, 0, 0, 0, 0, 0 ]
}
]
},
Notice, vertices count all odd number, and output 0 data. By your said, it is should be not output 0 :wonder:
It's because the values are very near zero, then later rounded to zero for JSON output. Binary doesn't do any rounding. Fixed in next version!
Nate ：It's because the values are very near zero, then later rounded to zero for JSON output. Binary doesn't do any rounding. Fixed in next version!
:happy: Thanks a lot, get it
12 天 后
spine-starling now has meshes, FFD and skinning! It was a bit of work, had to write my own renderer for meshes.