First try `spine
help` (case doesn't matter on windows), you'll get:
Spine Launcher 3.8.82
Esoteric Software LLC (C) 2013-2020 | http://esotericsoftware.com
Usage:
Editor: Spine [-hfkltv] [-x <host:port>] [-u <version>] [<path>]
Export: Spine [-i <path>] [-m] [-o <path>] -e <path>
Import: Spine -i <path> [-s <scale>] -o <path> -r [<name>]
Clean up: Spine -i <path> -m
Pack: Spine -i <path> [-j <path>]... -o <path> -p <name>
Spine -i <path> [-j <path>]... -o <path> [-n <name>] -p <path>
Info: Spine -i <path>
Editor:
-h,
---
help Print this help message and exit.
-f,
---
force Force download of the Spine update.
-k,
---
keys Enable hotkey popups by default.
-l,
---
logout Logout, removing activation code.
-t,
---
notimeout Disable timeout when checking for and downloading updates.
-v,
---
version Print version information and exit.
-x,
---
proxy Proxy server to use when checking for and downloading updates.
-u,
---
update The version number of the Spine update to load.
project.spine Path to a Spine project file to open.
Export JSON, binary, images, or video:
-i,
---
input Path to a folder, project, or data file. Overrides export JSON.
-m,
---
clean Animation clean up is performed before export.
-o,
---
output Path to write export file(s). Overrides export JSON.
-e,
---
export Path to export settings JSON file.
Import JSON, binary, or a project's skeletons into another project:
-i,
---
input Path to a folder, project, or data file to be imported.
-o,
---
output Path to project file to import into. Created if nonexistent.
-s,
---
scale Scale the project being imported.
-r,
---
import Perform a skeleton import. The skeleton name may be omitted.
Animation clean up:
-i,
---
input Path to project file or folder.
-m,
---
clean Animation clean up is performed and the project is saved.
Texture atlas packing:
-i,
---
input Path to folder of images to be packed.
-o,
---
output Path to write texture atlas and PNG files.
-j,
---
project Path to a project to determine which images are used by meshes.
-n,
---
name Texture atlas name, the prefix for the atlas and PNG files.
-p,
---
pack Texture atlas name or path to pack settings JSON file.
Texture atlas unpacking:
-i,
---
input Path to folder of atlas images.
-o,
---
output Path to write unpacked image files.
-c,
---
unpack Path to texture atlas file.
Project information:
-i,
---
input Path to project or data file.
Examples:
Spine
---
export /path/to/export.json
Spine
---
export "/path/with spaces/to/export.json"
Spine
---
input /path/to/project.spine
---
output /path/to/output/
---
export /path/to/export.json
Spine -i /path/to/project.spine -o /path/to/output/ -e /path/to/export.json
Spine -e /path/to/export1.json -e /path/to/export2.json
Spine -i /path/to/images/ -o /path/to/output/
---
pack /path/to/pack.json
Spine -i /path/to/images/ -o /path/to/output/ -n name -p /path/to/pack.json
Spine -i /path/to/project1.spine -o /path/to/output/ -e /path/to/export1.json
-i /path/to/project2.spine -e /path/to/export2.json -i /path/to/images/
-o /path/to/output/ -p /path/to/pack.json
Spine -i /path/to/skeleton.json -o /path/to/project.spine -r skeletonName
The command you showed only specifies -i
, which is this from the help above:
Info: Spine -i <path>
Where -i
is:
-i,
---
input Path to project or data file.
The path you passed is a folder though, not a project or data file. That is why you got Error loading project: ./Input
. We'll make the error message better when it needs a file but a folder is specified.
To do texture packing, see the texture packing example at the top of the help and the texture packing section lower down:
Pack: Spine -i <path> [-j <path>]... -o <path> -p <name>
Spine -i <path> [-j <path>]... -o <path> [-n <name>] -p <path>
...
Texture atlas packing:
-i,
---
input Path to folder of images to be packed.
-o,
---
output Path to write texture atlas and PNG files.
-j,
---
project Path to a project to determine which images are used by meshes.
-n,
---
name Texture atlas name, the prefix for the atlas and PNG files.
-p,
---
pack Texture atlas name or path to pack settings JSON file.
There are also some examples at the end of the help, but it may be hard to see at first which are doing texture packing. These are:
Spine -i /path/to/images/ -o /path/to/output/
---
pack /path/to/pack.json
Spine -i /path/to/images/ -o /path/to/output/ -n name -p /path/to/pack.json
You've got the input and output folders, no problem. The pack.json
is a JSON file saved from the Spine editor UI (or written by hand). The specification for the texture packer settings JSON file is here:
Texture Packing - Spine User Guide: JSON Configuration
You can read more about using the texture packer from the command line here:
Export - Spine User Guide: Texture packing
Please let us know how it goes!