Nate написал

1) Polygon packing would be great, but it's quite complex. Even rectangular bin packing is NP hard.

N is not that big in our cases. Unity and TexturePacker already have it, but I dont know which algorithm they are using. Did you at least investigate it?

Nate написал

2) What benefits are there to putting Spine on Steam? What Spriter does is not interesting for us.

I thought you'll be able to sell stuff in regions, but I dont know if its possible to sell periods and not whole app.

Nate написал

3) I understand the difference in economies between the US and eastern Europe (I live in Croatia). However, it's difficult to make discounts fair, especially for a lifetime license. Unfortunately we haven't been able to come up with a reasonable solution.

Make it yearly, like texturePacker. Even JetBrains doesnt sell life-time licenses anymore.

I agree. Yearly License would work for us as well. I mean, I would love to support you guys and keep Spine evolving and I would like to see more features. I would even agree to pay for 3.0 Upgrade. Chaos Group doing the same. for example Vray Version 2.0 was 1000$ and all the next version before 3.0 are free.

In addition, what would be cool, if you could have some kind AKA kick starter for Features. So let's say 50 users want to have some feature, those users can donate I don't know whatever 50 EU for example and then you add this feature, even thaw for the rest it will be kind free.

Just some crazy idea.

Just FYI, whatever other company or group is doing historically hasn't been a strong argument for Nate. :p
Any facts and info are helpful though.
And it's cool when we hear about sensible demand and not arbitrary should-be-this-and-that. So thanks for sharing!

For now, there's work to do! Lots of new features for Spine this year! (I hope I don't jinx it!)

Hi guys,
I have just updated to Spine 3.0.02 and think there are new bugs introduced.

1. Rotation angle edit box changes its value on focus change if negative scale is set.
   Here is the first video describing this bug as usual

2. Key frame navigation became broken.
   If I drag timeline cursor the key frames are playing normally, but if I just click at specified key frame nothing changes.
   And the second video is also here.

Awesome! The new scaling is great! Eagerly awaiting the Unity runtime

Damn, so I've basically just made my work file useless as i've saved it in v3, but v3 exports don't work with Unity at the moment? Did I miss some warning with the update on the program that let me know that my files were going to be held hostage until the runtime is updated?

When is this likely to be fixed? Is there anything that can be done to work around backwards compatibility? I've got older versions of the file if that helps?

Also, another discovery while I'm here! When exporting, in V.3, spine/texture packer isn't exporting all the assets used in the animations. It's just flat out ignoring about 1/3 of them. I've restarted and downgraded (due to the whole not working thing of V.3) and they export perfectly in any version earlier than v.3.
In my case, I have about 11 skins, each with a flailing arm animation which consists of about 20 pngs per character (a png sequence rendered from AfterEffects). When exported, V.3 Spine/TP only exports one skins set of arms, and ignores the other 11 skins worth. Yet it exports all 11 skin's other assets (heads, bodies, legs) just fine. Any Ideas?

I'm on Mac btw.

Any suggestions for either of these issues would be much appreciated. Cheers.

I ran into the same thing. Luckily I had a copy of the file backed on online.

@Iluks if you saved your project with an older version there should be a backed up version in the backup folder. If you go to "Settings" you can open your backup folder from there and check.

Would it be possible for you to share your project that is causing exports to fail? If so please send it to contact@esotericsoftware.com and include a link to this thread so we know where it's coming from.

Sorry for the problems. 3.0 is a very large upgrade but we'll have the bugs ironed out soon. We are working crazy hours to fix things.

What about Unreal 4 runtime?

Nate, any changes for my "loading bug"?

Don't know if it had been posted yet, but there's still a bug that forces me to close spine and reopen it in order to load a skeleton exported via photoshop script. (all the pieces end up in the same place instead of having their correct disposition). Also at some point if I'm moving the bones or the origin some points of a mesh stay in the same place deforming everything instead of moving with the root.
Both problems vanish after restarting but they're happening quite often and it's getting a little bit annoying.
Btw new scale system is definitely better! I can't wait for the new stuff to be implemented (: excited

EDIT:
Here I recorded a video of the root bug:

Finally !! I am able to make this.
Thanks spine 3.0!!! :beer:

Very cool Hwadock!

I know the question "how did you do it?" will be asked.
So here is a Spine project you guys can take a look at to see how to do it.

