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

Save genetated blendtrees as .assets #17

Open
ZenithVal opened this issue Feb 28, 2023 · 2 comments
Open

Save genetated blendtrees as .assets #17

ZenithVal opened this issue Feb 28, 2023 · 2 comments
Assignees

Comments

@ZenithVal
Copy link

Currently the blendtrees only exist within the animator, it would be nice if they were generated as dedicated assets.
It'd make it possible for users to merge this into pre-existing direct blendtree setups.

@regzo2
Copy link
Owner

regzo2 commented Mar 26, 2023

While I think giving users the ability to create the BlendTree asset outside of the selected animator container for OSCmooth would be nice, I am concerned about the user-oriented side of this option. The blendtree is generated a certain way based on a lot of contexts of the animator it will eventually be built into, with write-defaults being the biggest concern. If OSCmooth blendtrees weren't so volatile I would be tempted to have the asset exported into a .asset as the defacto functionality.

This is a similar concern with other features such as from this fork, wherein the feature specifically is a little beyond what I had originally architected OSCmooth to be for. I think there is a place for these features but I would want the user to be aware of them. I've thought about having an OSCmooth settings tab or window that would let you enable experimental or 'dangerous' features, and this would definitely be where I would have something like this with user acknowledgement.

@regzo2 regzo2 self-assigned this Nov 24, 2023
@regzo2 regzo2 linked a pull request Nov 24, 2023 that will close this issue
@regzo2 regzo2 removed a link to a pull request Jan 6, 2024
@regzo2
Copy link
Owner

regzo2 commented Jan 6, 2024

will work this into a future version

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

No branches or pull requests

2 participants