Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Load Export Settings

BinaryCats

In my opinion it makes sense for export setting files to be saved in the same directory where the .spine file is stored. Not the export directory.

Currently if you select save or load the save/load popup window will open at the export directory. We directories/repos, as I suspect most people do, for art and game. and export settings - in my opinion, would belong in the art.

It gets even more annoying with the bug which means the export directory doesn't save correctly, so i wanted to make an export setting file, so i didn't need to manually find the correct directory. Opening in the export directory, for me, makes export settings usless 🙁

Nate

What bug?

BinaryCats

uh, spine forgets where the spine file was last exported to. we don't know the repo. maybe because I export them to a directory, but my colleague exports them to another directory which I don't have (vice vera).

So, I export to
Me:
Spine File1:

export to:
C:foo/bar/exports
Commit.

Him:
Spine File1:

Pull
export to:
C:foobar/exports.
commits,

me:
Pull

Spine File2.
Export to
c:foo/bar/export/cats

SpineFile1:
C:foo/bar/cats - is now the default location for the export for spine file1

Spine File2:

Nate

Ah, thanks. Paths are stored in the project. If a path hasn't been set or doesn't exist, it falls back to other, related paths stored in the project, and then finally it falls back to paths stored in your Spine settings. We'll be improving the dialog for choosing a file or directory, so hopefully that will help.

As for the export settings, we'll look at more reasonable defaults.