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

[Feature Request] Persistent Paths from Path Deformations #67

Open
2 tasks done
Richardn2002 opened this issue Sep 28, 2024 · 0 comments
Open
2 tasks done

[Feature Request] Persistent Paths from Path Deformations #67

Richardn2002 opened this issue Sep 28, 2024 · 0 comments
Labels
Enhancement New feature or request Triage PR/Issue needs to be triaged.

Comments

@Richardn2002
Copy link
Contributor

Validations

  • I have checked for similar feature requests and could not find any.
  • I have made sure this is not an already-existing feature.

Description

Currently, path deformation is merely a meshing tool, destructive by directly modifying the meshes under edit. However, users may want to return later to continue adjusting paths, or even animate the paths for the corresponding animation.

Suggested solution

  • Extend the puppet file format to permanently store path info and parameter bindings.
  • Connect parameters to paths.
  • Decide on potential ordering and collision among multiple deformation sources, including multiple paths (if multiple is supported), meshgroups and the basic deformations of meshes.
  • Render puppets according to stored paths.

Alternative solution

Some also argue that the above features requested may be achieved by the upcoming bone system. The details of the bone system are unclear at this point, but by instinct, for example, using paths to animate lips and using bones to animate limbs, feel like different processes.

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request Triage PR/Issue needs to be triaged.
Projects
None yet
Development

No branches or pull requests

1 participant