New unloading models !

[hboxgames]

Here goes couple models that have problems with the last version (win64_1.1.0.305)

Although I'm using it the version before, since I don't want to remake all the material settings (really hope this can be solved somehow...) but I still thought it would help to let you know.

So there are 2 models that kinda have their dynamic parts like hairs that stays at 0
And a model that simply doesn't move from t pose
https://we.tl/t-3sGmmtjt89

Thanks for the great features always and good luck !

[alloystorm]

Will check those models. Thanks.

[alloystorm]

Merging the issue with "MMD Bulma DBS bunny" model here.

[alloystorm]

The problem with "Android 18" is the same with the Bulma model, one of the morphs is causing an error.

The issue with Lux Rift is that it's missing Leg and Knee bones which are required.

[hboxgames]

I see !
So I guess for LUX it's a maker problem, and for the morphs, you seem to be able to solve but looking for general fix ?
(How can I get temp fixed bulma and androids btw ?)
Thanks !

[alloystorm]

In the next version we'll make it to ignore the morph error (Android 18 and Bulma) so it won't crash. For now it seems there is no way to bypass it in the current version unless you want to edit the model and remove the morph that is causing the problem. It seems one of the morph group is referencing a morph that doesn't exist.

For Lux Rift it'll require someone to edit the Leg and Knee bones to the standard names.

[hboxgames]

I see ! Well it's normal that the app can't fix and react correctly if the problem is on the models ! If making it ignore the morph errors helps it could be great for glitchy models indeed. Don't worry for the Lux one, again I guess it's more about the model being buggy on this one ! Thanks ! 2021년 11월 14일 (일) 오전 1:39, alloystorm ***@***.***>님이 작성:

…

In the next version we'll make it to ignore the morph error (Android 18 and Bulma) so it won't crash. For now it seems there is no way to bypass it in the current version unless you want to edit the model and remove the morph that is causing the problem. It seems one of the morph group is referencing a morph that doesn't exist. For Lux Rift it'll require someone to edit the Leg and Knee bones to the standard names. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#144 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASF4NBWRAS2HYSNT2JCZ3ATUL4ALLANCNFSM5FDBR2CA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[alloystorm]

Added alternative bone names in 1.1.3, should now support Lux Rift and similar models. Also the morph issues with Android 18 and Bulma are now handled, they will not prevent the model load anymore.

[hboxgames]

Oh wow thankx ! 2021년 12월 2일 (목) 오전 12:12, alloystorm ***@***.***>님이 작성:

…

Added alternative bone names in 1.1.3, should now support Lux Rift and similar models. Also the morph issues with Android 18 and Bulma are now handled, they will not prevent the model load anymore. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#144 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASF4NBQIJQALRIVEYRHIAXLUO2TWNANCNFSM5FDBR2CA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.