Corona is the only runtime not supporting meshes?

I’m using version 3.2.01 and it worked.

Okay, I got it working with the newest version (3.3.07). I did have to do the change that yanko_popov suggested above, not use the shear tool in Spine, and override the createMesh function to load from my image sheet, and now it’s working perfectly.

Does anyone know if the shear tool will eventually be supported? My animator really wants to use it…

I see the Feature request for meshes in Spine has just been updated to: Planned. Sounds exciting. What’s the average time between planned and delivered I wonder? Anyone know any more?
 

http://feedback.coronalabs.com/forums/188732-corona-sdk-feature-requests-feedback/suggestions/8614108-add-meshes-support-for-spine?tracking_code=eb2182edd63f73ac241d19ce3d32e924

@kilopop, there are too way many variable to answer that question. We don’t normally marked things “planned” because the community turns that into a promise.

Rob

@Rob Miracle. Fair enough. Any clues as to why this request has been upgraded to: planned?

Cause I set it to planned for tracking purposes. Normally each week in the team engineering meeting I present the team several items from the Feedback site asking: Yes, we will do this, Maybe, or No. Usually when I get a yes, a work ticket is created in the task manager we use and gets assigned to an Engineer. When that happens, I set the feedback request to “Started”. But with this one, it’s we want to do this, but it’s not assigned to an Engineer yet. It’s in a limbo state and I need a way to track it, so I marked it “planned” which is exactly what “planned” should mean. We intend to do it, but we’ve not worked it in to the schedule.

Because things come up and change our priorities, “planned” can’t be a promise. It’s simply something we want to do.

Thanks for the insight. Sounds like a good plan.

I´m super excited about this!

Thanks to Steven, Vlad and anyone else that has worked on this  :rolleyes:

Steven sent me sample codes that blew me away :blink: Spine meshes working in Corona  B)

That guy is a star  :rolleyes:

@sirmania sounds promising :slight_smile:

As a bit of an update, the changes in the (non-Corona) spine-lua parts have made it into the runtimes. I haven’t yet submitted the Corona-specific part, but that’s all in the spine.lua file in the link I posted earlier.

It might still need a few minor tweaks but should be usable. As I mentioned in another post, I doubt the (planned) Corona API will differ too drastically; in any case, any such changes should be limited to the library. (As an aside, I’m already brainstorming how I could repurpose this stuff, once the mesh burden is lifted. :))

If you do animations with non-skinned meshes, there’s still a looping glitch. In hindsight I was probably looking in the wrong place for it; got a little tunnel vision after puzzling out skinned animations. If I feel motivated one day maybe I’ll try to track it down. Apart from that, I’m not aware of anything major (there might be a render order issue, but that ought to be an easy fix).

Exciting Progress. Thanks for everyones efforts and voting. Rob and team we look forward to your upcoming efforts. Thanks Nick (kadlugan/online2)

Hi @ChunkyApps just finished watching the latest CoronaGeek episode where you showed a very cool sample of using meshes in Spine, would it be possible that you can share your sample? A couple of years ago I did a module for implementing Spine animations in Corona (SpineHelper) but I think your example is way a lot simpler than the one I did

Hi @hector7 I’ve used your SpineHelper  in the past and even watched all your tutorials. Thank you for the work you’ve done on that. A lot of people I speak to are still using your library even now. The code I used I believe was from the latest Spine Runtime example at that time. However, a Spine update broke that code a bit. @yanko_popov above in this thread says he fixed it but I have not tested that. I have been waiting patiently for Esoteric to update their official runtime.

With that said, I’d be happy to share the code with you as I have it. I was planning to put it on GitHub once I had an up to date runtime so as not to cause more confusion but I can email you what I have if you wish. Is your appsglobal email still  functioning?

Hi @ChunkyApps, Wow! It is awesome to hear that my code has helped other people. If you can share the code as it is that’d be great, my appsglobal email address is still working, I just need to refresh my memory as it’s been a while since the last time I coded something in Corona, but I really want to go back to making apps, I really miss it, I even need to go through my own course to re-learn what I taught there!

@hector7- I sent it over. Let me know if you come up with any cool ideas. The official Spine Corona runtime should be updated soon I hope. Most of the other runtimes are already updated and I know it’s on the list.

Great, thanks a lot, let me take a look at the code, it will take me a few days as I need to refresh my memory :slight_smile:

I also am using your module @hector7. I’ve had to modify it here and there slightly, but overall it has been a great tool. Thanks!

@landoncope thanks I’m glad it still working well and that has been helpful to you. I’ll review it again to see if I can adapt it to the new features that the new version of Spine has

@hector7 I am using your Spinehelper and it works great!!! Your tutorials are awesome and have helped me a lot. If you one day would add support for meshes I wouldn’t complain  :wink:  Great job!