UE5.0.3 creates an assertion while adding unweighted bones to a metahuman about tttoolbox HOT 8 CLOSED

I tested the latest state of the unweighted feature branch with 5.0.3

Mixamo character seems still to work fine

Quoted from: https://discord.com/channels/671128082110742561/762949358417084426/997011808697196607

from tttoolbox.

MetaHuman Hudson worked so far as well

Adding sockets and virtual bones with TTToolbox seems to work as well.

from tttoolbox.

Hmmm... I need the exact same MetaHuman and the exact steps that were used to create the issue. I can not reproduce the issue locally on my machine. 😞

Wondering a little bit if the user had already added the virtual bones. 🤔

I do have the following questions for lAKKWHY:

1. Which exact steps were used to reproduce the issue?
2. Which MetaHuman is used that creates the assertion (it prevents a crash but sadly still closes the editor)?
3. Are the virtual bones already added to the skeleton asset of the MetaHuman?

from tttoolbox.

I'm getting this issue when I add the required virtual bones for ALS and then try to add the unweighted bones that I get this assertion as well.

Well... That is super sad!!!

if (!Skeleton->AddNewVirtualBone(SourceBoneName, TargetBoneName, newVirtualBoneName))

https://github.com/tuatec/TTToolbox/blob/master/Source/TTToolbox/Private/TTToolboxBlueprintLibrary.cpp#L153
Has an silent error if the source or target bone do not exist in the skeleton asset the virtual bones will be added to the asset without an error. And later I'm not able to open the skeleton asset again. 🙈

@ lAKKWHY
Please remove the virtual bones and try again.

from tttoolbox.

Hello here @ lAKKWHY
i,m using HANA metahuman.
I uploaded a video on discord channel https://cdn.discordapp.com/attachments/762949358417084426/997050379265130537/2022-07-14_13-25-54.mkv
Virtual Bones added but not working showing in Metahuman character. you can see in video.
Editor is not crashing when i recorded this video, because unweighted bones already exists i think!!

here is image of

from tttoolbox.

I added some fixes to this issue in the unweighted bones feature branch, see #2 (comment). In my case it fixed the wrong bone index access. Details can be found here, #2 (comment).

from tttoolbox.

OK I'm checking

from tttoolbox.

For me the issue was resolved, which is the reason why I now close this ticket here. If you still have the issue feel free to reopen and we will have a look at it again. 😉

I wish you all the success within your character integration journey. 💪

from tttoolbox.