You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: