Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Happy to over context!
It all depends on how you configure the avatar settings in the two apps, and/or in the editor if you imported your model in Animaze via the Animaze Editor.
You can configure it to work normally.
You can also configure it to behave as you describe above.
In the Import process, if you go via the editor, if you are a power user you also have a "VMC body retargeting" configurator, that allows you to decide which bones in your custom model, correspond to which standardized ones from a VRM skeleton sent in via VMC, if not identical. If that is enabled, not set up correctly it can break things so perhaps that's what's happened here?
We have tested with XR animator too, and several other VMC software, so have some of our Discord users, and the test went okay.
It is useful at first to use the same VRM file loaded in both apps until you learn the ropes.
If you see differences, send us the file and a video at support[@]animaze[.]us and context on which specific XR animator version and Animaze version (animaze.log from that session) you were using at that time.
XR animator uses the Unity engine, and its VRM importer is a ready-made VRM plugin for Unity.
Animaze wishes to keep you more independent from larger corporations, and to do so it uses an indie engine, and its VRM importer is written in-house.
There could be some edge cases on a VRM file, that are treated differently by Unity VRM import plugin, and by our indie import plugin, so the files with edge cases can end up imported differently.
If there is a problem that goes beyond "tweaking the settings" with custom VRM files (that were put together manually vs exported by a highly standardized software platform like Vroid Studio, that makes sure the VRM files are 100% up to spec), then that (non-standard aspects of the VRM file) is a bit more likely to be the cause here, than anything related to the VMC animation protocol itself.
The implementation when it was done was also submitted and validated by the VMC creator team, on their Discord, and was approved, listed on their website, and everything :).