Sorwidir wrote

So the reason the Skeleton Viewer can see my characters is because it has support to view binary files (.skel)?

Yep!

Sorwidir wrote

And once I buy the license, you recommend me to import the characters then export with 4.0?

Yes, then you can 1) use the 4.0 web player, and 2) edit your skeletons in the Spine editor, if you unpack the atlases.

Sorwidir wrote

But if I remember correctly, Misaki had to export the atlas, wont I have to manually assign textures to every part of the character?

There is no manually assigning textures in Spine. Spine uses naming conventions to find image files:
Images - Spine User Guide: Image file lookup

You need individual image files for the Spine editor to show your images. If all you have is an atlas, you need to unpack it:
Texture packing - Spine User Guide: Texture Unpacker

Sorwidir wrote

So with over 100 characters, it will take a long time? Or is this process also possible to "automate" with this CLI you speak of?

You can write scripts to do the steps. For example:

spine -u 3.7.94 -i old-data.skel -o new-project.spine 

---

import
spine -u 4.0.xx -i new-project.spine -o path/to/output/folder 

---

export binary

This runs 3.7.94, imports a binary file and saves a project file. Then it runs the latest 4.0 and exports the project file, giving you a binary file for each skeleton in the project.

You can also unpack an atlas:

spine -i path/to/atlas/images -o path/to/output/folder 

---

unpack path/to/your-atlas.atlas

Sorwidir wrote

I will buy a license nevertheless! Got the money now, so kinda excited.

Great! Welcome to Spine!

Those are only warnings. Your data was exported without nonessential data, so Spine has to make some guesses when importing it:
Import - Spine User Guide: Nonessential data

I don't see any attachments on your skeleton. Maybe you need to show a skin?

Ah, if your skeletons are using Spine Professional features (like meshes) then they can't be exported with Essential. I didn't know what features your skeletons use, but sorry I didn't consider that possibility earlier.

Though I understand budget is a concern, you can upgrade to Professional any time for the difference in cost from your Spine license page. If you'd prefer a refund that is no problem, in that case please email us: contact@esotericsoftware.com

Sorry!

The Skeleton Viewer source code is here:
https://github.com/EsotericSoftware/spine-runtimes/tree/4.0/spine-libgdx/spine-skeletonviewer
It could be modified to render with a green background, or to write a PNG, but would require programming with Java and libgdx.

Yep, it's normal Java development, though using the libgdx library (which Spine is built with).
https://libgdx.com/

Yep, the refund is for the full amount. You get the full amount back, but we have to pay a fee. For an Essential refund we are charged ~$3.

We lose on a refund. It's OK though, if someone finds out they really don't want Spine, they shouldn't have to pay. We should make a better product so no one wants a refund. In your case, I should have thought to mention that Essential can't export meshes.

Nate wrote

Sorwidir wrote

So the reason the Skeleton Viewer can see my characters is because it has support to view binary files (.skel)?

Yep!

Sorwidir wrote

And once I buy the license, you recommend me to import the characters then export with 4.0?

Yes, then you can 1) use the 4.0 web player, and 2) edit your skeletons in the Spine editor, if you unpack the atlases.

Sorwidir wrote

But if I remember correctly, Misaki had to export the atlas, wont I have to manually assign textures to every part of the character?

There is no manually assigning textures in Spine. Spine uses naming conventions to find image files:
Images - Spine User Guide: Image file lookup

You need individual image files for the Spine editor to show your images. If all you have is an atlas, you need to unpack it:
Texture packing - Spine User Guide: Texture Unpacker

Sorwidir wrote

So with over 100 characters, it will take a long time? Or is this process also possible to "automate" with this CLI you speak of?

You can write scripts to do the steps. For example:

spine -u 3.7.94 -i old-data.skel -o new-project.spine 

---

import
spine -u 4.0.xx -i new-project.spine -o path/to/output/folder 

---

export binary

This runs 3.7.94, imports a binary file and saves a project file. Then it runs the latest 4.0 and exports the project file, giving you a binary file for each skeleton in the project.

You can also unpack an atlas:

spine -i path/to/atlas/images -o path/to/output/folder 

---

unpack path/to/your-atlas.atlas

Sorwidir wrote

I will buy a license nevertheless! Got the money now, so kinda excited.

Great! Welcome to Spine!

borrowing this thread hope its ok

spine -u 3.7.94 -i old-data.skel -o new-project.spine

import

how to support batch?

spine -u 3.7.94 -i *.skel -o what to type here?.spine

import eg
spine -u 3.7.94 -i *.skel -o new-project.spine

import <

will not work because it will keep overwriting project.spine

maybe *.skel wont work either, how to use this for batch files?

xSaber, better to use your own topic:
Batch conversion