PixelBrothers

Hi PixelBrothers,
 
I recommend you send the actual Spriter project to the developer of Spriter 2 Unity along with a bug report via his Github page: https://github.com/bonus2113/Spriter2Unity
 
thanks,
Mike at BrashMonkey

Hi friends,
I recently discovered the Spriter :-P  software (used Spine until)...I need Spriter to making animations for Unity (v 4.6.1f), planning to buy the Spiter PRO version but I have some issues :???:  and I'm wondering if are there solutions for this problems:
First of all for some animations when are imported I get this :???:  error:
Quaternion To Matrix conversion failed because input Quaternion is invalid {-1.#IND00, -1.#IND00, -1.#IND00, -1.#IND00} l=-1.#IND00UnityEditor.AnimationUtility:GetCurveBindings(AnimationClip)UnityEditorInternal.AnimationWindowState:get_allCurves() (at C:/buildslave/unity/build/Editor/Mono/Animation/AnimationWindow/AnimationWindowState.cs:237)UnityEditorInternal.AnimationWindowHierarchyDataSource:FetchData() (at C:/buildslave/unity/build/Editor/Mono/Animation/AnimationWindow/AnimationWindowHierarchyDataSource.cs:43)UnityEditor.TreeView:ReloadData()UnityEditorInternal.AnimationWindowHierarchyDataSource:UpdateData() (at C:/buildslave/unity/build/Editor/Mono/Animation/AnimationWindow/AnimationWindowHierarchyDataSource.cs:146)UnityEditorInternal.AnimationWindowState:Refresh() (at C:/buildslave/unity/build/Editor/Mono/Animation/AnimationWindow/AnimationWindowState.cs:525)UnityEditorInternal.AnimationWindowState:OnGUI() (at C:/buildslave/unity/build/Editor/Mono/Animation/AnimationWindow/AnimationWindowState.cs:70)UnityEditor.DockArea:OnGUI() ...this error generates strange behavior for this particular animation, video example: View My Video
Please help me as soon as possible...Thanks in advance !

I know what it's like to want to keep a code-base to oneself until it's "finished", but, since you're planning on opening the source, anyway, it would be cool if Edgar would post it to, e.g. github. Besides the many benefits of keeping your code in a git repo, you'd also enable the community to help catch bugs, which could be reported directly through github itself. It could even be forked, to allow the community to help squash said bugs, as well as generally contribute to the code, resulting in faster, parallel development both of the main, "generic" branch, and of specific branches for other languages/environments. You could even use the github Wiki feature to post the documentation, which could then be collaboratively developed, as well. One of the best results, though, would be the motivating factor of not having to "go it alone".
 
(Now, everybody "like" this post and reply to show the BrashMonkey guys that you think it's a good idea! ;))