Categories
- All Categories
- 1.4K Cubism Editor
- 1.1K Help
- 56 Tips and Tricks
- 178 Feature requests
- 51 Other Live2D Products and Tools
- Cubism Viewer (for OW, for Unity)
- 3 Material Separation Photoshop Plug-in
- 48 Other Live2D Products and Tools (Other Photoshop Scripts, Sample Data, etc.)
- 287 Cubism SDK
- 257 Help
- 11 Tips and Tricks
- 19 Feature Requests
- 183 Community
- 38 General Discussions
- 10 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
[Regarding macOS Tahoe](Updated September 18, 2025)
We cannot guarantee the compatibility of the current releases of Live2D Cubism Editor and Cubism SDK with macOS Tahoe.
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/
We cannot guarantee the compatibility of the current releases of Live2D Cubism Editor and Cubism SDK with macOS Tahoe.
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.
Errors descriptions in logs
Hello.
As part of unofficial user support, I would like to request a more thorough elaboration of the description for errors that the user receives in case of unsuccessful export, saving and other program errors.
I often encounter banal lack of memory, problems with project resources, etc., but usually the logs are uninformative both for the average user and for me. And in the end I have to check the project file myself to find the cause. I believe that it is possible to make simpler text formulations in human language based on the received common problems.
It is clear that a certain part of the logs is needed to understand technical issues, but it is difficult for an ordinary user to navigate the web of errors.
Another example that doesn't allow you to see the picture:
For some errors there are no results other than "I am programming in Java and I encountered this error".
It's really great when there's at least text like the one in the quote below. When there's the name of the artmesh, deformer, parameter or something else that is causing the problem. And unfortunately it's still poorly written.
Why should users usually settle for vague phrases like "Scene are failed to output"? I'm sure there aren't a million reasons for things to go wrong. Most of the cases are absolutely trivial.
Please don't think that I am angry or rude in my request. On the contrary, I want the program to continue to develop successfully and make the process of troubleshooting easier. I really appreciate your efforts in developing and delivering better software. That's why I ask you to take the time to work on this important aspect.
Thank you and have a nice day.
As part of unofficial user support, I would like to request a more thorough elaboration of the description for errors that the user receives in case of unsuccessful export, saving and other program errors.
I often encounter banal lack of memory, problems with project resources, etc., but usually the logs are uninformative both for the average user and for me. And in the end I have to check the project file myself to find the cause. I believe that it is possible to make simpler text formulations in human language based on the received common problems.
It is clear that a certain part of the logs is needed to understand technical issues, but it is difficult for an ordinary user to navigate the web of errors.
Another example that doesn't allow you to see the picture:
ERROR java.lang.Throwable$WrappedPrintStream -1 println - at com.live2d.cubism.CEAppCtrl.command_exportVideo(Unknown Source)
For some errors there are no results other than "I am programming in Java and I encountered this error".
ERROR java.lang.Throwable$WrappedPrintStream -1 println - javax.imageio.IIOException: I/O error writing PNG file!
It's really great when there's at least text like the one in the quote below. When there's the name of the artmesh, deformer, parameter or something else that is causing the problem. And unfortunately it's still poorly written.
[ERROR] Exception in thread "AWT-EventQueue-0" java.lang.IllegalStateException: illegal_state : Failed to get default key form guid
Why should users usually settle for vague phrases like "Scene are failed to output"? I'm sure there aren't a million reasons for things to go wrong. Most of the cases are absolutely trivial.
Please don't think that I am angry or rude in my request. On the contrary, I want the program to continue to develop successfully and make the process of troubleshooting easier. I really appreciate your efforts in developing and delivering better software. That's why I ask you to take the time to work on this important aspect.
Thank you and have a nice day.
Tagged:
Comments
Thanks for using our products.
Your request has been shared with our development team.
Best regards.