Цей сайт найкраще переглядати в сучасному браузері з включеним JavaScript.

Function of disable bones?

baofengming

In spine,when I want to make some parts invisible,the only way I can do is to adjust the slot alpha to 0 in the setup mode,but after when the program rendering this animation, those parts still have to be rendered, although they are invisible.
Actually I don`t want neither those pictures nor bones be rendered or be updated,it is not good for FPS.So,is there any way I can "disable" and "enable" bones? so when rendering, those bones and pictures will not be rendered.
Thanks!

baofengming

Pharan

You're right. From what I know, it's better performance to key an image hide (the same way you key an image swap). I think that may be the biggest thing that affects framerate.

I wish disabling bones was a feature too though, not that I know how much of an impact it really makes.

Each bone update does do several multiplication operations regardless of whether the animation affected that bone or if it's a terminal bone without any image attached to it. Depending on your framework/engine and your purposes, this may or may not need to be done anyway.

baofengming

Spine is a great tool for 2d games develop, especially mobile games, but to develop games for mobile platform, performance is very important.
for example, i did a character with many different equipment and special effect,for example, a wizard of ice,most animation like "walk" ,"stand".... I don`t need any ice image to show, only in some peculiar animation, like when he do "attack" or "spell",those ice image is needed.Characters like this is really impact the performance.
so, if there is a function,I can choose "disable" for some bones in setup mode, and those bones will not be rendered, unless they are be animated in some animation, which means they have key frame. that would be great.
Thanks!!

Nate

You can hide attachments, which is preferred over setting the alpha to zero which will affect your fill rate. See the image switching video.

The bone local to world computations are generally not a bottleneck.