search

Yellow-Dog-Man / Resonite-Issues

Issue repository for Resonite.
https://resonite.com
134 stars 2 forks source link

DynamicBlendShapeDriver ends up disabling itself and causing an exception if one blendshape is not filled in. #2408

Open ModernBalloonie opened 2 months ago

ModernBalloonie commented 2 months ago

Describe the bug?

image If one blendshape doesn't match up with the naming here, the entire component disables itself.

image Here are the drives that are null, because I don't have those blendshapes on the mesh.

If i get rid of those null drives... image the component works fine.

To Reproduce

Get a mesh with some blendshapes.

Try to drive it with the DynamicBlendShapeDriver

Type one of the blendshape names wrong, and type one of them right.

The ones with wrong names will cause the component to have an exception.

Expected behavior

For the component to work for the shapes it had found, even if some drives are not filled in.

Screenshots

Included earlier.

Resonite Version Number

Beta 2024.6.25.1149

What Platforms does this occur on?

Windows

What headset if any do you use?

Desktop, Quest Pro

Log Files

DESKTOP-QBGCSAQ - 2024.6.25.1149 - 2024-06-26 14_14_13.log

Additional Context

This bug is even detailed on the Resonite Wiki page for the DynamicBlendShapeDriver. https://wiki.resonite.com/Component:DynamicBlendShapeDriver

Reporters

ModernBalloonie

ModernBalloonie commented 2 months ago

image Looking at the log, here's one of the exceptions.

ModernBalloonie commented 2 months ago

Interesting tidbit I found. Seems like if I null the mesh renderer field after putting the mesh in, I can enable it and the drives work, however when the mesh is put in the renderer field, the component disables itself.

BlueCyro commented 2 months ago

I've fixed this, just waiting on the internal PR