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
I know there is a component to merge PhysBones, and it also need some improvements #895
But I wanted to suggest also integrating it into main optimization step, when bones are next to each other and all their values are the same, and they can't be grabbed, maybe they could be merged automatically. As far as I understand, there is no difference in behavior for these cases.
(I might try to make PR some other week if you are interested in the feature overall)
Thank you for creating feature request and looking for implementing feature.
I'm interested in the feature and I have it in mind to implement such a feature in the future, but I forgot to create issue.
But I wanted to suggest also integrating it into main optimization step, when bones are next to each other and all their values are the same, and they can't be grabbed, maybe they could be merged automatically. As far as I understand, there is no difference in behavior for these cases.
I think so but I have to consider PhysBone Chain length and Parameter setting in Options section.
Duplicated Parameter setting may work weirdly so I think we should not merge if Parameter setting is there.
Also, if any of PhysBone settings is using curve setting, we have to consider PhysBone Chain Length.
If PhysBone Chain Length is different, the frame (time) PhysBone pick from curve is different between PhysBone so it must be same to work correctly.
(I didn't know that at the time so I did not make error in MergePhysBone but for now there will be warning in that case.)
I know there is a component to merge PhysBones, and it also need some improvements #895
But I wanted to suggest also integrating it into main optimization step, when bones are next to each other and all their values are the same, and they can't be grabbed, maybe they could be merged automatically. As far as I understand, there is no difference in behavior for these cases.
(I might try to make PR some other week if you are interested in the feature overall)
GPT 4:
隣接するボーンで、すべての値が同じで、かつ掴むことができない場合に、それらを自動的に結合するように、メインの最適化ステップに統合することを提案したいと思っています。理解している限りでは、これらのケースでの動作に違いはないようです。また、PhysBonesを結合するコンポーネントが存在し、それにも改良が必要であることは知っています。#895
The text was updated successfully, but these errors were encountered: