• Editor

  • Spine 3.6 is now available!

    الإنجليزية

  • msm

    • منشور رقم 13
    • هذا المنشور باللغة الإنجليزية

    congrats, looks awesome.

    Impressed as always at the features you are packing into Spine.

    I'd just like to say that all the editor updates are awesome of course, but I appreciate the attention you also are giving to improving the runtimes and the repos. Your previous move to keeping the runtimes in pace with latest editor release features was huge, and now moving to versioned branches for the repo is another big improvement. So thanks for the awesome work.

    Any thoughts on separating the individual runtimes into their own git repos? For one, reading the commit history would be a lot more useful, as it would not be interspersed with other platforms I'm not using. Would also make importing just what I need as a git submodule for example a lot easier.

    Thanks again

    Related Discussions
    ...

    • Mario

    • منشور رقم 14
    • هذا المنشور باللغة الإنجليزية

    I'm considering moving the runtimes to individual git repositories and making them submodules of the main repository. It's a bit complex to unwind the example projects, but it's on my "will look into this option asap". FWIW, every runtimes specific commit is prefixed with [runtimename] so you can filter the logs more easily.

    • Nate

    • منشور رقم 15
    • هذا المنشور باللغة الإنجليزية

    We discussed it a bit here:
    Separate repos · #758
    Submodules would be convenient for users to pull in the Spine Runtimes, but quite inconvenient for runtime development. Git submodules are a bit of a half-baked Git feature (look, a haiku. uhhh I hate mornings). I would much rather Git implements a better solution to the problem of pulling in part of a repo without causing the repo maintainers grief.

    • Eeldridge

      • منشور رقم 16
      • هذا المنشور باللغة الإنجليزية

      Hi I am new to the forum and have been using Spine for just a few months.

      I just updated my Software today and started working on a file i made from the previous version. it worked but after saving the file and closing the program, when I started it up again, I am getting this error message.

      "Sorry, an error occurred while reading the project file.

      project version: 3.6.34
      spine version: 3.6.34"

      help... i am running late on deadlines and this update has set me behind T_T

      • Erika

      • منشور رقم 17
      • هذا المنشور باللغة الإنجليزية

      What was the previous version you were using? Spine saves backups every 15 minutes in the backup folder so if you're lucky you might find a very old version, try matching the editor with that version by downgrading it, and then go on working.

      • Nate

      • منشور رقم 18
      • هذا المنشور باللغة الإنجليزية

      eldridge, can you please email us the .spine file you aren't able to open? contact@esotericsoftware.com

      4 أيام لاحقا

      • tuanhm107

        • منشور رقم 19
        • هذا المنشور باللغة الإنجليزية

        Great update! If only the clipping mask has a feather option tho 😃

        • Mmayhemking

          • منشور رقم 20
          • هذا المنشور باللغة الإنجليزية

          I definitely need a tutorial on painting weights...

          Help solve the problem, after updating Unity when selecting any object of Spine2D, here comes this error https://pastebin.com/FThuMEFW

          Unity 5.6.f21
          Last installed spine-unity-3_6-2017-06-26 Compatible with Spine 3.6.x and Unity 5.6-2017.1

          NullReferenceException: Object reference not set to an instance of an object
