Home› Help

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Sign In Register

Categories

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.

Export .Moc error with [INFO ] Texture Atlas does not contain: [ERROR] java.util.NoSuchElementExcep

PisitPisit
in Help
Environments:
- Live2D Software Version: (e.g. Cubism Editor 4.2.00)
- OS & Version: Windows 10
- PC Model: HP OMen 15-dc1xxx
- Graphics Specifications:GeForceRTX2060
- CPU: (e.g. Intel Core i7-8750H)
- Memory: 32GB
- Illustration Software used: Photoshop
- Attach screenshot or capture video to show your problem: - screenshot attached

Currently, I have a model which can be exported properly. After adding a new hiding feature for a hand, I cannot export the model as it shows saving but I got only an empty folder. The log report as such:

[INFO ] locked : false
[INFO ] locked : false
[INFO ] ????????? ??? : true
@TexRelocDialog
[WARN ] setupTexture : # 143.000 MB Increased
[INFO ] Texture Atlas does not contain:
[ERROR] java.util.NoSuchElementException
[ERROR] at java.util.ArrayList$Itr.next(Unknown Source)
[ERROR] at com.live2d.cubism.doc.model.exporter.CDisplayInfoJsonParser.a(Unknown Source)
[ERROR] at com.live2d.cubism.doc.model.exporter.CDisplayInfoJsonParser.a(Unknown Source)
[ERROR] at com.live2d.cubism.doc.model.exporter.b$a.a(Unknown Source)
[ERROR] at com.live2d.cubism.doc.model.exporter.b$a.a(Unknown Source)
[ERROR] at com.live2d.cubism.doc.model.exporter.f.a(Unknown Source)
[ERROR] at com.live2d.cubism.doc.model.exporter.f.invoke(Unknown Source)
[ERROR] at com.live2d.util.ad.a(Unknown Source)
[ERROR] at com.live2d.util.af.run(Unknown Source)
[ERROR] at java.lang.Thread.run(Unknown Source)


Early inspection: I create texture atlas already and nothing seem to be wrong. If there is any suggestion regarding the issue , please give me some advice T T/

Screenshot:
For my texture atlas: https://drive.google.com/file/d/1L-z50ZcDuW-iPdM41cXNp4pZ2VzzJWB7/view?usp=sharing
For editor with log error: https://drive.google.com/file/d/1gMFdqUURhexIsQjGp07GRbFDtS4LoWt3/view?usp=sharing
· Share on Facebook

Comments

  • Enoko(Staff)Enoko(Staff)
    @Pisit

    Thank you for your continued use of our product.
    We apologize for any inconvenience caused.

    Is your situation like this?
    - Originally this model was modeling and exporting without any problems.
    - However, when I tried to export again after hiding the hand parts, an error occurred and the export could not be performed correctly.

    Please send us the following files.
    - Log file
    Please refer to this page for information on how to obtain the log file.
    https://help.live2d.com/en/other/other_22/
    - CMO3 file

    Please upload the files to this upload page.
    https://biz.datadeliver.net/posts/wLWr6T4RvWVS

    Best regards!
    · Share on Facebook
  • PisitPisit
    @Enoko(Staff)

    Dear Enoko,

    I have the situation as described in your reply.

    As advised, the zip file including model and log extracted from given guide have been uploaded to the given link.

    Thanks for helping T T9.
    · Share on Facebook
  • Enoko(Staff)Enoko(Staff)
    @Pisit

    Hello Pisit,
    Thank you for providing the files.
    I was able to receive and check the contents.

    The CMO3 file may have become corrupted.
    Please stop the modeling work on this file.

    Open the automatic backup folder and look for the normal model file just before it was corrupted.
    (https://docs.live2d.com/en/cubism-editor-manual/autosave/)
    If you can retrieve the normal model file just before it was corrupted, please send it to us.

    Please upload the files to this upload page.
    https://biz.datadeliver.net/posts/wLWr6T4RvWVS

    We apologize for any inconvenience caused.
    We will investigate in detail.
    We hope you will wait for a while.
    · Share on Facebook
  • ueno(staff)ueno(staff)
    Hello, @Pisit .
    This is Live2D Support.

    We have repaired the model file, please check back.
    We will continue to investigate the cause of this problem.

    Please download the file from below.
    The password is the file name of the cmo3 file you sent us.
    http://dtbn.jp/OsAYBKNR

    We apologize for any inconvenience caused.
    We thank you for your continued support of Cubism Editor.
    · Share on Facebook
  • PisitPisit
    Dear @ueno(staff) and @Enoko(Staff)

    Thanks you for the supports. Our team simply worked on other characters so the late reply from us. We sincerely appreciated for your help T T9. Now we can continue working on this character.

    Love Live2D support, very reliable.
    Regards.
    · Share on Facebook
  • Enoko(Staff)Enoko(Staff)
    @Pisit

    Thank you for your continued patronage of our products.

    The bug you reported has been addressed in the latest version, 5.2.00 beta1.
    The issue was caused by a bug that caused parameter binding to become internally invalid.
    We apologize for any inconvenience caused.

    We hope you will continue to support our products.
    · Share on Facebook
Sign In or Register to comment.