Thanks! One heads-up though — development is wrapping up (see the announcement),
so even with a sample I may not be able to fix avatar-specific issues.
Feel free to send it anyway, but no promises!
Hello! Thank you for the kind words and the detailed report — and no worries at all about the translation.
We're investigating this. Two things could be going on: the multi-avatar build has a long stage where the progress display doesn't update at all (so it can look frozen while still working), but with about 10 models combined it may instead be hitting an internal size limit and failing without showing any error.
To tell which one it is, we need the log from your machine: after trying the build, please press the app's inquiry button (it has a Copy Log feature) and send it through the in-app form — that gives us everything we need to fix this.
Thanks for your patience
Hi, thanks for the report, and sorry for the trouble!
To be upfront: the current converter doesn't support transparent (alpha) materials — any part of a model that's meant to be see-through (like glasses lenses) will currently render as solid/opaque instead. That's a known limitation on our side, not something wrong with your avatar or how you converted it.
As a workaround, you can use the Lab feature's "Delete Mesh" tool (open the tool's main window -> Lab -> Delete Mesh) to remove fully-transparent meshes such as glasses lenses from the conversion entirely, so they don't show up as opaque blocks.
For the texture issue, we'd need a diagnostic log to tell whether it's on our side or specific to your model — could you submit a report through the in-app "Inquiry" (問い合わせ) form after a conversion attempt? It automatically attaches the log, which helps us pinpoint the cause much faster than a description alone.
We're looking into proper transparency support, though we can't promise a timeline yet. Thanks again for your patience!
Thank you very much for the kind words, and for using Uchinoko for Palworld.
Glad to hear that exporting as VRM worked around the root bone issue.
Regarding being able to replace only one specific body type: this is helpful feedback, and we will keep it in mind as a possible improvement.
Regarding physics: this is already something we are looking into, so please bear with us for now.
Hi JtheDuelist, thank you for the report, and I'm sorry for the trouble.
A new version (v2.2.13) went live a few hours after your comment. It has a restructured, single-executable package that is not flagged in my testing — I've also added a pre-release antivirus scan and periodic automated re-checks of the published files. Could you give v2.2.13 a try (itch or GitHub, both are updated)?
If it still gets blocked on your machine, please let me know the threat name Windows Defender shows — that would help a lot. A proper code signature is in preparation as the fundamental fix.
Thank you for the report, and I'm sorry it took me this long to reply —
and sorry for the trouble in the first place.
There's a new build on the page now, and it downloads and runs normally on
my machine. Please give it another try.
If it still gets flagged for you, there's a second, older file on the page
that should download cleanly.
Sorry again for the hassle, and thanks for flagging it.