You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. I am using an asset that moves the breast in the booth.
This asset uses the Normalized Blend Values feature of Direct Blend Tree, and when I apply d4rkAvatarOptimizer to the avatar, the Normalized Blend Values setting is turned off, causing problems.
The AvatarOptimizer made by anatawa12's previously had the same problem, and it was caused by making it without considering Normalized Weights. Related Content
Can you please check if the avatar is optimized according to the Normalized Blend Values option status for Direct Blend Tree?
Constraints
The avatar was downloaded from the booth and no modifications were made to it.
The only new component added to the avatar was d4rkAvatarOptimizer.
There were no issues when using Anatawa12's Avatar Optimizer with VRCFury, add d4rkAvatarOptimizer, the issue occurs.
This is the FX layer in Play Mode. You can see that Normalized Blend Values is turned off.
Since the issue persists even with all options disabled, it seems like the underlying processing is causing the issue.
The text was updated successfully, but these errors were encountered:
Hello. I am using an asset that moves the breast in the booth.
This asset uses the
Normalized Blend Values
feature of Direct Blend Tree, and when I apply d4rkAvatarOptimizer to the avatar, the Normalized Blend Values setting is turned off, causing problems.The AvatarOptimizer made by anatawa12's previously had the same problem, and it was caused by making it without considering Normalized Weights.
Related Content
Can you please check if the avatar is optimized according to the Normalized Blend Values option status for Direct Blend Tree?
Constraints
This is the FX layer in Play Mode. You can see that Normalized Blend Values is turned off.
Since the issue persists even with all options disabled, it seems like the underlying processing is causing the issue.
The text was updated successfully, but these errors were encountered: