• RuntimesUnity

  • Error when texture repacking for mix and match using image sequences.

    inglés

  • FFry

    • Publicación n.º 1
    • Publicación en inglés

    Our project was recently converted from 4.0 to 4.1 and we've started using the sequence properties on timelines we are encountering a "Region is Null" error for any skin that uses it. Our programmer determined that the issue occurs when texture repacking with mix and match. We are using the latest 4.1 runtimes in our project.

    Attached are some comments/screencaps as well as the mix and match setup from the programmer. Any help would be appreciated as this feature was part of the incentive to upgrade from 4.0 to 4.1.




    Thanks!

    Related Discussions
    ...

    @Fry We can't debug your code by looking at screenshots. Could you please send us a minimal Unity project which still shows this issue? You can send it as a zip package to contact@esotericsoftware.com, briefly mentioning this forum thread URL so that we know the context.

    • Fry respondió a esto

      • FFry

        • Publicación n.º 3
        • Publicación en inglés

        Harald

        Thank you! The programmer is preparing that and I'll email it early next week with a link to this thread.

          @Fry Thanks for sending the reproduction package! I just noticed that the necessary bugfix that allows repacking of sequence attachments was only published to the 4.2-beta branch, since it contains risky changes that might break existing 4.1 projects.
          See the issue ticket here:
          EsotericSoftware/spine-runtimes2268

          To integrate the changes to your 4.1 project, you would need to apply the bugfix commit manually to your spine-unity runtime's AtlasUtilities.cs file:
          EsotericSoftware/spine-runtimese10b37a
          Since you're using Add package from git URL to add the spine-unity package, you would need to instead download the package, modify it accordingly and add the package via Add package from disk.
          Sorry for the inconvenience!

          @Fry Actually you don't need to integrate the commit manually, you can simply use the complete AtlasUtilities.cs file content from the 4.2-beta branch as-is, since no other changes were made (only license headers updated).

          So you can just copy the file content from here:
          EsotericSoftware/spine-runtimesblob/4.2-beta/spine-unity/Assets/Spine/Runtime/spine-unity/Utility/AtlasUtilities.cs

          @Fry We have pushed another bugfix for the issue to the 4.2-beta branch.
          EsotericSoftware/spine-runtimes2268
          A new spine-unity 4.2 unitypackage is available for download.
          https://esotericsoftware.com/spine-unity-download
          In your case, you might again want to copy the contents of the AtlasUtilities.cs file over as described in the previous post above.

          Just a remark regarding your reproduction project: You have placed the spine-unity UPM package inside the Assets/ directory and then added the package via the Unity Package Manager from this subdirectory. This is not recommended, you should instead move the UPM package outside of Assets (e.g. <projectdir>/Modules) when added via the package manager. Also, having a subdir Assets/Assets is not recommended and might perhaps cause problems.

          • Fry respondió a esto

            • FFry

              • Publicación n.º 7
              • Publicación en inglés

              Harald

              Thank you!