“On the runtime side of things, almost all of the runtimes are up to date with the latest editor features. Corona is yet unable to render meshes, but the Corona guys are working on that. LÖVE can render meshes, but hasn’t been updated to do so yet. All the other runtimes are up to date and work great with IK, meshes, weights, bone flipping, etc.”
Hopefully Corona Labs will sort this out as this isn’t the best promotion for Corona.
Technically speaking we already support meshes under the hood. We are working with Spine and some others to figure out how to expose the API so that everyone’s needs are met. No ETA on delivery.
Technically speaking we already support meshes under the hood. We are working with Spine and some others to figure out how to expose the API so that everyone’s needs are met. No ETA on delivery.
@pickerel: Yes we have plans. My previous post states that. If you’re asking if we’ve made any progress, then I’m going to say no. Now I’m not always privy to engineering discussions, but I’ve not heard of any.
Right now our focus is on the Fuse Integration, OS-X and Windows builds. There is no feature requests in our feedback site for this. We can’t track interest in the forums. I highly suggest that if you want to raise awareness of this feature that you go to:
This is a showstopper for us. We’ve been evaluating Corona for a new app and requires a high quality drawing output. Lack of anti-aliasing would be a nail in the coffin
This is very, very important for business app. I’ve been waiting for this solutions for the last 4 years and nothing has changed. It is impossible to develop good business app due to limitation of native object - textfield,webview etc. Please corona do something alternative!
The total number of votes doesn’t determine when we get to it. Other factors like how difficult it is to implement? how much support it will require? How cross platform will it be? What work arounds are available?, etc.
So things like widgets to replace native text fields is something we probably won’t tackle until we get a 10 fold increase in engineering resources. It’s simply too hard and time consuming with regards to engineering time. We did a tutorial on how to build a widget framework around native.newTextFields, we’ve made them able to be moved in groups, help with positioning and text sizing with them and the community has built a very full featured widget that still uses native.newTextFields. To actually implement the text fields as OpenGL objects would be insanely difficult. We get it that you want it, but its simply not practical.
Vector Graphics I think would be quite popular, but we’ve been chasing more important features, features that will impact more users and things that get dumped on us. We have to keep functioning when Apple, Google, Facebook and such dropping breaking changes on us and an increasing rate.
So maybe after we get Windows and OS-X builds out the door and we get the Fuse items integrated then we can tackle more things on the list. Windows and OS-X builds are two of the most requested features. But it won’t get tackled if its not on the feedback site and there are not votes, then it won’t happen for sure.
FYI For anyone else following this link and want meshes in Spine heres the vote link. Cant hurt getting some extra votes to increase support to get this fixed. Please give it a vote
Devs we realise that theres a lot on your plate, but if this is a low-medium hanging fruit in terms of difficulty we’d love you to shift up urgency, or do a late nighter and daily build a version where you rejig vertex scaling and mesh redering with a spine workaround for time being.
@pickerel: Yes we have plans. My previous post states that. If you’re asking if we’ve made any progress, then I’m going to say no. Now I’m not always privy to engineering discussions, but I’ve not heard of any.
Right now our focus is on the Fuse Integration, OS-X and Windows builds. There is no feature requests in our feedback site for this. We can’t track interest in the forums. I highly suggest that if you want to raise awareness of this feature that you go to: