Texture loading error

Some textures don't load properly and some areas of workspace don't click. Export is possible, but some textures don't output normally.

- Live2D Software Version: Cubism Editor 5.3.00
- OS & Version: Windows 10
- Graphics Specifications: GeForce RTX 4060Ti
- CPU: Intel Core i7-12700F
- Memory: 64GB
- Illustration Software used: ClipStudio
- log file : https://drive.google.com/file/d/1dLtqTrmO5vKeo2wDNdxeqwMhSyQsImYT/view?usp=sharing
Tagged:

Comments

  • Hi @jin11

    Thank you for using our product.

    Please store the model file you are experiencing issues with in the data box below.
    https://biz.datadeliver.net/posts/mshQMn6GlQ9p

    Please note that this data box will only be made available to the development team.

    Thank you for your cooperation.
  • edited January 29
    I uploaded the file, please check it!
  • Hi @jin11

    We apologize for the delay in our reply.

    After investigating, we found that there appears to be an issue with several ArtMeshes called [반짝이6].

    The issue is occurring because the model image for ArtMesh589, ArtMesh594, ArtMesh602, ArtMesh610, and ArtMesh617 is not being referenced correctly. Deleting these five ArtMeshes resolved the error.

    We tried [Set as input image for selected ArtMesh] from the model image in the Project Palette, but this did not improve the situation, so it is recommended that you recreate the problematic ArtMeshes.

    The cause of this issue is unknown, but we suspect [반짝이6] was created by duplicating.

    If you remember what operations you performed to create these ArtMeshes, please let us know.

    In addition, for models with errors, the [Create ArtMesh for collision detection] command may not be properly reflected in the Parts Palette, and other operations may not be performed correctly.
    After taking the above steps, it would be a good idea to save the file under a different name and try again just to be on the safe side.

    Thank you in advance.
  • I've used the auto mesh creation feature. Thanks for the help!
  • Hi @jin11
    Thank you for reporting the procedure.

    However, we were unable to reproduce the issue in our environment.
    Please let us know if you encounter any further problems using similar procedures.
Sign In or Register to comment.