[ANSWERED] Skeleton tracking a pre made 'puppet'

quarterinchjack

Hi all,

This question relates to the excellent Guru Session #19 that Mark presented in 2021 that looked at skeleton tracking with a Rokoko suit. During the session he used a figure made from a simple 3d pipe model and explained how to replace that pipe with any other 3d model to hand. My question is can I use a fully formed pre-rendered human figure (made in Blender) instead of the figure made from the individual pipes? My gut feeling is that I would need to dissect that original model and pull apart the separate limbs to be imported as a replacement for the pipe model - is that correct?

Thanks for any help.

Andy

Woland

@quarterinchjack said:

My gut feeling is that I would need to dissect that original model and pull apart the separate limbs to be imported as a replacement for the pipe model - is that correct?

Yes, that is correct.

quarterinchjack

@woland Great, thanks I'll give that a go.

Woland

@quarterinchjack

Other things that might be helpful:

There should be a download link for the file mark used with the Rokoko Suit here: https://support.troikatronix.com/support/solutions/articles/13000100433-guru-session-19-body-tracking-with-the-rokoko-smartsuit-pro-
The example file for the Rokoko Studio Live Watcher actor may also be a helpful basis for creating a patch: https://troikatronix.com/add-ons/rokoko-studio-live-watcher/
This lovely line puppet created by the ever-brilliant @bonemap can be found on the TroikaTronix Add-Ons Page: https://troikatronix.com/add-ons/line-puppet/

Best wishes,

Woland

quarterinchjack

Thanks @woland - I'm not using a suit, so going to try and rejig Mark's patch to either use a Kinect or perhaps the Zig Sim Pro mobile app which looks pretty good. I don't think the latter outputs a skeleton, just individual limb point OSC location data. I don't suppose you know of a way to package that up as a skeleton output that the decoder would recognise?

Woland

@quarterinchjack said:

I don't suppose you know of a way to package that up as a skeleton output that the decoder would recognise?

Unfortunately, it is not currently possible to programmatically create data with the special type "skeleton".