यह साइट एक आधुनिक ब्राउज़र में सबसे अच्छी तरह से देखी जा सकती है जिसमें जावास्क्रिप्ट सक्षम है।

Wrong scaled animations when using SkeletonGraphic

Spinebot

It seems like you're encountering issues with scaling and positioning your SkeletonGraphic component within a UI panel in Unity. Based on the provided contexts, here are a few steps and considerations that might help resolve the issue:

Ensure Correct Version Compatibility:
- Make sure that the versions of the Spine Editor and the spine-unity runtime are compatible. You mentioned using Spine Unity Runtime 4.1.42 with Unity 2022.3.14f, which should be fine, but double-checking never hurts.
Initialization and Update Order:
- The order of initialization and updates is crucial. Ensure that Initialize, Update, UpdateMesh, and MatchRectTransformWithBounds are called in the correct sequence. Your code seems correct, but let's ensure no steps are missed.
RectTransform Settings:
- Ensure that the RectTransform settings are correctly applied. Setting anchoredPosition and sizeDelta to zero should center and fit the skeleton within the parent, but double-check the parent’s RectTransform settings as well.
Multiple Canvas Renderers:
- If you are using multiple blend modes, ensure that Multiple CanvasRenderers is enabled in the SkeletonGraphic component's Advanced settings.
FitInParent Mode:
- The FitInParent mode should scale the skeleton to fit within the parent’s bounds. Ensure that the parent’s RectTransform is correctly set up to provide the desired bounds.
Example Code:
- Here is a refined version of your code with additional checks and comments:

var skeleton = AnimationManager.instance.GetSpineSkeleton(unitPrototype.excelId);
if (skeleton != null)
{
    skeletonGraphic.skeletonDataAsset = skeleton;
    skeletonGraphic.startingAnimation = "idle";
    skeletonGraphic.startingLoop = true;
    
    // Initialize the SkeletonGraphic
    skeletonGraphic.Initialize(true);
    
    // Update the SkeletonGraphic to apply changes
    skeletonGraphic.Update(0f);
    skeletonGraphic.UpdateMesh();
    
    // Match RectTransform with bounds
    skeletonGraphic.MatchRectTransformWithBounds();
    
    // Set layout scale mode to FitInParent
    skeletonGraphic.layoutScaleMode = SkeletonGraphic.LayoutMode.FitInParent;
    
    // Center the RectTransform within the parent
    skeletonGraphic.rectTransform.anchoredPosition = Vector2.zero;
    skeletonGraphic.rectTransform.sizeDelta = Vector2.zero;
    
    // Ensure Multiple Canvas Renderers is enabled if using multiple blend modes
    skeletonGraphic.enableMultipleCanvasRenderers = true;
}

Debugging:
- Add debug logs to check the values of RectTransform properties before and after setting them to ensure they are being applied correctly.
- Verify that the SkeletonDataAsset is correctly assigned and initialized.
GIF Analysis:
- From the GIF, it seems like the animation is not fitting correctly within the bounds. Ensure that the parent panel’s RectTransform is correctly sized and positioned.

If the issue persists, consider creating a minimal Unity project that reproduces the problem and testing it in isolation to rule out any project-specific settings or conflicts.

Harald

@Nelvin Sorry to hear you're having troubles! Does your SkeletonGraphic component have Advanced - Multiple CanvasRenderers enabled, and does the issue still occur if you disable this setting?

Nelvin

