• Runtimes

  • swift runtimes?

    英语

I don't see any runtimes for swift-Spritekit. I purchased this program hoping to use it but now I am not sure how since there is no tutorial on this particular language- API. I am going through the tutorial on Ray Wenderlich site but it is a bit out dated. The runtime they suggests don't work. Any help would be greatly appreciated. a Tutoriol or source code would be GREATLY welcomed.

Related Discussions
...

I haven't tried Swift yet, sorry. There are examples in spine-cocos2d-iphone, not sure how applicable they are to Swift stuff.

8 天 后

I am relatively new programing so I not going to be able to use cocos-2d stuff at all. This is very frustrating. If there is a good Sprite kit-Objective version I can usually convert it to Swift but this is not the case. I am dead in the water.

Dec, 1 2014 using the newest updates:
Ok, I worked out the best possible solution until the Sprite runtimes are written in swift. Use this link to find the runtimes in Objective-c.
https://github.com/mredig/SGG_SKSpineImport. This oen is the only now I could get to work.
Copy over the "SpineImporter" file and all it's content. While uploading that file onto your Swift project Xcode will ask you for a bridging head. Check YES. then go to the bridging file and type this #import "SpineImporter.h". from there you can use the files inside of your swift project. Below is the code to get the Spine animation to work inside of swift. One last think, cope over your Spine files and the Atlas file that goes to your Spine file(total4 files). Make sure that you have changed the names in the code below to reflect your own files. This should get you started.

//put in GameScene or intended animation file.
import SpriteKit

class GameScene: SKScene {
    var mo = SGG_Spine()
    

override func didMoveToView(view: SKView) {
    backgroundColor = SKColor.whiteColor()
    
    mo.skeletonFromFileNamed("skeleton", andAtlasNamed:"MOCharacter", andUseSkinNamed:nil)
    mo.position = CGPointMake(self.size.width * 0.5, self.size.height * 0.3);
    mo.runAnimation("animation", andCount: -1)
    mo.queuedAnimation = "animation"
    mo.queueIntro = 0.1;
    mo.zPosition = 20;
    mo.xScale = 0.4;
    mo.yScale = 0.4;
    mo.zRotation = 0.0
    addChild(mo)
    
      }

override func touchesBegan(touches: NSSet, withEvent event: UIEvent) {
    for touch: AnyObject in touches {
        let location = touch.locationInNode(self)
//            self.inputBegan(location) // uncomment if you want to use touches
           

    }
}

func inputBegan(location: CGPoint) {
    mo.runAnimation("animation", andCount: -1, withIntroPeriodOf:0.0, andUseQueue:false)
    
}

override func update(currentTime: CFTimeInterval) {
    /* Called before each frame is rendered */
    mo.activateAnimations()
}
}

Thanks for the update, unfortunately it's not something I know much about (not a programmer) but I've formatted your post so it's a little easier to read with code tags 🙂

I'm going to try what claybear39 is using and then I may write my own iOS 7.1/8.x SpriteKit Swift importer. We'll see how it goes. I'll come back here to post it when I get things worked out. Part of the reason Obj-C libraries aren't all ported to Swift yet is that Swift has changed up several of the basic concepts of coding - and for much of this year was in a beta state that changed. Theoretically you can also bridge between the code because I think swift eventually compiles down to obj-c.

That aside, I really enjoy Spine and look forward to using it in projects on iOS in Xcode.

7 天 后

Thanks for the help Shiu. I will be looking forward to your help too Wave-Existence. With this example I didn't try different poses within the same animation. I was just trying to get the one simple spine run animation to work for a fast approaching deadline project.

3 个月 后

Thanks for what you've posted claybear39, it's a huge help in getting started. I've already added an implementation for the queuedAnimation property that may not be necessary in Obj-C, but was in Swift due to optional mess. I'm going to look into an IK implementation, but it seems like it's going to be a bit more work to do that. I'll either post here or set up a gitHub repo with my changes to Michael Redig's work on these libraries.

5 天 后

I am also really looking forward to a Spritekit Swift runtime. Is there a way to flip skeletons/animations with the SGG_SKSpineImport?

Hi gobione, from what I can tell if you flip a sprite in the Spine editor by animating x or y scale to -1, things work fine as is with SGG_SKSpineImport. I've already tested that and have an example working in an app. I think the skeleton itself can be flipped with the existing tools, but you'll have to double check the example file.
Also worth noting - you'll have to follow claybear39's post to get these libraries set up. That's because they are not yet implemented in Swift, but Apple's interoperability between Swift and Obj-C works really well. It means you'll have to set up the bridging headers. I can see lots of benefits to an official fully Swift and SpriteKit runtime, but the SGG_SKSpineImport libraries may be fine once I've got the IK constraints implemented. (If you don't use those, you're already set with the SGG libraries as is.) Although due to differences in Swift and Obj-C (I think that's why) you may want to add in what I posted on ben_ 's thread on the runtime forums. It's a getter/setter method for the queuedAnimation property. If you don't explicitly state it there you'll end up with a nil reference thrown to the REPL loop and it will crash everytime in Swift.

If you want to wait, I plan to post my updates to the SGG_SKSpineImport libraries on github after I complete the IK constraints classes and methods.

On the implementation of the IK constraints - I have a question for Nate or whoever handles the runtimes on the esoteric software team: (I'm referencing the official generic C# runtimes) where do you find the values in the JSON data to set the BoneData's properties FlipX and FlipY? Are those inferred somewhere by getting the pos/neg sign from the scalar values? Also, where do you get the alpha/mix property for the IKConstraintData and IKConstraint? I'm guessing this is something that can be specified in the editor to say, for instance, I'd like to weight an IK Constraint to 0% in an animation so I can basically use FK animation, or 30% for a partial effect. Is that right?

5 天 后

Great, it works, thanks Wave-Existence!