• RuntimesGodotBugs
  • When you fill in the SpineSkeletonDataResource, godot 4.4 crashes

Hello! I started learning how to use Spine with Godot 4.4. stable and 4.4.1. Godot Engine 4.4.stable.official.4c311cbee - Vulcan 1.4.303 - Forward+ - Using Device #0: NVIDIA - NVIDIA GeForce RTX 3080.
I downloaded spine-godot GDExtension 4.4.1, put it in the project folder with examples, and the project started normally. Then, following the spine-godot Runtime Documentation, I created a resource, added a skeleton and a SpineBoy atlas to it. When adding a new element to the Animation Mixes array godot crushes. And if you first add 2 elements to the array, then at the beginning godot does not crash, you can also add either an atlas or a skeleton, but as soon as the resource is filled with both atlas and skeleton and the array has only one element, godot crashes again. I recorded a video showing this problem.
In addition, all the examples worked, except for opening the file. I pointed out the path to him, but the coin was not found, and if the coin is inside the project, then it is located without problems.
video
bug text in console:
CrashHandlerException: Program crashed with signal 11
Engine version: Godot Engine v4.4.stable.official (4c311cbee68c0b66ff8ebb8b0defdd9979dd2a41)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] error(-1): no debug info in PE/COFF executable
[2] error(-1): no debug info in PE/COFF executable
[3] error(-1): no debug info in PE/COFF executable
[4] error(-1): no debug info in PE/COFF executable
[5] error(-1): no debug info in PE/COFF executable
[6] error(-1): no debug info in PE/COFF executable
[7] error(-1): no debug info in PE/COFF executable
[8] error(-1): no debug info in PE/COFF executable
[9] error(-1): no debug info in PE/COFF executable
[10] error(-1): no debug info in PE/COFF executable
[11] error(-1): no debug info in PE/COFF executable
[12] error(-1): no debug info in PE/COFF executable
[13] error(-1): no debug info in PE/COFF executable
[14] error(-1): no debug info in PE/COFF executable
[15] error(-1): no debug info in PE/COFF executable
[16] error(-1): no debug info in PE/COFF executable
[17] error(-1): no debug info in PE/COFF executable
[18] error(-1): no debug info in PE/COFF executable
[19] error(-1): no debug info in PE/COFF executable
[20] error(-1): no debug info in PE/COFF executable
[21] error(-1): no debug info in PE/COFF executable
[22] error(-1): no debug info in PE/COFF executable
[23] error(-1): no debug info in PE/COFF executable
[24] error(-1): no debug info in PE/COFF executable
[25] error(-1): no debug info in PE/COFF executable
[26] error(-1): no debug info in PE/COFF executable
[27] error(-1): no debug info in PE/COFF executable
[28] error(-1): no debug info in PE/COFF executable
[29] error(-1): no debug info in PE/COFF executable
[30] error(-1): no debug info in PE/COFF executable
[31] error(-1): no debug info in PE/COFF executable
[32] error(-1): no debug info in PE/COFF executable
[33] error(-1): no debug info in PE/COFF executable
[34] error(-1): no debug info in PE/COFF executable
[35] error(-1): no debug info in PE/COFF executable
[36] error(-1): no debug info in PE/COFF executable
[37] error(-1): no debug info in PE/COFF executable
[38] error(-1): no debug info in PE/COFF executable
[39] error(-1): no debug info in PE/COFF executable
[40] error(-1): no debug info in PE/COFF executable
[41] error(-1): no debug info in PE/COFF executable
[42] error(-1): no debug info in PE/COFF executable
[43] error(-1): no debug info in PE/COFF executable
[44] error(-1): no debug info in PE/COFF executable
[45] error(-1): no debug info in PE/COFF executable
[46] error(-1): no debug info in PE/COFF executable
-- END OF BACKTRACE --

Related Discussions
...

Spinebot The documentation just states that there are 2 versions. One of which is 4.4.1. I tested on versions 4.4. stable and 4.4.1

By trial and error, I managed to create a resource. The procedure is as follows: after I created the resource, the first thing I did was add 2 elements to the animation_mixes array. Next, I assigned the Object type to both elements via the pencil icon to the right of the elements in the inspector. Next, click the drop-down menu to the left of the pencil and select SpineAnimationMix at the very bottom. In the elements, I wrote idle and run as in the examples. And then I added a skeleton with an atlas to the resource. I assume that the errors may be related to SpineSkeletonDataResource::set_animation_mixes or SpineSkeletonDataResource::update_mixes(). I hope that this bug will be fixed soon.

  • Misaki ответили на это сообщение.

    ram876 We apologize for the unclear response from Spinebot. This appears to be a known bug in spine-godot GDExtension:
    EsotericSoftware/spine-runtimes2779
    By subscribing to this ticket, you will receive notifications when there is progress on the issue.

    Based on my testing, spine-godot custom C++ engine module works fine, so if there is no reason to use GDExtension, it would be quicker for you to start your work if you use that.

    • ram876 ответили на это сообщение.
    • ram876 оценил это.

      Misaki Thanks! Yes, in the module, I didn't get any errors when resizing the array.