Spine 3899 Updated Jun 2026

A persistent bug in earlier builds caused incorrect bone inheritance flags when exporting animations from Spine to runtime engines like Unity and Unreal. Specifically, non-uniform scaling on parent bones would occasionally corrupt child bone transforms. Build 3899 fixes the matrix calculation errors. Testing confirms that animations exported with the updated version retain precise world-space positions across all major runtimes (C++, C#, Lua, and Haxe).

When upgrading framework engines or web renderers while running 3.8.99 data, gray lines or edge bleeding artifacts can emerge on graphic borders. This occurs due to alpha premultiplication or texture bleeding modifications across game engines. To mitigate this issue without updating your entire animation library, verify your texture packing export preferences inside Spine, ensuring that aligns perfectly with your engine's rendering pipeline configurations. 3. Trial Launcher Overage Errors

Which (e.g., Unity, Godot, Phaser) are you importing your 3.8.99 assets into? spine 3899 updated

Unity import 2018, Spine 3.8.99 not importing Atlas - Spine Forum 3 Dec 2020 —

in the "Export -> Pack Settings" section to help Unity read the file correctly. Texture Artifacts A persistent bug in earlier builds caused incorrect

: Recent updates from providers like Medtronic and Arthrex detail changes where over 75 spine and cranial procedures were removed from the Inpatient Only (IPO) list and over 100 were added to the ASC Covered Procedures List.

3.8.99 supports standard features like mesh deformation, skinning, and IK, which remain highly capable. Testing confirms that animations exported with the updated

Esoteric Software typically follows a pattern: a major release (e.g., Spine 4.2), quarterly feature updates, and hotfix builds like 3899. Based on roadmap discussions, the next milestone will focus on:

If you are maintaining a project specifically on version 3.8.99, focus on these key legacy features and upgrade requirements:

: Intermittent atlas texture coordinate parsing errors can cause texture tearing or misaligned attachments inside runtime environments like Unity or custom C++ engines.