يتمّ عرض هذا الموقع بشكل أفضل في متصفّح حديث مع تمكين JavaScript.

spine-ts/three - How to clean up properly?

davidp

How can you properly clean up all the geometry & materials, instances, loaders, etc. after use to free up all memory?
I have a game with multiple levels and every time the spine gets loaded again, it doesn't clear the memory and slowly causes the performance to drop

davidp

Mario

three.js comes with dispose() methods for meshes and matrials, see their examples here: https://threejs.org/examples/?q=memory#webgl_test_memory2

I've added an issue to add a dispose() method to the relevant classes in spine-ts three.js. [ts][threejs] Dispose methods for resource clean-up · #1412

Mario

I've now added SkeletonMesh#dispose() and the underlying needed changes in the 3.8-beta branch. To make sure there's no leak, you need to do 2 things:

If you remove a SkeletonMesh from the scene, call its dispose() method. This will dispose the underlying mesh(es) and material(s).
If you have a TextureAtlas that is no longer in use, call its dispose() method. This will dispose the underlying texture(s). Make sure no other SkeletonMesh is using that atlas!

davidp

Thanks!

I just tried the 3.8-beta branch but I'm having issues loading spines, no errors, but they're just invisible. Has the loading/initialisation changed from 3.7?

I just looked and it seems like the count property of drawRange for the MeshBatcher is 0 for the 3.8-beta version, whereas its 219 for the 3.7 version

EDIT: Sorry, just learned that 3.8 of the runtimes also means that I have to update the spines to 3.8. Will test again shortly

EDIT2: Working fine now in 3.8-beta 🙂 thanks!

Mario

Cool 🙂