Dear Users,

Now, we are seeking users who can give us a hand with expertise to evolve our software more dynamically.
If you are willing to help us, we’d like you to make a registration for “Live2D Creators Circle” via the link below.
Designers, programmers, translators are especially welcomed so far.
(More detailed explanation will be given to you before we ask you to do tasks)

https://docs.google.com/forms/d/1G5KK_GL3ozwPXtTHrpi_ktbsI8UZf8jlYRSlDworyBo/viewform?usp=send_form

Creating models(cubism 3 version)

I have a question why you changed the way of rendering models from one mesh to a mesh for each part of the body, because creating a game object is quite a costly action in the Unity, and now for example to change the character you need not just load a new texture and moc file, but create each part of model as when importing to a Unity, or create a game object from the created prefab, which also requires each time to create a new game object and destroy old one. Pool of objects now seems like a waste of time and can't be using in this solution now.

Comments

  • Hi,

    The person in charge of this topic is taking holidays. He will answer soon after coming back. I'm sorry for your inconvenience.

    Sincerely,
  • He has not returned from holidays yet?
    I think about solution with creating objects pool of models parts, and create each model interactive from pool, and take and returns parts of models, but want hear you person opinion
  • Hi,

    Please excuse for not getting back to you earlier. As you're pointing out, object pooling doesn't work anymore. The change was motivated to allow better Unity integration including using builtin render and animation functionalities. In prototype stage the new approach was already evaluated in real-world applications and proved to scale well. I hope this somehow explains the motivation.

    Sincerely,
Sign In or Register to comment.