It would be nice to actually finish a program that actually works with transferring animation data to Unity besides just sprite sheets, without all of these errors. I don't see a point in spending all this time working on more features within Spriter when the only place we can actually use them is in Spriter. I've had this program for a whole year and have been unable to properly transfer this stuff to Unity or any other program unless I only did Sprite Sheets. Yea, the plugin KIND of transfers animation data, but it gives me tons of errors, gets shit wrong, and it's basically impossible to work with. The latest update to the plugin, and the old one I have, do not work with Unity 5 at all right now. It keeps giving me this error called "Unknown character n" or something and doesn't attempt to make a prefab, not even a broken one, just nothing happens.
We agree about Spriter support in general being the top priority, and as RunnerPack mentioned, this has been our focus for the past several months. Instead on focusing on Spriter support for any specific authoring system (and showing "unfair" favoritism ), our first logical step is a fully featured "generic" Spriter implementation which is as powerful and flexible as possible, and also being carefully constructed so the addition of known future features will be as painless as possible, without the need of drastic re-writes and re-porting the implementation once the new features are added. This is indeed taking longer than we would like, but we're working on it as diligently as possible and apologize humbly for the long wait. I also completely sympathize with your frustration and patience wearing thin.
As for Spriter2Unity specifically, reporting the errors you're facing as clearly as possible in the appropriate thread, and to the attention of the actual developers would likely be much more fruitful. I suggest you first, make sure you're using the latest of everything (Spriter, Spriter2Unity, and Unity). Then get your error list, and report everything as clearly as possible. It's also very important to know that Spriter2Unity does not yet support several of the more advanced Spriter features, so learning what it does not support and learning to at least for now create your animation while avoiding the unsupported features will allow you to work without issues.
Starting a thread specifically to list the known unsupported features would be useful to everyone and might even help encourage current and future developers to get those features supported all the sooner.
That all aside, once our generic reference implementation is finished, our next focus will be on helping with specific implementations, and the order in which we'll be able to help ensure full support for any particular authoring system will depend predominantly on two factors: a) the level of collaboration from the developers/community of each given authoring system and b ) The general popularity of that particular authoring system.
Long story short, Edgar is focusing his full time and attention (as much as possible) to creating the best, most flexible, thorough, and future proof Spriter implementation which should make porting full Spriter support to any authoring system fast and painless once its finished, and, as soon as it is finished well focus as much of our time and resources as we can to helping to port this new, full implementation to as many authoring systems as possible, including of course Unity, which is both very popular and has a great community who have continually donated their valuable time and expertise to supporting Spriter.
