4.2 Live Link receiver with 5.2 Fusion

Software Unity
1

Hello, we are currently working with Zed and Unity - and have a project which is working great with one zed cam and the fully integrated zed sdk in Unity. We want to expand to more cams and use Fusion and Live Link - but I don’t currently have a second cam and won’t have access to one until next week when I’m on site.
In preparation i’m trying to get my head around how this all works - so that once i’m on site things go smoothly.
What I have working is the live link package in an empty test project which is successfully receiving skeleton data from the Mono Sender app.

Both the live link receiver package and the sender come from a Zed SDK of around 4.05 / 4.2 -
the part i’m not clear about is once I’m on site and able to configure Fusion - (which will be from the 5.2.0 sdk) - will the live link 4.2 version of ZEDBodyTrackingManager be able to receive that data?
Or is there a 5.2 compatible version of the live link receiver somewhere - which uses the newer data types like BodyTrackingFrame and DetectedBody instead of sl.Bodies and sl.BodyData?

Thanks,

2

I guess another way of asking the question would be - when using Fusion from SDK 5.2 - what data will come out the other end - will it be sl.bodies etc - or the newer data format we’re already using with 5.2 -
and is there any loss in terms of skeleton stability etc using Fusion and live link compared to just having the whole SDK in the project?
thanks!

3

Hi,

I’m not sure to see what changes in the data format you are refering to.

The live link sample is sending ‘sl.Bodies’ data to Unity, so it should be working with 5.2 with no issue.

Actually, you can use the fusion module with one camera if you want, just to test if everything works as expected. All you need to do is creating a “fake” calibration file with only one camera.

The live link plugin is sending body tracking over the network using UDP so it can lose packets if the network is very bad. Other than that, it’s the same.