[Notice of Holidays]
Please note that our staff will not be available from 2024/Dec/28 - 2025/Jan/5 JST.
The Live2D Creators Forum will remain open during the holidays.
Submissions that require a response will be answered after we reopen for business.
Please note that it will take longer than usual to respond to your request.
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.
0 ·
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.