Antidamage I was not trying to be rude, I was trying to be concise because it's a difficult thing to communicate in text.
Sorry for the misunderstanding then. 🙂
Please in general don't try to be concise when asking on the forum, chances are that you leave out important information which might help resolve your issue. Instead it helps a lot to describe what problem you encounted by taking which steps, in as much detail as possible. The problem with trying to be concise is that one would need to be an expert on the topic already to know what to omit. You posted the detailed information after your initial postings, which was great and then provided the necessary information.
It's not helpful to assume rudeness when most people simply aren't going to be rude in that context, especially when they're looking for help.
Since you have now pointed out that you didn't intend rudeness, perhaps it was already helpful. 🙂
Having to cope with a problem and then not receiving a helpful reply can lead to frustration easily, which is understandable. Thus it might help to either get back into a more calm state, or to check if one's wording is not the best yet or could be misunderstood. And please don't get me wrong, I am not saying that you were frustrated and thus rude, I just point it out in case it could have been. 🙂
I'm coming from UE so my assumption was that the json skeleton was the main file to import, and the rest would be imported with it if they were named correctly. I don't know a lot about unity so I don't always know the right questions to ask.
If you're new to Unity, we highly recommend getting familiar with Unity itself and the general workflows first. Otherwise it may lead to a lot of frustration.
For example, Project - Import New Asset
is something that we would recommend to not use when working in Unity. Any assets inside the Assets
or Packages
directories are imported automatically by Unity. Any assets outside the project's Assets
(or Packages
) directory are not visible to Unity, so things can't be found there.
Once you're more familiar with Unity, be sure to check out the example scenes that come with the spine-unity runtime, see:
https://esotericsoftware.com/spine-unity#Example-Scenes
So for instance is it better to keep source assets in the project structure before importing them, or is it better to keep them outside of the project structure until they're imported?
There is no such thing as "importing from within the project structure", if by project struction you mean the Unity project. Anything placed in any subdirectory within Assets
is imported automatically. There is no manual import. You can just re-import a folder inside Assets
a second time. Perhaps this misunderstanding might have been the cause of your problems.
If by project structure you mean from a subdirectory of your Spine project, outside of the Unity project, then it does not really matter, it's up to you. You just need to make sure to copy all exported skeleton asset files over into the Unity project after they have been exported. We don't recommend exporting the assets directly from Spine into a Unity Assets
subfolder. In general we recommend automating the export process using the Spine command line interface, then you can export and copy the files over using a single shell script, and also re-export all your assets at once if you should later upgrade the Spine version from e.g. 4.1 to 4.2.