How to export recordings with BODY_38 as fbx file

Software C++
1

Hi all,

I’ve been experimenting with the official example C++ source code for exporting a tracked body as fbx file. While this example works well for bodies in the body 34 format, it doesn’t currently support the body 38 format. At least at first glance, only a few modifications seem necessary to have this example support the body 38 format. One of these modifications involves changing the utils.hpp file so that the joint parent indices, children indices, and local translations match those of the body 38. The only thing that currently prevents me from progressing with this is my lack of knowledge concerning the correct coordinates for the local joint translations. Are these coordinates published somewhere? Or has anybody among you already implemented fbx support for the body 38 format?

Any advice or pointers to information is greatly appreciated.

Thanks in advance and best regards

Daniel

2

Hi,

I think the simplest solution is that I update the sample myself.
I’ll try to take some time to do it this week.

Best regards,

3

Hi Benjamin,

thanks a lot for planning to update the sample! I very much look forward to this update.

Best regards

Daniel

4

Sure! I’m happy someone is using it.

5

Hi again,

I updated the sample to fix the api issues and I also added the body 38 support.
The new version will only be officially available with the next ZED SDK version but you can access it here in the mean time.

Best regards,
Benjamin V.

6

Hi Benjamin,

this is fantastic! Thanks a lot for updating the sample so quickly.

Best regards

Daniel

1 Like
7

Hi Benjamin,

I’ve experimented with the updated version of the sample and have come across some issues. For some reason, when exporting the recording with a body_38 skeleton, the nodes don’t possess names but only numbers. Also, when opening the resulting fbx in MotionBuilder, only the nodes but not the connections between them are displayed. These two issues don’t occur when exporting the recording with the body_34 skeleton. Do you have an idea what might be causing these issues?

Thanks and best regards

Daniel

p.s.1. I’m using the AnimationUtility, GeometryUtility, and Common source files from version 4.2 of the ZED SDK.

p.s.2. I’ve modified the CreateSkeleton function by replacing sl::BODY_34_PARTS::LAST with sl::BODY_38_PARTS::LAST and sl::BODY_34_PARTS(I) with sl::BODY_38_PARTS(I).

8

I’ll take a look this afternoon.

9

Hi Bejamin,

great! Thanks.

Best regards

Daniel

10

I made an update fixing the bone naming and your “ps2” as well.
However I don’t see only the nodes but not the connections between them are displayed when I open it in Blender.

11

Hi Benjamin,

thanks a lot for fixing the bone names and my hand-cooked modifications to the skeleton creation. I’m glad to hear that things look fine in Blender after importing the FBX. It must be just Motion Builder acting up.

Best regards

Daniel

12

Hi Benjamin,

just to conclude the topic: I can happily confirm that the FBX export of the body 38 format works now very well and that things also look fine when importing the resulting file into MotionBuilder.

Thanks again for updating the C++ sample code.

Best regards

Daniel

1 Like