[Help wanted] Only some assets drawn in Esoteric example project

[lardois]

Hi and thanks for the great library. Just trying to get familiar with it and run into problem...

Downloaded Spine Trial from Esoteric home page. There are some examples included. Tried to get "owl" example running.

Created asset folder named "Owl" and added Sprite Atlas named "default" under it. "Provides namespace" are crossed in both. Then dropped all the assets from "owl" "images" folder into that Sprite Atlas.

There's no directory structure in Owl Spine project, so no need for other atlases besides "default" I think?

The core is relatively simple, copied from the example:

class MainScene: SKScene {
    
    override func didMove(to view: SKView) {
        
        backgroundColor = .white
        
        if let character = Skeleton(fromJSON: "owl-pro", atlas: "Owl", skin: "default"){
            
            character.position = CGPoint(x: self.size.width / 2, y: (self.size.height / 2))
            character.setScale(0.2)
            
            self.addChild(character)
            
            if let idleAnimation = character.animation(named: "idle") {
                character.run(SKAction.repeatForever(idleAnimation))
            }
        }
    }
}

However, only some of the assets are drawn (and animated). Can't figure out why these ones, but not others.

Asset names should be correct, they're the same as in Spine project and JSON file.

Tried also to copy images from "1x" to "2x" and "3x" also with no help.

What might be the problem? And how could I debug this kind of problems?

[maxgribov]

Try to start by following step by step on this guide:
https://github.com/maxgribov/Spine/wiki/Assets

[lardois]

Hi, have read the guide very carefully, but can't still see what is wrong here.

[maxgribov]

are namespaces enabled for the folder Owl and atlas default?

[lardois]

Yes they are, as noted...
Could it be because of some missing feature in example file? There are some "mesh" keys in JSON file...

[maxgribov]

By the way, if you used meshes in the Spine App that could be a problem there. Meshes are currently not supported by library and I do not know to whom effect they can lead.

[lardois]

Yeah, it seems it was because of the mesh feature.
Noticed now that Spine examples that have "pro" extension use pro features, such as Mesh. the ones with "ess" in file name are done with some "lite" feature set and these examples work fine.

[maxgribov]

Yup... Sorry but I still can't find the time to implement mesh support...