If you have any questions, reports, suggestions, or requests about Live2D, please send them to this forum.
※We cannot guarantee statements or answers from Live2D staff. Thank you for your understanding in advance.
 
Live2D Cubism
Cubism Products and Downloads
Cubism product manuals and tutorials
Cubism Editor Manual    Cubism Editor Tutorial    Cubism SDK Manual    Cubism SDK Tutorial
[About Cubism Editor / SDK 5.4 Alpha](Updated: July 14, 2026)

You can download the alpha installer from the dedicated forum below.
If you have any feedback regarding the alpha version, including feature requests or bug reports, please use the same forum.

Cubism Editor / SDK 5.4 Alpha Forum
https://creatorsforum.live2d.com/c/cubismeditorsdk54alpha/

[Regarding macOS Tahoe](Updated October 16, 2025)

macOS v26 Tahoe is now supported!
We advise against upgrading your macOS at this time as it may cause Live2D products not to function correctly.
Upgrading macOS can also cause you to lose your Cubism Editor license file.
Please make sure to deactivate your Cubism Editor license before upgrading the macOS.

For more details:
https://help.live2d.com/en/other/other_09/
For inquiries regarding issues with license purchases or license activation errors, please contact us through the email form.

Complex Warp Deformer Performance Issue (and a tip to avoid it)

Steps to reproduce in Live 2D Cubism Editor 5.3.04:

1) Create a complex Warp Deformer (eg; 10x10 or more Divisions, Angle X + Angle Y with 5 keys each at -30, 15, 0, 15 30, and Extended Interpolation)
2) Create a very simple Warp Deformer* (eg; 2x2 Divisions, no keys)
3) Attempt to deform the simple Warp Deformer

This will incur the same deformation penalty as the complex deformer! However...

4) Put the complex deformer into its own Part (folder)
5) The performance is back!

* The performance hit affects other other types (like ArtMesh) and actions (like selection or movement) too

Recording of the issue and fix

P.S. For the development team: surely this is a cache issue? The complex warp deformer is a sibling of the other parts in the root / parent part, but if it's not selected and not part of the hierarchy, any calculations on it can surely be skipped since it can't be affected? Unless siblings can affect warp deformers in ways i'm not familiar with. At the very least, moving a sibling part surely should not invalidate this cache? If it's a bounds recalculation then bounds of warp deformers should be cached instead of recalculated.
Sign In or Register to comment.