What is the best approach if you for example have 10-20 animations? One fbx with all of them or separate into multiple fbx files? It just feels that 1 huge animation is not optimal compared to many separate files. It will only load the ones needed.
Any thoughts around this? I don’t see a good tutorial on importing separate animations. I saw on a youtube clip somewhere about naming them to @walk @run etc or some such
Thanks!
Both methods create separate animation clips so it’s really just up to your personal preference in work flow. Here’s the doc page for importing animations with the “split” or “@” method:
I would say to choose the method that fits your pipeline best. Do you prefer exporting a single FBX to Unity and then manually splitting and defining all the animations within the Unity editor (very tedious task if you have more than 10 animations per character, which is usually the case). Or, do you prefer or find it faster to export multiple FBX files each with an animation from your 3D app, and simply use the @ naming convention in Unity?
You should experiment with each and find one method that suits your production needs the best. No right or wrong way here, just preference. I have used both methods, and depending on the project, I’ll usually go with one or another based on what I’m working on at the moment.
Ok, but you say unity splits them up so there is really no performance issue because in the end we end up with same thing. So back to choosing workflow. Thanks for clearing it out for me