Categories
- All Categories
- 1.2K Cubism Editor
- 1K Help
- 56 Tips and Tricks
- 148 Feature requests
- 48 Other Live2D Products and Tools
- Cubism Viewer (for OW, for Unity)
- 3 Material Separation Photoshop Plug-in
- 45 Other Live2D Products and Tools (Other Photoshop Scripts, Sample Data, etc.)
- 262 Cubism SDK
- 235 Help
- 11 Tips and Tricks
- 16 Feature Requests
- 5 SDK for Unreal Engine alpha
- 2 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.
Keyform Optimization
An idea to optimize keyforms; The ability to select what attributes receive key data when adding keys.
Right now, it saves vertex/point position, color data (multiply/screen) opacity, and draw order for every key.
I'm not sure if unchanged data gets optimized on export, but the editor has gotten noticeably slower over time as more things become keyable, as every key holds data for every attribute.
It might help if we are able to specify what attributes receive keys on which parameters, so we could exclude opacity keys for something that doesn't need to change opacity in editor
This would also make edits that currently require the "multiple keyform edit" no longer need it for most applications (such as toggles or color slider keys).
Overall it'd mean a lot less gets processed for extended interpolations as well, allowing for cleaner files.
Right now, it saves vertex/point position, color data (multiply/screen) opacity, and draw order for every key.
I'm not sure if unchanged data gets optimized on export, but the editor has gotten noticeably slower over time as more things become keyable, as every key holds data for every attribute.
It might help if we are able to specify what attributes receive keys on which parameters, so we could exclude opacity keys for something that doesn't need to change opacity in editor
This would also make edits that currently require the "multiple keyform edit" no longer need it for most applications (such as toggles or color slider keys).
Overall it'd mean a lot less gets processed for extended interpolations as well, allowing for cleaner files.
Comments
Thanks for using our products.
Please tell us about the environment you are using so that we can share your request in more detail with our development team.
For questions regarding Editor, please provide: Live2D Software Version: (e.g. Cubism Editor 4.0.01)
- Live2D Software Version: (e.g. Cubism Editor 4.0.01)
- OS & Version: (e.g. Windows 10, macOS HighSierra)
- PC Model: (e.g. MacBookPro 2017)
- Graphics Specifications: (e.g. GeForce GTX 950M)
- CPU: (e.g. Intel Core i7-7700)
- Memory: (e.g. 8GB)
- Illustration Software used: (e.g. Photoshop, ClipStudio, SAI)
- Attach screenshot or capture video to show your problem: (e.g. Photoshop, ClipStudio, SAI)
Best regards.
My PC is generally strong and capable of handling the load of large models for the most part
I have an NVidia RTX 3090 graphics card as well
The software generally runs okay, but full models with extended interpolations etc become laggy. I was thinking if we could limit what attributes actually get saved keys, perhaps it could reduce the computational load of adjusting parameters/keys, as well as offer some additional utility
Thanks for sharing the details.
I have shared your request with our development team.
Best regards.