• Editor

  • Strange Imports

    英語

Hello there

a little uncertain if this will be kosher, but I didn't see any rules for the forum, so I figured I'd post here and see what happens. If I get a slap on the wrist, oh, well.

I recently purchased a Spine Essentials License, and for the sake of teaching myself, I've been going through some files from various games (which I won't name) in order to give myself my own tutorial, I suppose. Unfortunately for me, one of those games has meshes, so I can't fully view it, but the parts that I can view are...strangely sized.

The main issue I'm curious about this is that the files can be viewed fine in the Spine Viewer jar; everything scales properly. But all of the textures that are non-meshed are shrunk when opened in the editor. I was wondering if anyone had any experience with this, or potentially knew why this could happen. But if this is skirting too close to being illegal, feel free to delete this thread, etc. etc.

Related Discussions
...

  • Nate

  • 投稿 #3
  • この投稿は英語で投稿されました

Probably the texture atlas was exported scaled down. When you unpack the atlas, you get smaller images that the original project used in Spine. When the JSON or binary was exported, it is exported as it was in Spine. At runtime you can specify a scale when loading the data so it matches the scaled down (or up) texture atlas.

When you import the data into Spine you can specify a scale. It may take some trial and error to find the same scale used to create the atlas. It is likely a number like 0.5, 0.66, 0.75, but could be anything.

Messing with the scaling did the trick

I think I wasn't quite understanding how sizing worked, but, thanks for the tip! Still a little sad about the meshes, but, hey, that's how the cookie crumbles.

(For anyone who stumbles upon this thread, if the images are too spaced out, turn the scaling down, and if they're too close together, turn the scaling up. I was confused because I thought it was going to be the other way around.)