Frequently Asked Questions

[Last updated: 11/25/2021]

 

Q. I imported Cubism SDK for Unity into Unity, but I get a DllNotFoundException when I insert a model.
Q. If I have multiple models in a scene, the draw call will increase. What should I do?
Q. Which platforms are supported for export from Unity?
Q. Is there a benchmark?
Q. I am a Cubism 2.x user. Should I upgrade my 2.x project to 3.x?
Q. What Unity versions are supported by the 3.0 SDK?
Q. Are there any concerns about updating a project from Unity 5.x to Unity 2017.x?
Q. Skinning physics operations do not shake as expected on the SDK.
Q. I want to make my Unity project with pre-R8 SDK compatible with Android 64bit.
Q. Can I use AnimationClip generated at runtime in Unity with Cubism SDK for Unity?
Q. Does Cubism SDK work with IE11?
Q. Copying CubismCore fails after overwrite import of Unity SDK

 

Q. I imported Cubism SDK for Unity into Unity, but I get a DllNotFoundException when I insert a model.

A. Restart Unity.

When updating a model without restarting Unity, such as when importing Cubism SDK for Unity for the first time or updating,
an error like DllNotFoundException: Live2DCubismCore will be output.

This error is caused by Unity not loading the native libraries that come with the Cubism SDK for Unity.
Unity loads native libraries at startup, so if you get this error, restart Unity and see if you get the same error.
For more information, click here 

 

Q. If I have multiple models in a scene, the draw call will increase. What should I do?

A. Use sorting layers and sorting orders to organize the order of your models.

The CubismRenderController component included with the SDK makes it easy to set sorting values.

Unity's SetPass call increases when the texture, shader, etc. of the mesh to be drawn in the scene changes.
Although it is possible to devise ways to reduce SetPass during the model creation phase, the same increase in SetPass occurs between each model.
Therefore, if the switching of textures, shaders, etc. can also be combined in all models, a reduction in SetPass calls can be expected.
Sorting layers and sorting orders are used to summarize the switching between multiple models.

For details on how to reduce switching of textures, shaders, etc., as well as points to keep in mind when creating models, please refer to “Performance of Models in the SDK” in the Editor manual.

 

Q. Which platforms are supported for export from Unity?

A. Cubism SDK for Unity currently supports the following platforms.

  Windows macOS Linux Android iOS Consumer
PlayStation®4 Nintendo Switch™
Status of support

For more information, see “Platform Support Status”.

 

Q. Is there a benchmark?

A. The Cubism SDK for Unity includes sample scenes for benchmarking, making it easy to check performance on each platform.

Native, not available on the web.

 

Q. I am a Cubism 2.x user. Should I upgrade my 2.x project to 3.x?

A. It depends on the size of the project and the duration of development and operation.
From 3.0, the SDK is not compatible with previous versions due to significant improvements in the SDK.
Cubism 2.x model data for embedded use is not compatible with the 3.0 SDK, and the Cubism 2.x SDK API is not forward compatible with the 3.0 SDK.
To use the 3.0 SDK, you will need to re-export your model data in the 3.0 Editor or upgrade the code, assets, etc. in your Unity project.
Therefore, upgrading a project should be decided after examining the benefits that both the editor and the SDK bring and the cost to upgrade.

 

Q. What versions of Unity does Cubism SDK for Unity support?

A. Our policy is to support the latest version of Unity at the time the SDK is released, so the officially supported version is Unity 2018.3 as of 3.3.
Operation with earlier versions is not supported, but may work if prefabrication, materials, etc. are reworked.

The csc.rsp and mcs.rsp files in the SDK package can be used in Unity 5.5 by changing the file names to gmcs.rsp and smcs.rsp.
For more information, please click here.

 

Q. Are there any concerns about updating a project from Unity 5.x to Unity 2017.x or later?

