gyzbean

I don't see any particular issue, apart from the fact that you removed "Strip Whitespace X/Y."
How many atlas pages does this configuration export?

We cannot help you if you don't send us a minimal reproduction project of your issue, as I said above.
Many users use spine-godot without any issue with draw calls.

@gyzbean Thanks for preparing a reproduction project. As Davide said above, you can send it to contact@esotericsoftware.com.

@gyzbean You can upload your project at some filehosting service and share a link if file size is too big.

gyzbean

Thanks for sending us the project. We'll analyze the issue as soon as we can, probably next week.

This is a limitation of Godot. They currently do not implement batching for 2D triangle meshes.

orgs/godotengineprojects/33?pane=issue&itemId=20224421

We've worked around this as best as possible, by using meshes explicitely:
EsotericSoftware/spine-runtimesblob/4.2/spine-godot/spine_godot/SpineSprite.cpp#L173

However, that does not help with draw calls. It does improve performance compared to canvas_item_add_triangle_array though.

Note however, that Godot 4+ uses Vulkan as the default renderer. Batching is much less impactful there, which is one of the reasons it hasn't been implemented by Godot yet.

I think Godot is mature enough for production use, including on mobile. Vulkan makes batching mostly irrelevant.

I suggest you setup a simple scene with multiple SpineSprite nodes that's similar to your target complexity and test performance on devices you care about.