Spine.com -i C:\Bird.skel -o C:\Bird.spine -r
What version are you running with this? It's best to specify a version. You'll need to specify the exact version the
.skel file was exported with. Eg if that was
Spine.com -u 3.6.53 -i C:\Bird.skel -o C:\Bird.spine -r
If that opens the editor UI instead of creating the
C:\Bird.spine then it means the launcher validated the parameters for the latest Spine, but the
3.6.53 editor is too old to accept the parameters. I'm afraid you'll have to do the binary data import using the editor UI, sorry! Once you have saved
.spine files for each of your
.skel files you can use the command line to do the exports using 3.8 (or any version).
If I instead do
Spine.com -u 3.8.95 -i C:\Bird.skel -o C:\Bird.spine -r
it creates the output .spine file, but the original binary file is exported using 3.6. That output .spine file can not load the skeleton data in the 3.8.95 editor.
I would expect that to fail, as 3.8.95 is very unlikely to be able to read binary data from 3.6.xx. Do you mean it creates a
C:\Bird.spine that won't open in the 3.8.95 editor? If so, that sounds like a bug.