Framework initialization and termination (Java)

[Last update: 10/06/2022]

Cubism SDK for Java is currently in alpha version, and the specifications may change in the beta or official version.



Set logging-related options in the CubismFramework.startUp function.
Without calling this function, the CubismFramework.initialize function to be performed later will not work.


The argument registers the level of debugging and the function to be debugged.
During initialization, Cubism Core version information is displayed via debugging functions as shown below.




After executing the CubismFramework.startUp function, call the CubismFramework.initialize function.
Always call it once before using the Framework in your application.
If it is never called, an error will occur when using the Framework.
If called in succession, the process is ignored.
However, after calling the CubismFramework.dispose function (described below) and exiting, the initialize function can be called again to initialize it.




Calling the CubismFramework.dispose function releases the common part resources allocated by the Framework.
Do not call this function before calling CubismFramework.initialize function.
Basically, it is called when the application is terminated.
The exception is in very low memory environments, when you don't need or want to completely disconnect the library,
you can call this function to release the resource, and then call the CubismFramework.initialize function again the next time you use it.

© 2010 - 2022 Live2D Inc.