Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
In the meantime, I've been using the Live2D Motion command instead of expressions - those seem to be MOSTLY accurate (though I have noticed some inconsistencies which may or may not be user error).
But if others are having this same issue, I'd say it's a bug. Perhaps the devs can test this?
I can't seem to get any motions I create to work either. They show up in VNM's "select motion' screen, although they don't activate when I use either the motion, or motion group command.
Would you be able to post an image of the animator view of one of your motions? Or a screen grab of your output settings from the viewer?
*EDIT*
I have motions working now
After making and exporting expressions from the Live2D 2.1 viewer. Manually open each expression file and substitute in an additional suffix for each parameter. As follows:
This is what parameters will look like:
{"id":"PARAM_ANGLE_Y","val":12.72}
This is how they need to look:
{"id":"PARAM_ANGLE_Y","val":12.72,"calc": "set"}
I would be very interested to know if this even is a problem that other people have encountered, or if it's some dumb thing i've done.
Thanks for your help.