Categories
- All Categories
- 1.2K Cubism Editor
- 1K Help
- 56 Tips and Tricks
- 149 Feature requests
- 50 Other Live2D Products and Tools
- Cubism Viewer (for OW, for Unity)
- 3 Material Separation Photoshop Plug-in
- 47 Other Live2D Products and Tools (Other Photoshop Scripts, Sample Data, etc.)
- 266 Cubism SDK
- 239 Help
- 11 Tips and Tricks
- 16 Feature Requests
- 6 SDK for Unreal Engine alpha
- 3 Download
- 1 Manual and Update History
- 2 Bug
- Feature Request
- 181 Community
- 37 General Discussions
- 9 Feature Requests
- 26 Projects, Showcase & Critiques
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
※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 macOS Sequoia] (Updated October 22, 2024)
Live2D Cubism Editor 5.1.02 now supports macOS Sequoia.
Other Live2D Cubism products currently released are not guaranteed to work on macOS Sequoia.
Please refrain from upgrading macOS, as it may not operate properly.
Live2D Cubism Editor 5.1.02 now supports macOS Sequoia.
Other Live2D Cubism products currently released are not guaranteed to work on macOS Sequoia.
Please refrain from upgrading macOS, as it may not operate properly.
SimpleModel.expressionMgr.stopAllMotions() couldn't be called
I was wondering how this could be invoked.
Every time I change into a new expression, the parameters are stuck and the intended expression could not be seen.
I was wondering if there was actually a stop all expressions function like in motionMgr.stopAllMotions().
Every time I change into a new expression, the parameters are stuck and the intended expression could not be seen.
I was wondering if there was actually a stop all expressions function like in motionMgr.stopAllMotions().