UnityEditor.PropertyHandler.OnGUILayout (UnityEditor.SerializedProperty property, UnityEngine.GUIContent label, Boolean includeChildren, UnityEngine.GUILayoutOption[] options) (at /Users/builduser/buildslave/unity/build/Editor/Mono/ScriptAttributeGUI/PropertyHandler.cs:198)
UnityEditor.EditorGUILayout.PropertyField (UnityEditor.SerializedProperty property, UnityEngine.GUIContent label, Boolean includeChildren, UnityEngine.GUILayoutOption[] options) (at /Users/builduser/buildslave/unity/build/Editor/Mono/EditorGUI.cs:7569)
UnityEditor.EditorGUILayout.PropertyField (UnityEditor.SerializedProperty property, Boolean includeChildren, UnityEngine.GUILayoutOption[] options) (at /Users/builduser/buildslave/unity/build/Editor/Mono/EditorGUI.cs:7563)
Spine.Unity.Editor.SkeletonAnimatorInspector.DrawInspectorGUI (Boolean multi) (at Assets/Spine/spine-unity/Editor/SkeletonAnimatorInspector.cs:48)
Spine.Unity.Editor.SkeletonRendererInspector.OnInspectorGUI () (at Assets/Spine/spine-unity/Editor/SkeletonRendererInspector.cs:385)
UnityEditor.InspectorWindow.DrawEditor (UnityEditor.Editor editor, Int32 editorIndex, Boolean rebuildOptimizedGUIBlock, System.Boolean& showImportedObjectBarNext, UnityEngine.Rect& importedObjectBarRect) (at /Users/builduser/buildslave/unity/build/Editor/Mono/Inspector/InspectorWindow.cs:1229)
UnityEditor.DockArea:OnGUI()

          • Pharan

            • منشور رقم 22
            • هذا المنشور باللغة الإنجليزية

            @Dmitriy Makeyev That's the same issue here! Spine 3.36 Error??
            Should be fixed on the current one.

            4 أشهر لاحقا

            Hi, getting these warnings and errors after importing into an empty 2017.2.0f3 project:

            build: http://esotericsoftware.com/files/runtimes/unity/spine-unity-3_6-2017-10-16.unitypackage

            Script 'Animation' has the same name as built-in Unity component.
            AddComponent and GetComponent will not work with this script.

            Assets/Spine/spine-unity/Editor/SpineEditorUtilities.cs(233,22): warning CS0618: UnityEditor.EditorApplication.playmodeStateChanged' is obsolete:Use EditorApplication.playModeStateChanged and/or EditorApplication.pauseStateChanged'

            Assets/Spine/spine-unity/Editor/SpineEditorUtilities.cs(233,22): warning CS0618: UnityEditor.EditorApplication.playmodeStateChanged' is obsolete:Use EditorApplication.playModeStateChanged and/or EditorApplication.pauseStateChanged'

            Assets/Spine/spine-unity/Editor/SpineEditorUtilities.cs(234,22): warning CS0618: UnityEditor.EditorApplication.playmodeStateChanged' is obsolete:Use EditorApplication.playModeStateChanged and/or EditorApplication.pauseStateChanged'

            Assets/Spine/spine-unity/Editor/SpineEditorUtilities.cs(234,22): warning CS0618: UnityEditor.EditorApplication.playmodeStateChanged' is obsolete:Use EditorApplication.playModeStateChanged and/or EditorApplication.pauseStateChanged'

            Use of UNITY_MATRIX_MV is detected. To transform a vertex into view space, consider using UnityObjectToViewPos for better performance. - SpineVertexLighting.cginc

            Shader error in 'Spine-SkeletonGraphic-TintBlack': undeclared identifier 'i' at line 113 (on d3d11)

            • Pharan

              • منشور رقم 24
              • هذا المنشور باللغة الإنجليزية

              That should be fixed now. Latest unitypackage dated today.
              The first warning is harmless. But Unity Tech said they won't remove it.

              Thanks 🙂

              3 أشهر لاحقا

              • Ddannyjones

                • منشور رقم 26
                • هذا المنشور باللغة الإنجليزية

                Thanks for this information...
                🙂

                4 أشهر لاحقا

                • GgOzaru30

                  • منشور رقم 27
                  • هذا المنشور باللغة الإنجليزية

                  Does branching no longer necessary in this version?

                  • Nate

                  • منشور رقم 28
                  • هذا المنشور باللغة الإنجليزية

                  Not sure what you mean? On GitHub there is currently a 3.6 branch and a 3.7-beta branch.

                  • GgOzaru30

                    • منشور رقم 29
                    • هذا المنشور باللغة الإنجليزية

                    I meant branching mesh in Spine Editor. Re-branching the mesh to all points after we add in middle one, I meant.
                    The yellow lines in picture. Do we have to do it manually or it's automatically now?

                    • Nate

                    • منشور رقم 30
                    • هذا المنشور باللغة الإنجليزية

                    You always need to create the orange edge lines manually, but they are optional. You only need the orange lines when the gray lines that Spine creates automatically are not sufficient for your needs. In other words, the orange lines allow you to control how Spine performs triangulation. Please see the Edges documentation here:
                    Meshes - Spine User Guide: Edges

                    Some people go crazy and add a bunch of orange lines to their mesh simply because they like how it looks (looking at you, Shiu). However, if you create an orange line over a gray line, the resulting mesh is exactly the same. Well not exactly, the orange lines may make it easier for you to select parts of your mesh, especially if you hold down shift when clicking an edge (for edge loop selection).

                    • GgOzaru30

                      • منشور رقم 31
                      • هذا المنشور باللغة الإنجليزية

                      Weird, the orange lines doesn't show in my editor. Just update it to 3.6.52.

                      • Nate

                      • منشور رقم 32
                      • هذا المنشور باللغة الإنجليزية

                      Did you click a mesh, then the Edit Mesh button, then the Create tool, then drag starting from a mesh vertex?