[C-Runtime] Examples/tutorials

BinaryCats

Hello,

Firstly, let me start of with saying that my artist and I love spine, it is a powerful tool which fits our needs. We have noticed that there are a lot of (great) tutorials for using the editor but there seems to be a distinct lack of information for the runtimes (in my opinion). I understand there is a lot of support for the majority of publicly available engines, such as unity, and other API's. However we have our own engine (c++ + dx11), we want to incorporate the bone animation too. I feel that there is information lacking in this area.

I have read through the documentation (http://esotericsoftware.com/spine-using-runtimes/ ), don't get me wrong, it's great but some parts are either lacking information or confusing (granted that is probably to do with me). I also saw that there was a link for an c-spine runtime on git, (https://github.com/EsotericSoftware/spi ... c#examples) but unfortunately the link doesn't work 🙁.

Is there any chance some video for the generic run times? and/or the examples link to work?

As a totally un-bias I would suggest dx11 video tutorial 😉

BinaryCats

Nate

Sorry, the example for spine-c was removed since there was so little to it. I've fixed the link.

Any feedback on what is confusing for the runtimes document would be helpful. We're doing editor documentation at the moment but the runtimes will get similar treatment in time.

The best examples for how to extend spine-c for your game toolkit is to look at the runtimes that use it:
https://github.com/EsotericSoftware/spi ... ng-spine-c
spine-sfml is the simplest one and all the interesting parts are in one file:
https://github.com/EsotericSoftware/spi ... e-sfml.cpp
In a nutshell, you need to implement _AtlasPage_createTexture, _AtlasPage_disposeTexture, and _Util_readFile. After that, all you need is a function that takes an spSkeleton and draws it. This is done by iterating the slots and knowing how to render the different attachment types. _AtlasPage_createTexture sets a void* rendererObject which you can reach from your rendering code.

BinaryCats

Nate schrieb
Sorry, the example for spine-c was removed since there was so little to it. I've fixed the link.

Any feedback on what is confusing for the runtimes document would be helpful. We're doing editor documentation at the moment but the runtimes will get similar treatment in time.

Thanks, that's great to hear, i'll look out for it 🙂

Nate schrieb
The best examples for how to extend spine-c for your game toolkit is to look at the runtimes that use it:
https://github.com/EsotericSoftware/spi ... ng-spine-c
spine-sfml is the simplest one and all the interesting parts are in one file:
https://github.com/EsotericSoftware/spi ... e-sfml.cpp
In a nutshell, you need to implement _AtlasPage_createTexture, _AtlasPage_disposeTexture, and _Util_readFile. After that, all you need is a function that takes an spSkeleton and draws it. This is done by iterating the slots and knowing how to render the different attachment types. _AtlasPage_createTexture sets a void* rendererObject which you can reach from your rendering code.

Ah ok, that is what I was doing as you wrote it, it does seem simple enough, but no doubt you will see a few posts from me asking what I am doing wrong haha 😉

jpoag

BinaryCats schrieb
we have our own engine (c++ + dx11), we want to incorporate the bone animation too

I too use Spine-C to integrate into our own engine (DX9, GL, GLES2) on (Win32, OSX, iOS, Android) with lots and lots of custom Spine related code. E.g. how to attach a custom engine object as a child of a Spine Movie, or how to draw mesh/bone debug stuff.

I'd post the code in it's entirety, but there's a lot of context missing. For instance in the code attached, the ResourceLoader looks in a chain of resource types, like encrypted zip files or app resources before trying the disk.

BinaryCats

oh thanks for that jpoag