Hello,
we experience quite a lot of fatal exceptions caused by the spine runtime.
Below you can see the crashlog from Crashlytics. We do not have this locally, but it happens on some devices.

Fatal Exception: IndexOutOfRangeException
0 ??? 0x0 BuildMeshWithArrays (Spine.Unity.MeshGenerator)
1 ??? 0x0 UpdateMeshSingleCanvasRenderer (Spine.Unity.SkeletonGraphic)
2 ??? 0x0 UpdateMeshToInstructions (Spine.Unity.SkeletonGraphic)
3 ??? 0x0 Rebuild (Spine.Unity.SkeletonGraphic)
4 ??? 0x0 PerformUpdate (UnityEngine.UI.CanvasUpdateRegistry)
5 ??? 0x0 CanvasUpdateRegistry😛erformUpdate (UnityEngine.UI)

Can you provide help with this, please? How can we solve or avoid this or know which asset is causing it?
Thanks

Related Discussions
...

Based on the crash log you've provided, it seems like the issue is related to the SkeletonGraphic component in the Spine-Unity runtime. The IndexOutOfRangeException could be caused by various factors, including but not limited to issues with the mesh generation process or how the SkeletonGraphic component is updated.

To address this issue, here are a few steps you can take:

  1. Ensure you're using the latest version of the Spine-Unity runtime. Updates often include bug fixes that might resolve your issue. You can check the latest version on the Spine Unity Download page.
  2. Check for any custom modifications you might have made to the Spine runtime or your assets that could lead to this exception.
  3. Review how you're using the SkeletonGraphic component, especially if you're dynamically changing assets or properties at runtime. Make sure you're not inadvertently causing the mesh to be in an invalid state.
  4. Test with different assets to see if the issue is isolated to specific Spine assets. This could help identify if the problem is related to how certain assets are set up or exported from Spine.

Unfortunately, without a reproducible example or more specific details, it's challenging to pinpoint the exact cause of the issue. The steps above are general troubleshooting tips that might help you narrow down or resolve the problem.

  • Harald

  • Gönderi #3
  • Düzenlendi
  • Bu yayın İngilizce içinde

@ffischer Very sorry to hear you're encountering such issues! Which exact version of the spine-unity runtime are you using? We would love to receive a reproduction project for this issue, if it still occurs using the latest version of the spione-unity runtime.

Your problem may be caused by accessing the SkeletonGraphic.skeleton and modifying active attachments after SkeletonGraphic.LateUpdate(), as described in this posting:
https://esotericsoftware.com/forum/d/24056-index-was-outside-the-bounds-of-the-array-in-meshgenerator/13

See the following thread in general:
https://esotericsoftware.com/forum/d/24056-index-was-outside-the-bounds-of-the-array-in-meshgenerator
If you have any additional information, please let's continue the discussion over at the above thread to keep the discussion to a single thread.

4 gün sonra
14 gün sonra

@Harald
Thanks for the response and the fix. We released an update with it and the crashes are gone.

  • Harald

  • Gönderi #6
  • Bu yayın İngilizce içinde

@ffischer Thanks for confirming, glad to hear.