visgotti Posted July 3, 2020 Share Posted July 3, 2020 I'm implementing something similar to spine, except the editor is in the web browser and is catered to pixel art.. For the runtime - I'm going to have each 'skeleton' be a container, now I'm wondering if it'd be more optimized to have a sprite per 'skeleton' layer, then change those textures based on the current frame, or would it be faster to have sprites keep the same texture, then resort the parent container's children? I can write code to benchmark this myself, but it'd save some time if anyone has experience/insight about this. All textures per 'skeleton' will share the same baseTexture regardless of which method I go with, so hopefully one of the two methods I mentioned will utilize that optimization more than the other Quote Link to comment Share on other sites More sharing options...
ivan.popelyshev Posted July 3, 2020 Share Posted July 3, 2020 Sprite is lightweight, just change its texture. visgotti 1 Quote Link to comment Share on other sites More sharing options...
visgotti Posted July 3, 2020 Author Share Posted July 3, 2020 2 minutes ago, ivan.popelyshev said: Sprite is lightweight, just change its texture. As always, thanks for the quick response Ivan! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.