[DiscordArchive] Interesting, I'll investigate.
[DiscordArchive] Interesting, I'll investigate.
Original source
Interesting, I'll investigate.
For blizzlike models the ordering is actually saved on import. Any idea of how to solve that ?
rektbyfaith
08-16-2022, 06:57 PM #1Archived author: Titi • Posted: 2022-08-16T18:57:35.318000+00:00
Original source
Interesting, I'll investigate.
For blizzlike models the ordering is actually saved on import. Any idea of how to solve that ?
Original source
A temporary solution could be to ignore this restriction, or if this parent bone error appears, simply set the parent to -1 for the offending bone and require manual reapplication for now
This seems to work pretty consistently
rektbyfaith
08-16-2022, 07:01 PM #2Archived author: Cyn • Posted: 2022-08-16T19:01:56.279000+00:00
Original source
A temporary solution could be to ignore this restriction, or if this parent bone error appears, simply set the parent to -1 for the offending bone and require manual reapplication for now
This seems to work pretty consistently
Original source
The real solution isnt really with WBS, in a perfect world i would completely redo the bone index to be ordered correctly
rektbyfaith
08-16-2022, 07:02 PM #3Archived author: Cyn • Posted: 2022-08-16T19:02:45.545000+00:00
Original source
The real solution isnt really with WBS, in a perfect world i would completely redo the bone index to be ordered correctly
1 Guest(s)
1 Guest(s)