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
This issue just covers a feature implementation for the feature request from InquisitorSource5
A few use cases for this feature would be:
Capes with bones attached to the shoulders
Grabbing bones
An implementation of such a feature would be as follows:
Object value under bone called "SmartWeld" this would point to an attachment that the bone should attach to
Create a new constraint which just forces the bones position to be at a specified location
At the start of each frame check for a SmartWeld object and check if the attachments position has changed, If so update our internal bone data to reflect that
Pass that data to the weld constraint which would then force the bones location
If you have any other ideas on such an implementation feel free to share.
The text was updated successfully, but these errors were encountered:
Final implementation was decided as, SmartWeld object which can reference an attachment, bone or basepart. It can have an attribute called "Rigid" which controls wether it should use a spring or just set the bones position, commit soon.
This issue just covers a feature implementation for the feature request from InquisitorSource5
A few use cases for this feature would be:
An implementation of such a feature would be as follows:
Object value under bone called "SmartWeld" this would point to an attachment that the bone should attach to
Create a new constraint which just forces the bones position to be at a specified location
At the start of each frame check for a SmartWeld object and check if the attachments position has changed, If so update our internal bone data to reflect that
Pass that data to the weld constraint which would then force the bones location
If you have any other ideas on such an implementation feel free to share.
The text was updated successfully, but these errors were encountered: