Based on the error message you're showing, this appears to be an IndexOutOfRangeException related to array bounds in the threading system of spine-unity 4.3-beta.
Regarding the CPU core count issue:
Yes, it looks like Environment.ProcessorCount is returning 32 (based on your CPU information showing 16 cores with 32 logical processors), which may be causing the array index to go out of bounds in the threading implementation.
Recommended Solutions:
Try manually limiting the thread count - You can try setting a lower thread count to see if this resolves the issue. This would help confirm if the high core count is the problem.
Check your spine-unity version - Make sure you're using the latest 4.3-beta version. The most recent spine-unity 4.3-beta was updated on 2025-10-20. You can download it here:
Disable threading temporarily - As a workaround, you could try disabling threaded operations in your Spine Preferences:
- Go to
Edit > Preferences > Spine
- Under Threading Defaults, try disabling:
- Threaded Mesh Generation
- Threaded Animation
Reporting the Issue:
If updating to the latest version doesn't fix the problem, this appears to be a legitimate bug with high core count systems (32 threads). The array bounds checking in the threading system may not account for systems with this many logical processors.
Could you confirm:
- Which exact version of spine-unity 4.3-beta you're currently using?
- Whether disabling threading in the Spine Preferences resolves the crash?
This information would be helpful for tracking down the specific cause of the array index issue.
