Categories
- All Categories
- 1.3K Cubism Editor
- 1.1K Help
- 56 Tips and Tricks
- 160 Feature requests
- 1 Cubism Editor 5.3 alpha
- 1 Download
- Reporting bugs about new features/Feedback
- Other Bugs
- 50 Other Live2D Products and Tools
- Cubism Viewer (for OW, for Unity)
- 3 Material Separation Photoshop Plug-in
- 47 Other Live2D Products and Tools (Other Photoshop Scripts, Sample Data, etc.)
- 274 Cubism SDK
- 246 Help
- 11 Tips and Tricks
- 17 Feature Requests
- 17 SDK for Unreal Engine alpha
- 5 Download
- 1 Manual and Update History
- 11 Bug
- Feature Request
- 182 Community
- 38 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
Problem with export/update of Texture Atlas
Hello!
I am having a problem with exporting the model I am currently working on (texture atlas files in particular).
- Live2D Software Version: Cubism Editor 5.1.03 and 5.2.02
- OS & Version: Windows 10 Pro
- Graphics Specifications: Nvidia GeForce GTX 1070
- CPU: AMD Ryzen7 2700X 3.7GHz
- Memory: 32GB
TLDR:
Update texture atlas process takes several hours. It then causes the program to freeze on 5.1.03 and though it doesn't freeze on 5.2.02 it still doesn't seem to update the atlas correctly, as it doesn't export any textures when exporting the moc3 file. Manually exporting the texture image throws a Null error.
Full description of the problem with all Info I can provide:
I have worked on this model mostly in Cubism 5.1 and was able to successfully export the model (including texture files) before, to test the eye and mouth rigging. When I was done with the head angle and hair rigging (still all done in 5.1), I updated to 5.2 and proceeded with the next rigging steps. At this point I wanted to export the model to test my progress in Vtube Studio. Since I added toggles and had to include some previously invisible textures to the texture atlas, I proceeded to initialize the texture atlas with all textures and pressed the “OK” button for it to update the textures. After the normal loading bar it seemingly got stuck at the “updating” phase. I retried it multiple times with different texture resolutions, multiple textures, restarting program and pc etc.
At some point I just let it run and it took over 4 hours(!) until it was “done” - the loading bar and the texture atlas window disappeared. Assuming it had successfully updated the textures I exported as moc3 file. The progress took another 2 hours before it saved the moc3, but it didn't export the texture atlas folder with it. I tried this multiple times and it gave me an error message that mesh ID xxx is not placed in the texture atlas, while it would always show a different ID on each try. It must have somehow failed updating the textures. Though, the “Edit Texture Atlas” window shows the reinitialized/updated textures with all the textures included. When I tried to use the “Export Texture Image(Beta)” function it threw a “Null” error.
The next day I decided to roll back and reinstalled Cubism 5.1.03. On a backup file of the model from 5.1.03 - I tried updating the texture atlas. At first it went similar: It stayed at the same “Update TextureAtlas progress bar for over an hour, then the progress bar and texture atlas windows closed. However, the program seems to have frozen, as it doesn't react to any click or input. When minimizing and opening the program again it is a completely blank white window. It shows the same behaviour on multiple tries.
Some additional Info: I monitored the hardware usage since I suspected it running into memory problems. As expected my CPU and GPU where taking a nap from boredom. While the Ram usage spiked when opening the texture atlas window and during the “Update TextureAtlas” process – it never exceeded 26 GB usage of 32 GB, even with other tasks running in the background at the same time. The Ram usage of Cubism floated around 18GB.
I also tried increasing the maximum Ram usage threshold in the config file, since this solved issues for some people. Unfortunately it did not make any difference to my systems Ram usage or the problem described above.
I have several log files and my model files ready to share.
The model is for a client and my desperation and frustration is immeasurable right now...
I would be incredibly grateful for any help or ideas what I can do to fix this problem!
Thank you for your kind attention and best regards,
avi
I am having a problem with exporting the model I am currently working on (texture atlas files in particular).
- Live2D Software Version: Cubism Editor 5.1.03 and 5.2.02
- OS & Version: Windows 10 Pro
- Graphics Specifications: Nvidia GeForce GTX 1070
- CPU: AMD Ryzen7 2700X 3.7GHz
- Memory: 32GB
TLDR:
Update texture atlas process takes several hours. It then causes the program to freeze on 5.1.03 and though it doesn't freeze on 5.2.02 it still doesn't seem to update the atlas correctly, as it doesn't export any textures when exporting the moc3 file. Manually exporting the texture image throws a Null error.
Full description of the problem with all Info I can provide:
I have worked on this model mostly in Cubism 5.1 and was able to successfully export the model (including texture files) before, to test the eye and mouth rigging. When I was done with the head angle and hair rigging (still all done in 5.1), I updated to 5.2 and proceeded with the next rigging steps. At this point I wanted to export the model to test my progress in Vtube Studio. Since I added toggles and had to include some previously invisible textures to the texture atlas, I proceeded to initialize the texture atlas with all textures and pressed the “OK” button for it to update the textures. After the normal loading bar it seemingly got stuck at the “updating” phase. I retried it multiple times with different texture resolutions, multiple textures, restarting program and pc etc.
At some point I just let it run and it took over 4 hours(!) until it was “done” - the loading bar and the texture atlas window disappeared. Assuming it had successfully updated the textures I exported as moc3 file. The progress took another 2 hours before it saved the moc3, but it didn't export the texture atlas folder with it. I tried this multiple times and it gave me an error message that mesh ID xxx is not placed in the texture atlas, while it would always show a different ID on each try. It must have somehow failed updating the textures. Though, the “Edit Texture Atlas” window shows the reinitialized/updated textures with all the textures included. When I tried to use the “Export Texture Image(Beta)” function it threw a “Null” error.
The next day I decided to roll back and reinstalled Cubism 5.1.03. On a backup file of the model from 5.1.03 - I tried updating the texture atlas. At first it went similar: It stayed at the same “Update TextureAtlas progress bar for over an hour, then the progress bar and texture atlas windows closed. However, the program seems to have frozen, as it doesn't react to any click or input. When minimizing and opening the program again it is a completely blank white window. It shows the same behaviour on multiple tries.
Some additional Info: I monitored the hardware usage since I suspected it running into memory problems. As expected my CPU and GPU where taking a nap from boredom. While the Ram usage spiked when opening the texture atlas window and during the “Update TextureAtlas” process – it never exceeded 26 GB usage of 32 GB, even with other tasks running in the background at the same time. The Ram usage of Cubism floated around 18GB.
I also tried increasing the maximum Ram usage threshold in the config file, since this solved issues for some people. Unfortunately it did not make any difference to my systems Ram usage or the problem described above.
I have several log files and my model files ready to share.
The model is for a client and my desperation and frustration is immeasurable right now...
I would be incredibly grateful for any help or ideas what I can do to fix this problem!
Thank you for your kind attention and best regards,
avi
Tagged:
Comments
Thanks for using our products.
Please store the model file that is causing the problem in the following data box so we can investigate.
https://biz.datadeliver.net/posts/cYWzkg6lkxSg
Best regards.
Hello Ookubo,
I have uploaded the model files into the databox. Thank you for looking into the problem and please let me know if there is anything else I can do!
Best regards,
avi
Thanks for sending me the data.
We are working on your data, but we will need a little more time.
Best regards.