cgtinker
commented
1 year ago The ability to save transfer settings to files seems a very good idea, though I haven't tried it fully yet.
Just fixed a tiny issue there regarding id's of custom mapping objects. While this probably doesn't effect you currently - there has been a bug..
A work-saving enhancement for the users would be to have the Transfer Drivers field be auto-filled
maybe I'll just autofill 'cgt_Drivers' if any rig gets selected - this will just transfer what ever is in the scene.
to match the Mediapipe Target: type (e.g. Hands) that was last detected
While I like the context driven idea, I don't want anything from the transfer stuff being connected with the detection stuff as I consider to remove the detection part in the future (and just use freemocap or create an own exe pushing data via a socket.., not rly sure about yet)
Another minor improvement would be to change the HAND folder to HANDS, since it contains both left and right hands.
Will do ;)
The ability to save transfer settings to files seems a very good idea, though I haven't tried it fully yet.
A work-saving enhancement for the users would be to have the Transfer Drivers: field be auto-filled to match the Mediapipe Target: type (e.g. Hands) that was last detected. That would save users the time and potential confusion of having to figure out which folder (e.g. cgt_drivers/cgt_hands, etc.) to use for storing the transferred drivers in 90+% of cases. It could still allow manually changing the transfer drivers results selection for special cases.
Another minor improvement would be to change the HAND folder to HANDS, since it contains both left and right hands.