[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.[SDK] I got an error message like that "Buffer Validation Cannot create buffer of zero length."
Hello
While testing several models for our app, we encountered the following error during the initialization of model:
-[MTLDebugDevice newBufferWithLength:options:]:642: failed assertion `Buffer Validation
Cannot create buffer of zero length.`
Coming from the lines:
(CubismComandBuffer_Metal)
Line 89
_vertices = [device newBufferWithLength:_vbStride * count
options:MTLResourceStorageModeShared];
(CubismRenderer_Metal)
Line 1310
const csmInt32 drawableVertexCount = model->GetDrawableVertexCount(i);
Line 1317
_drawableDrawCommandBuffer[i]->CreateVertexBuffer(device, vertexSize, drawableVertexCount);
We tried the models in frameworks CubismSdkForNative-4.r.7 and CubismSdkForNative-5.r.1-beta.3 both in the demo app and in our app and both resulted in the mentioned error. (Simulator and real device)
The target model can be downloaded via
https://ko-fi.com/s/867102f774. It's free.
This issue is caused by value 0 from "model->GetDrawableVertexCount(i)" some value of an array on a certain index has value 0. I was wondering if it's normal that the array contains zeros sparsely. We found the workaround to return 1 instead of 0 to resolve it. That's working now, but I am afraid that it's the right approach.
As mentioned again to be clear, it occurs on the demo app for native provided by Live2D.
Thank you in advance.
0 ·