Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

[AS3][Starling] Update to 3.4.0

Mario

Hi there,

we have updated the ActionScript3 and Starling runtimes to Spine 3.4.0. This update brings you improved transform constraint, shearing and paths! Check out the new tank example in the Starling example project to see paths in action.

This update is also deprecating the spine-starling runtime for Starling 1.7. You can find a branch for that Spine runtime here, which is compatible with Spine 3.1.08. We will not back port new Spine features to this deprecated runtime. However, it should be easy to grab the ActionScript3 runtime (which contains the bulk of the runtime code) and retrofit it to 1.7.

The update to Starling 2.0 has simplified the spine-starling runtime considerably! Thanks to Daniel Sperl from Gamura for his support during the port.

Happy coding!
Mario

LegioXV

Guys,
after using this package with Flash Pro 2015 CC I get error below at TankExample (and any example) class at step 'addChild(skeleton);' for any of your examples

ReferenceError: Error #1069: Property http://adobe.com/AS3/2006/builtin::insertAt not found on __AS3__.vec.Vector.<starling.display::DisplayObject> and there is no default value.
   at starling.display::DisplayObjectContainer/addChildAt()
   at starling.display::DisplayObjectContainer/addChild()
   at spine::TankExample()
   at starling.core::Starling/initializeRoot()
   at starling.core::Starling/initialize()
   at starling.core::Starling/onContextCreated()

And my new animation doesn't work with old runtimes after 3.4.0 anymore (however old animations worked with old runtimes)
I need your help asap, as this issue breaks me deadlines.

Mario

From a first glance this appears to be an issue with the Flash player and Starling versions you use. What version are you on? Starling 2.0 requires Air 4.1 and Flash Player 11.4 as a minimum IIRC. We might have to escalate this on the Starling forums, as the code that crashes is in Starling itself and not the Spine runtime.

LegioXV

So far this is the settings for publishing I have in Flash, AIR 2.5 as maximum.
Loading Image

Could that mean if I switch to Adobe Animate CC everything should work fine?

Mario

Ok, I've had some input from the Starling creator (thanks Daniel!). Starling 2.0, and hence the latest spine-starling runtime, require at a minimum Flash Player 19/Air 19. I'm afraid I'm not familiar with and don't have a license for Flash Pro. You will need to add a Flash Player 19 target to Flash Pro. Maybe some other spine-starling users can chime in here on how to do that. Or you could ask on the Starling forums.

Found this, looks like Animate is the successor to Flash Pro. Maybe upgrading to that gives you Flash Player 19/Air 19 support. http://forum.starling-framework.org/topic/goodbye-flash-pro-hello-adobe-animate

LegioXV

Thanks badlogic,
I confirm this solution - after updating to Animate CC mentioned issue is solved

P.S.: you're doing a great job guys, your application is doing some real magic with meshes!

schsj

Why will no longer be supported by version 1.7? Most large-scale projects do not plan to upgrade to version 2.0, And now we can not use the new functionality of spine. PolygonBatch do not support new features, only MeshBatch?

Mario

We are a small team and don't have the resources to support multiple, incompatible versions of an engine. That being said, you can take the spine-as3 code that's compatible with the latest Spine features, and modify the Starling 1.7 specific code. The only real big change is how mesh attachments are handled. The old PolygonBatch should be able to support everything in 3.4.01.