Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optionally prefer Body over viseme mesh during merging #74

Closed
wants to merge 1 commit into from

Conversation

Fraxul
Copy link
Contributor

@Fraxul Fraxul commented Jan 27, 2024

This new setting handles the case where the avatar has a Body mesh and a separate viseme mesh that need to be merged together, and you want the merged output mesh to be called Body for MMD world compatibility.

It's a bit of an edge case, sure, but at least it's not much code to support.

This handles the case where the avatar has a Body mesh and a separate
viseme mesh that need to be merged together, and you want the merged
output mesh to be called Body for MMD world compatibility.
@d4rkc0d3r
Copy link
Owner

I vaguely remember that I gave the viseme mesh priority because it had issues if it got merged into another mesh. Idk if I resolved those bugs or rely on the sorting.

If the bugs don't exist anymore I don't see why I would even need an option for this and not just make it default behavior to merge into "Body".

@d4rkc0d3r
Copy link
Owner

There was indeed a bug that had to be fixed but it should now always merge into the mesh Body if it exists in a merged mesh blob.

@d4rkc0d3r d4rkc0d3r closed this Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants