-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add point-based frame definition support to the mesh importer #802
Comments
This has been delayed because There are a few outstanding issues with the implementation - namely, that it has issues with chained Once those are merged upstream, I have already verified that OSC will be able to use them essentially immediately by building a branch of OSC against those patches: So the downstream integration steps of putting frame-definition support into the model editor should be more-or-less done. Adding it into the mesh importer is a separate concern, but will require separate engineering step (some are done against this issue) in order for that to work. |
Similar to how the specialized "Frame Definition"
framedefs.toml
, for warping workflows.oscmis
, rather thanosim
, if the user wants the software to actually remember the edges etc (atm, it'll bake anosim
file, which isn't quite right)The text was updated successfully, but these errors were encountered: