@wiige BTW: Now would be a rather unstable time to update the API translation, as with the 4.3-beta runtime changes rather large parts of the documentation have changed, and the respective documentation is not up to date yet. The changes affect mainly everything related to bone poses, transforms and applied transforms and constraints. So please do not put any effort into syncing these sections yet.

@wiige Thanks for asking, sure!

Please note that this page is directly edited, it's not generated from a template like the spine-unity-download variants. At the download pages we generate the content to keep the current download URLs and version numbers in sync.

@wiige Thanks very much for your quick and thorough update! We've updated the spine-unity-download page accordingly.

wiige I found several mistanslations at https://zh.esotericsoftware.com/spine-unity-download, will rectify them and post here with physics-constraints guide

@wiige Oh, thanks for letting us know! As the spine-unity-download page is generated, might I ask you if you could directly modify the template instead of the generated result page:

@wiige Thanks very much for translating the page, much appreciated as always!

wiige note that I translated "On-Demand Loading" as "懒加载/惰性加载" which is Lazy Loading, by my understanding to the doc, because "按需加载"(literal translation) is not a customary expression in Chinese.
are they equivalent? I need an unity expert @Harald

Yes, the terms are equivalent. Thanks for translating it in the most suitable way.

Hi, @wiige ! A completely new page, ”On-Demand Loading UPM Packages,” has been added to the spine-unity runtime documentation. Could you help with the translation?

The diff is below, but as for the table of contents, I can add the links to each page, so you don't need to prepare the .md files for each page, just let me know the translation text:
https://diffy.org/diff/d421898072269

Thanks in advance!

@wiige Thanks for the quick translation, that was very fast! ️ We've updated the spine-unity documentation page accordingly.

@wiige FYI: We've added two lines explaining mixing and empty animations to the spine-unity-main-components page (the last line in the diff just had also removed and is otherwise unchanged):
https://diffy.org/diff/202dd31b1911a

Changes are in these sections:
https://esotericsoftware.com/spine-unity-main-components#Setting-Animations
https://esotericsoftware.com/spine-unity-main-components#Empty-Animation-and-Clearing

Hi, @wiige! The general Spine runtime guide has been updated, so I’d like to share the diff with you. We’d really appreciate it if you could also update the Chinese documentation. : https://diffy.org/diff/6502be39f4709
Thanks as always!

@wiige Glad to hear, thanks for checking!

@wiige FYI: We've just added a documentation section for a recently adde RenderExistingMeshGraphic utility component (a SkeletonGraphic variant for RenderExistingMesh). I've already added an analogous Chinese translation here:
https://zh.esotericsoftware.com/spine-unity-utility-components#RenderExistingMeshGraphic
If I made a mistake there with the translation, please let me know.

Hi @wiige !
Sorry for the delay in sharing this, but I would like to ask you to translate the contents of the updated Installations section of the spine-godot documentation. Here is the diff:
https://diffy.org/diff/d78e826c6f783

The diffs may look long, but they are mostly scripts, so there are not many parts to translate. I would appreciate it if you could respond at your convenience.

Hi @wiige !
We have updated the pixi objects section and added an explanation about bounds providers in the spine-pixi documentation, could you please translate these?: https://diffy.org/diff/047538dbf9c1

Happy New Year, @wiige ! There has been a small update to the spine-pixi documentation and I am sharing the diff with you: https://diffy.org/diff/6337c752b1cfa
I hope you will take a look at it when you have time.

@wiige FYI: We've added a small section to the spine-unity-main-components page here. It's a remark to not call SetAnimation every frame and what to do instead.

The diff is as follows:
https://diffy.org/diff/30c056aef9214
Here is the added text, starting before #### Queueing Animations:

> **Important Note: don't call `SetAnimation` every frame.** It might be tempting to call `SetAnimation` with the target animation in your script's `Update` method regardless if it's already playing, thinking that the spine-unity runtime will automatically detect whether the animation changed. Not only will this start the animation anew each frame, freezing at the animation's first frame. As the Spine runtimes are designed for smooth transitions between animations, this will also add a [TrackEntry](/spine-api-reference#TrackEntry) for each call, mixing from animations previously added on the same track to this newly added one.
>
> Instead of calling `SetAnimation` every frame, keep track of the current state of your character and only call `SetAnimation` when you want to change to a different animation.
If you ever want to keep the animation at the first frame while e.g. pressing and holding a button, set [TrackEntry.trackTime](/spine-api-reference#TrackEntry-trackTime) instead. If this is not an option, you can use [AnimationState.ClearTrack](/spine-api-reference#AnimationState-clearTrack) to clear all animations on the same track before setting the new animation.

Thanks very much for your quick update @wiige, much appreciated as always!

@wiige FYI: We've just added an additional entry to the spine-unity FAQ section, regarding incorrect colors when Tint Black is only enabled at the material:
https://diffy.org/diff/fd7bf735a70d7

If the diff causes problems, the new section text is as follows:

> **Why does my skeleton display wrong colors when I enable the Tint Black option in the material settings?**  

![](/img/spine-runtimes-guide/spine-unity/CommonError-Tint-Black.png)  

Please make sure that you have enabled `Advanced - Tint Black` at the SkeletonRenderer (or SkeletonAnimation) component.

@wiige Sorry, it took me a while to realize that the spine-c and spine-cpp runtime documentation has been significantly updated, and I am late in sharing it with you. You can see the diffs below:

• spine-c: https://diffy.org/diff/1814165bcbeaf
• spine-cpp: https://diffy.org/diff/0d5a63c184f6c

I know you are in the process of working on the spine-pixi one, so I would be happy to check it out when it is convenient for you. Thank you for all of your help!

Hi, @wiige!
Yesterday we released the spine-pixi-v8 runtime and with it a major update of the spine-pixi documentation: https://esotericsoftware.com/spine-pixi

So we would be grateful if you could translate it when you have time.
(Incidentally, the runtime page has not yet been updated, but this documentation can be accessed via the spine-pixi-v8 release blog.)

Hi, @wiige. We recently added a section to the Skeleton Viewer documentation that mentions how to run it from the trial version, but I now realize that the Chinese documentation seems to have been outdated for quite some time. I apologize for not being able to provide a clear diff file, but I have added the missing section in English and hope you will check it out when you have time:
https://zh.esotericsoftware.com/spine-skeleton-viewer