You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am currently using the spine-v8 runtime that pixijs is working on. https://github.com/pixijs/spine-v8 this one. It says that this will be added when it's ready to the official esoteric runtimes.
In the runtime (spine-v8) there is no logic for containers for each slot like in pixi-spine.
The slotsContainers logic is needed when we want to apply filters, masks, etc to the slot attachment.
The logic for adding spine atlases from already loaded pixi resources is also needed. I've made a mixin for this logic pixijs/spine-v8#41 for spine-v8. But will it be added in the spine-v8 ?
Will there be slot containers logic added in the spine-v8 runtime ? What are the draw backs if it is ?
Will the pixi-spine runtime be deprecated after the adding of the official esoteric runtime ?
How to consider which runtime to use ?
Thank you in advance.
Cheers, Kaloyan.
The text was updated successfully, but these errors were encountered:
Hello, I am currently using the spine-v8 runtime that pixijs is working on. https://github.com/pixijs/spine-v8 this one. It says that this will be added when it's ready to the official esoteric runtimes.
In the runtime (spine-v8) there is no logic for containers for each slot like in pixi-spine.
The slotsContainers logic is needed when we want to apply filters, masks, etc to the slot attachment.
The logic for adding spine atlases from already loaded pixi resources is also needed. I've made a mixin for this logic pixijs/spine-v8#41 for spine-v8. But will it be added in the spine-v8 ?
Will there be slot containers logic added in the spine-v8 runtime ? What are the draw backs if it is ?
Will the pixi-spine runtime be deprecated after the adding of the official esoteric runtime ?
How to consider which runtime to use ?
Thank you in advance.
Cheers, Kaloyan.
The text was updated successfully, but these errors were encountered: