wiige We have checked to see why the link is not being added properly, and it appears to be due to a change in the translation of "Previous:" and "Next:" on the Chinese page. Other documents in Chinese (e.g., general runtime guide and user guide) use "下一节: / 上一节:" , but the spine-unity runtime documentation uses "下一章: / 上一章:" , which seems to be causing the detection to fail.
If there is no particular reason why this should be the case, I would like to use "下一节: / 上一节:" to match the other documents. Do you think we should use "下一章: / 上一章:", including the other pages? Let me know your opinion!

wiige Thank you for explaining in detail! From your description, it sounds like it would be better to use "下一节: / 上一节:", as each page of the spine-unity documentation is structured to be followed by content that assumes that the previous section has been explained, rather than completely independent content. So I'll change it to "下一节: / 上一节:".

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

wiige Thank you for your very quick response! I have updated the Chinese page with the translation you provided and it looks perfect:
https://zh.esotericsoftware.com/spine-skeleton-viewer

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.)

@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!

@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.

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

wiige Thanks for translating the spine-pixi documentation! I made a few minor corrections to the link URLs, but otherwise it seems perfect:
https://zh.esotericsoftware.com/spine-pixi

Thank you so much for all your help!

@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.

wiige Thank you for the update! Reflected in the documentation:
https://zh.esotericsoftware.com/spine-unity-main-components#%E5%8A%A8%E7%94%BB-AnimationState
I truly appreciate all the help and support you’ve given us throughout this year. I’m so grateful for your dedication to translating Chinese for such a long time. I hope we can continue to count on your help next year as well!

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.