• Editor
  • Problems with exoprt settings in the last Spine update

I'm not sure which forum fits my question, so I'm publishing it here.

I updated to 3.6.15 and realized that now every time I want to export I need to choose the destination folder. In the previous version it sets automatically to the same folder where the source file placed and this variant was very useful because I have dozens of folders in my project. Is there any possibility to restore previous settings?

Related Discussions
...
  • Đã chỉnh sửa

I don't see this happening. It remembers the last export directory and uses that for subsequent exports, just like it used to.

Note you should save after exporting so the export directory is saved in the project file. I guess we should mark the project as modified when you export to a new directory.

But it's not comfortable. Which scenario will lead me to the situation when you export different animation in the same folder? It would just owerwrite export files.

The previous version of Spine didn't remember the last export directory and it was a good decision.

The routine process: I have 100 folders with Spine-files inside each one. I want to export all these animation, 1st animation to 1st folder, 2nd to 2nd etc. Because it's easy to find them and import to my development tool after.
Before 3.6.15 I just pressed export and it exported into appropriate folder. It was so useful.
Now I have to choose the folder every time. It's just wasting of time.


If you will add checkbox "export to the source folder" or something like that it would save so much time for your users.

It helps to separate 1) what you doing, 2) what you actually see, 3) what you expected to see, and 4) what you suggest to fix it. When these are combined, it is harder to help.

krutovig đã viết

The previous version of Spine didn't remember the last export directory and it was a good decision.

Spine has always remembered the export folders. It works exactly as it used to, it's just that we had to change how the paths are stored, which means your old export paths got discarded. I guess this is the true source of the problem. We'll look at what we can do to keep your old paths, at least the directory paths. Anyway, after exporting, the path is stored in the project, but you need to save the project so the project file gets updated with the new path. So, take these steps: set export path, export, save project. Now you can: close Spine, open Spine, open project, export, and it will use the same path you used last time for that project.

In 3.6.16-beta we set the "dirty" flag, so you will be prompted to save the project if you've exported to a different directory (or taken other actions that store paths in the project, like texture packing).

If you really have many Spine projects, I suggest using the CLI interface to perform exports:
Export - Spine User Guide: Command line
Here's an example export script:
spine-runtimes/export.sh at master
If needed, we can help you here on the forum to write your own script, depending on what OS you are using.

Thanks for promising of adding "dirty flag".

To be clear, I will try to specify with separate paragraphs.

1) what you doing
I have around 100 animations in 100 separate Spine files which are in 100 separate folders. Like "animation1", "animation2" ... "animation100". I export these 100 animations in such way when export files of animation1 are in animation1 folder, export files of animation2 are in animation2 folder etc. Then I go to Unity and integrate them into the game from these folders.

2) what you actually see
I export animation1 to animation1 folder. Then I open animation2, press export and Spine exports it in the previous folder (animation1) by default which overwrites animation1 files. Every time I must choose the correct folder.

3) what you expected to see
I export animation1 to animation1 folder. Then I open animation2, press export and Spine exports animation2 in the animation2 folder etc.

According to your words that Spine has always remembered the last export folder, I don't know how it's possible but I hadn't this issue before 3.5.15

4) what you suggest to fix it.
I inquire to add the flag "export to the source file folder" which will export files into the folder where the opened Spine files is.

I hope my explanation is better this time. Sorry, maybe my English is not perfect.

Thanks! You're making the very good software.

Thanks, I understand now. 🙂

For each project, open the project, export to the desired folder, then save the project. After doing that, the next time you open the project, it will have the path you last exported that project to.


Edit: in 3.6.16-beta we will preserve paths stored in the project file to avoid the problem krutovig was having. Sorry for the trouble!

Hi.
I've updated to 3.6.16 and don't see any changes. Where can I find this option?

When opening a project saved with 3.6.14-beta or earlier, the export dialog in 3.6.15-beta should use the last export path. If you saved your project with 3.6.15-beta then you just need to do an export, then save the project.

Thanks. Looks like it works