galacean / engine-spine Goto Github PK

Add slot separate ability for SpineAnimation component

The Galacean Spine runtime code has become quite outdated and is facing issues both in its project architecture and performance. The demand for Spine is gradually increasing, necessitating an urgent refactoring and optimization of the runtime code.

Refactoring includes several aspects:

Project Engineering Optimization #66 #56

• Spine has released higher versions like 4.0, 4.1, etc. The past project structure, unable to fulfill the needs of managing multiple versions, necessitates an update to the project engineering structure.
• Parts of the runtime are coupled with the Galacean editor, which need to be separated in the directory structure.

Loader Optimization

• Support for loading multiple textures. #85 #53
• Create material and set texture during loading. #48
• Custom file loading. #88

Renderer Optimization

• Optimize code structure for improved code readability.
• Optimize mesh generation logic to improve performance. #52
• Support for Spine 4.0, 4.1.
• Support for premultiplied mode.
• Use double buffering to improve performance (Performance testing is required to determine if it can enhance performance).
• Calculate bounding box at first rendering frame. #84

Problem

When we move spine to the edge of scene, the spine disappeared.

// spineEntity.transform.setPosition(0, -15, 0)
spineEntity.transform.setPosition(27.9, -15, 0)

We just need to move a little bit, and the spine will disappear immediately.
But it should still show a little spine.

Reproduction

https://stackblitz.com/edit/b1ookm?file=index.ts

Reason

This is caused by bounds of spine.

The bounds of spine is a point.

We can update the bounds manually to temporarily fix it.

const spineAnimation = spineEntity.getComponent(SpineAnimation)
spineAnimation.autoUpdateBounds = true
// or
// spineAnimation.updateBounds()

Now, it works well.

Expected

Spine, which is not truncated by default, updates bounds as needed.

spine 资源 loader 引用的 engine 不是当前 engine 实例，是之前创建的 engine 实例。
如果前 engine 销毁，再加载 spine 资源会报错。

1. According to unity runtime, its better to generate sub mesh instruction before actually add submesh.So runtime need do this.
2. Now a lot of logic is all in buildMesh function, its redundancy.

Fix SpineAnimation clip attachment render problem.

Adapt engine-spine to mars runtime

Raptor hoverboard animation get wrong rendering result.

expect like this:

support loading json and atlas file

• If no clipping involved, set texture once after playing animation.
• If clipping involved, set texture at each frame, using dirty flag to optimize.
• If had multiple texture, set texture at each frame, using dirty flag to optimize.

Now the whole spine animation combine as one single mesh.
So, different attachments cannot have additive effect.
Runtime should separate attachment which has different blend mode as sub mesh, and give it new material.

1. Support multiple texture
2. Fix hack texture problem that fragment sub mesh not share one default material.

when set scale less than 0.01, render is wrong

but when scale is bigger than 0.01，render is right

Currently, the loader determines the file type based on the file extension during the loading process. However, it fails to handle temporary links created via URL.createObjectURL. The loader needs to attempt processing these types of files and provide feedback to the user.

• Simplify component, refactor SpineRenderer -> SpineAnimation
• Use new MeshRenderer
• Refactor resouce loader
• Support load bin file
• Remove oasisTexture, use Texture2D
• Encapsulate spine resource class for editor

• vite use [email protected] which is not support apple m1, need be upgraded