Hello. One important question. If i used v.2.1.27 before. Can i switch to 3.0.05 within a one project? Does Unity SDK supports older versions?
For example my game already contain few characters made in 2.1.27. If i update to 3.0.05 and make few character animation in new version. Will i have problem with the old animation in my game with new SDK?
I hope i clearly described. Thanks in advance.

Shiu написал

Very cool Hwadock!

I know the question "how did you do it?" will be asked.
So here is a Spine project you guys can take a look at to see how to do it.

how could you not do that in <3?

artist confirmed it was magic

this 3.0 stuff confuses me :x :x

@effectic:
v3.0 runtimes will ignore flipX and flipY and won't be backwards compatible with inherited local-axis scaling.
If you used non-uniform scale before, you may need to adjust your animations. But it's also possible that they look just fine. (I used to use non-uniform scale at really tiny amounts just to warp sprites a little.)
If you used bone flipX and flipY, you DEFINITELY need to switch your animations to using negative scale and re-export.

If you DIDN'T use non-uniform scaling on non-terminal bones, or flipX or flipY, everything should work normally.

@[удалено]
It was one of the first things I tested when I first got Spine.
You definitely couldn't do that before.

Hi, I have a problem with the installation of the last spine version (3.0.07) I don't know what to do, because every time An unexpected error message appears after the download. Can you help me, please? Thanks a lot!!

Nate, why Spine loading is so slow? I have Photoshop, Visual Studio and other software - loads in 1-2 seconds ... Spine takes about 10 seconds to load, why?

Nate написал

kxs, we're working on that. If you choose Local axes it should work better.

Fran90, please see this thread: http://esotericsoftware.com/forum/Spine-3-0-05-3-0-07-update-fails-5722

thanks

Nate написал

I admit I haven't investigated polygon packing yet. Of course it's possible and I would definitely like to have it.

I found this MIT licensed project last week that does polygon packing.
https://github.com/Jack000/SVGnest

The only problem is that it's written in in javascript and not java

I think I have the same problem as puzzler. I updated to to V3 today and every time I launch it downloads the latest build - v3.0.0.8.

I've tried manually setting the version rather than having it on "latest" but there was no change.

Shiu написал

Very cool Hwadock!

I know the question "how did you do it?" will be asked.
So here is a Spine project you guys can take a look at to see how to do it.

I opened the spine project but i still dont get how you skewed the image in spine? :think:

majzim написал

I opened the spine project but i still dont get how you skewed the image in spine? :think:

Change the scale of the parent bone. then when you rotate the child bone the image appears to be skewed.

Oh man this is so cooooool! We did something similar in a project last Spring but it took so much more work to get an effect that didn't look this slick. I'm likin this 3.0 so far

i work with the 2.1.27 for an html5 project. Can i update to the 3.0.7 ? the html5 runtime is ok for this new version ?

Not yet. Only libGDX is updated to 3.0 right now.

i second the html5 runtime update !!

Hello guys, how many of you did join the global game jam?
I'm jamming right now, a perfect time to discover bugs! lol.

New bug I found:
I tried to set a bone with images and other bones attached to mirror it, when I try to pose it spine freaks out.
Video:

but this is outrageous! why couldn't you leave the flipXY function for compatibility purposes!?! we are in the middle of game development and now all of our animations are screwed! we had to revert to 2.1.27 and we can't use the new stuff from v3! :bang:

Hi, I have a problem with spine export function especially when exporting spine from command line and btw I'm using mac. Usually my team export all the spine assets using automated python script thus we need to use spine CLI to export things, everything is fine until recently I've updated the spine app to v3.0.08. When exporting spine using CLI, the width and height data in the JSON file is always 0 and I don't know why. But when I try to export without CLI, the width and height is exported correctly in the JSON file. Reverting back to previous version can fix this but some of my spine projects have already upgraded to v3.0.08.

I apologize if this has already been covered, but I just installed the current version on my system (32 bit XP).
It installed without issue, but when I attempt to launch the application the program never starts. No error messages, just complete lack of activity.
Is there an error log that I could check? Or are there any other suggestions?

Hi, we have a problem with the CLI exporter: some attachments are consistently getting width and height equal to 1 if we run export from CLI, but if we run export on the same project from Spine itself then everything is fine. I reproduced it with 3.0.07 and 3.0.09 on Windows. There was no such problem with v.2.

Hi! Any ETA for 3.0 Unity Runtimes?