• Bugs
  • Animation will export with folder names

  • Изменено
Related Discussions
...

When I export my animation that is organized into separate folders in Spine, the animation will export with the parent folder name in the animation asset name. For example in Spine: Animation folder name: WalkAnimFwd . Animation asset name in folder: WalkFwd_Start. Exported name: WalkAnimFwd_WalkFwd_Start (desired name is just WalkFwd_Start). Is this the intended behavior or is there a setting I can edit to turn this off? The work around is to ungroup all of the animation on export to get the proper name but it's not an ideal workflow.

Repro:

  • Open Spine and group an animation in a folder
  • Name folder and animation differently so you can see results better
  • Export the animation and look at exported files name

Software: 3.8.93

It is the expected behavior: at runtime the animation name includes all parent folders. The animation name needs to be unique per skeleton. abc/name and xyz/name would not be unique if the folder path was omitted. Typically the naming isn't a problem at runtime, even if it is a bit long. Why is it problematic for you? Maybe you can name your animations to not repeat the folder name, eg WalkAnimFwd/Start?

Hey Nate!

I keep all of my animation names unique due the the volume of them and the different characters I have that use the same skeleton (unless I'm miss understanding what you are saying). So me using folders is just and organization way to keep my tree clean so I know what animation set I'm working on and the folder name may not be the name I want to be a prefix of the animation when I import into Unity. Which is my current issue and that's why I unparent all of my animation from their folders before exporting. I can keep doing this as my personal work around but I wanted to know if this was the intentional behavior.

Though I see now where there may be a cross roads, the reason why renaming is a bit of a pain is because we use Perforce as a file manager across the project. So renaming this is possible but it includes a couple more steps typically to make sure the files are submitted safe. This can be a pain at times but it is doable.

Spine currently allows animations (and skins and events) with the same name, but different folders. If a user does that (I understand you don't), then if we had a setting to export without the folders in the names, then they'd end up with duplicate names and that would break things.

Ideally you would just use the folder names as part of the animation name. Even WalkAnimFwd/WalkFwd_Start isn't really a problem. Is your issue that you've been using WalkFwd_Start in the code since before Spine had folders? I'd think it should not be a big problem to change the names you use at runtime.