Harald
Thanks for your fast reply - it's disabled, for the sake of completeness I enabled it, but the result was just an error.

ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
System.Collections.Generic.List`1[T].get_Item (System.Int32 index) (at <a3b02d6f9b494355b946095ea1f25c54>:0)
Spine.Unity.SkeletonGraphic.PrepareRendererGameObjects (Spine.Unity.SkeletonRendererInstruction currentInstructions, System.Boolean isInRebuild) (at ./Library/PackageCache/com.esotericsoftware.spine.spine-unity@879c7adb37/Runtime/spine-unity/Components/SkeletonGraphic.cs:1049)
Spine.Unity.SkeletonGraphic.PrepareInstructionsAndRenderers (System.Boolean isInRebuild) (at ./Library/PackageCache/com.esotericsoftware.spine.spine-unity@879c7adb37/Runtime/spine-unity/Components/SkeletonGraphic.cs:736)
Spine.Unity.SkeletonGraphic.UpdateMesh () (at ./Library/PackageCache/com.esotericsoftware.spine.spine-unity@879c7adb37/Runtime/spine-unity/Components/SkeletonGraphic.cs:743)
ArmyBuildingPopup.SelectUnitToBuy (Unit unitPrototype) (at Assets/Scripts/UI/Menus/Army Management Elements/ArmyBuildingPopup.cs:120)
EventChannels.SelectUnitToBuy (Unit unit) (at Assets/Scripts/SpellSystem/SpellManager.cs:22)
ArmyManagementScreen.ShowBuildingPopup (ArmyBuildingType buildingType, UnityEngine.UI.Image imgLevel1, UnityEngine.UI.Image imgLevel2, UnityEngine.UI.Image imgLevel3) (at Assets/Scripts/UI/Menus/ArmyManagementScreen.cs:981)
ArmyBuildingButton.SelectCategory () (at Assets/Scripts/UI/Menus/Army Management Elements/ArmyBuildingButton.cs:107)
ArmyManagementScreen.Update () (at Assets/Scripts/UI/Menus/ArmyManagementScreen.cs:229)

Harald

@Nelvin Sorry, I noticed that you're setting Multiple CanvasRenderers via code.

I just tested your code, it's indeed a bug with the spine-unity runtime (also present on the 4.2 branch).
A quick fix is to set the layoutScaleMode to LayoutScaleMode.None before the mesh is first updated, as the MatchRectTransformWithBounds method currently takes the scaled mesh after layout scale mode has enlarged it.

I've created an issue ticket here:
EsotericSoftware/spine-runtimes2577
Thanks for reporting!

Until a bugfix is released, the quick-fix code would be as follows:

skeletonGraphic.layoutScaleMode = SkeletonGraphic.LayoutMode.None; // add this line
skeletonGraphic.Initialize(true);

//skeletonGraphic.Update(0f);  // you can remove this call
//skeletonGraphic.UpdateMesh(); // you can remove this call as well
skeletonGraphic.MatchRectTransformWithBounds();

skeletonGraphic.layoutScaleMode = SkeletonGraphic.LayoutMode.FitInParent;

Note that you can remove the calls to Update() and UpdateMesh() as they are also called by MatchRectTransformWithBounds (see the code here).

Nelvin

Harald
Sorry for my late reply but my ISP is having issues since Friday.
Thanks a lot for your help - strangely this helps in my preview panel where the currently selected unit is shown but not when I use the exact same code (using the same method where I initialize the SkeletonGraphic, set the scaling mode etc.) for the list of selectable units. For these, my Spine animations are scaled down to a tiny size rather than filling the available rect.
In my quest to find the issue or at least a workaround, I eventually tried to just DestroyImmediate the SkeletonGraphic component and add a new one. So far, this seems to work.

I've attached a screenshot and it seems the rectTransform is correct but the scaling of the mesh is wrong.

What I noticed is, if I do not set the sizeDelta to zero, the visual scaling is correct but only because the rectTransform is huge and, as a result, the selected unit is way to big.

Finally, if I call MatchRectTransformWithBounds before and after setting layoutScaleMode to FitInParent, it works for in both cases.

Any further idea what may go wrong when reusing the existing one?

I can use either workaround but I'd feel more comfortable to know if there might be an issue on my side or if this is caused by the issue you tracked, so will eventually be fixed.

Thanks a lot

Harald

Harald @Nelvin Sorry, I noticed that you're setting Multiple CanvasRenderers via code.

I just noticed it was Spinebot who suggested the setting, not your actual code.

Nelvin Thanks for your fast reply - it's disabled, for the sake of completeness I enabled it, but the result was just an error.

I could not yet reproduce such an error message when enabling Multiple CanvasRenderers. How did you enable this setting? By enabling it in the Inspector, or via code? If via code, where in relation to the other API calls did you place the call?

Harald

Nelvin What I noticed is, if I do not set the sizeDelta to zero, the visual scaling is correct but only because the rectTransform is huge and, as a result, the selected unit is way to big.

Finally, if I call MatchRectTransformWithBounds before and after setting layoutScaleMode to FitInParent, it works for in both cases.

Any further idea what may go wrong when reusing the existing one?

I can use either workaround but I'd feel more comfortable to know if there might be an issue on my side or if this is caused by the issue you tracked, so will eventually be fixed.

Thanks for sharing your investigations. We will publish a proper bugfix, I was just not fast enough on Friday evening with finding the proper solution.

Harald

@Nelvin We have just released a bugfix for the issue on the 4.2 branch.
A new spine-unity 4.2 unitypackage is available for download here as usual:
https://esotericsoftware.com/spine-unity-download
Please let us know whether this fixes the issue on your end as well. Thanks for reporting!

Nelvin

Harald I'm currently bound to 4.1 - is it possible to add the changes to the 4.1 branch too? That would be great.

Thanks a lot.

Harald

@Nelvin Sorry to say that such a commit is slightly too risky, it might break existing 4.1 projects.

Nevertheless, you should be able to integrate the changes of the following commit quite easily into your local spine-unity 4.1 runtime installation:
EsotericSoftware/spine-runtimesb1fe837

Nelvin

Harald No problem and very understandable - I'll integrate the changes locally then.

Harald

Glad to hear, thanks for your understanding.