A. If you update your project from Unity 5.x to Unity 2017.x or later, model Prefab components that are not stored in Assets will disappear.
If you are updating a project from 5.x to 2017.x or later, please update the model on the Hierarchy with the Apply button before raising the project.

 

Q. Skinning physics operations do not shake as expected on the SDK

A. Physics calculations are affected by the input difference time (FPS).

Physics calculations depend on parameters, the state of the internal pendulum, and inputs.
The physics of skinning using a multistage pendulum model is particularly sensitive to small inputs, which can significantly affect the results of the calculations.
If you want exactly the same behavior, use the physics-baked .motion3.json file.

If the appearance in the Cubism Editor physics/scene blend settings differs from the appearance in the SDK, this may be due to the different FPS of the operation.
The current Cubism Editor is calculated at actual FPS, and the calculated FPS depends on the scale of the model and the performance of the PC on which it runs.
If you wish to refine the details of the physics operation, we recommend that you do so while checking it on the actual device.
We are planning to fix the problem that the physics calculations in the Cubism Editor have difficulty matching the behavior on the SDK, etc., in a future update.

 

Q. I want to make my Unity project with pre-R8 SDK compatible with Android 64bit

A. Please obtain and use the 64-bit compatible version of the library from the latest version of the SDK.

Cubism 3 SDK for Unity R8 and earlier does not support 64-bit Android.
To make a project created with SDK before R8 64-bit compatible, obtain the 64-bit compatible version of the Android library from Cubism SDK for Unity for R9 or later and add it to the project.
Cubism SDK for Unity's library files for 64bit-compatible Android are located in the following hierarchy.

/Assets/Live2D/Cubism/Plugins/Android/arm64-v8a/libLive2DCubismCore.so

In addition, since the Android library files included in Cubism SDK for Native are equivalent to those included in Cubism SDK for Unity, 64-bit support is also possible by using Native's 64-bit compatible version of the Android library.
The library files for the 64-bit compatible version of Cubism SDK for Native for Android are located in the following hierarchy.

/Core/lib/android/arm64-v8a/libLive2DCubismCore.a
/Core/dll/android/arm64-v8a/libLive2DCubismCore.so

If you have added a library to your project, make sure the Platform and CPU are set correctly in Inspector with that library selected.

 

 

Q. Can I use AnimationClip generated at runtime in Unity with Cubism SDK for Unity?

A. Simply using Cubism SDK for Unity as-is will not work.

AnimationClip generated at runtime cannot be played by AnimatorController or Playable API.
Therefore, Cubism SDK for Unity, which uses these functions, is also not supported.

If you are using an AnimationClip generated at runtime, it is possible to make it play by using Unity's Animation component.
However, the “MotionFade” feature of Cubism SDK for Unity does not support motion playback by the Animation component.
This can be handled by not using MotionFade or by customizing the SDK source on the user side.

MotionFade in Cubism SDK for Unity requires the fade to be processed as the motion plays back, and monitors the motion playback state.
In Cubism SDK for Unity, CubismFadeStateObserver and CubismMotionLayer monitor the playback state.
This can be handled by implementing a component on the user side that monitors the playback state of the Animation component.
The component that monitors the playback state of the motion implements ICubismFadeState.

 

Q. Does Cubism SDK work with IE11?

A. Cubism SDK for Web has been tested with IE11 and is supported.

Cubism SDK for Unity depends on the browser supported by Unity, but IE11 may be deprecated or disabled.
See the official Unity reference for more information.

 

Q. Copying CubismCore fails after overwrite import of Unity SDK

A. Restart Unity with an empty scene or a scene not using the Cubism SDK open.

The Cubism Core in the Cubism SDK for Unity cannot replace the Cubism Core used on the editor because it is referenced by Unity when used in a scene.
To reset the Cubism Core reference, restart Unity with a scene open that does not use Cubism Core (empty scene, etc.).

 

© 2010 - 2022 Live2D Inc.