# ZED360 crashing and not showing skeletal data

**URL:** <https://community.stereolabs.com/t/zed360-crashing-and-not-showing-skeletal-data/10694>\
**Category:** Software\
**Created:** [January 26, 2026, 5:17pm UTC](https://community.stereolabs.com/t/zed360-crashing-and-not-showing-skeletal-data/10694 "2026-01-26T17:17:58Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ZavierL](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/z/df705f/32.png) [@ZavierL](https://community.stereolabs.com/u/ZavierL)\
**Post date:** [March 4, 2026, 10:09am UTC](https://community.stereolabs.com/t/zed360-crashing-and-not-showing-skeletal-data/10694/6 "2026-03-04T10:09:24Z")

</div>

Hi,

We have recently been experiencing the same issue. Based on the information shared in the thread **[Framerate issue when using the Fusion Network Workflow](https://community.stereolabs.com/t/framerate-issue-when-using-the-fusion-network-workflow/10593)** , we performed some tests on our side.

With the same setup, ZED360 reporting `WRONG BODY FORMAT` error when running with SDK 5.1 & 5.2, while SDK 5.0 works correctly.

Our project requires multi-camera Body Tracking and Object Detection. According to SDK 5.1 release notes, the fllowing feature was introduced:

`Added support for object detection streaming from ` **`sl::Camera`** `to` **`sl::Fusion`** ` in the network configuration.`

Additionally, based on the FPS issues discussed in the thread mentioned above, it seems we will likely need SDK5.1+ for our project.

So we would like to ask if there has been any update, fix or recommended workaround for this issue?

Here is some additional information about our setup:

We have two Zed Mini Box [**JetPack: 6.1 (nvidia-jetpack 6.1+b123) L4T: 36.4.4 Ubuntu: 22.04**] each having two Zed X connected.

Thanks

---

_[View the full topic](https://community.stereolabs.com/t/zed360-crashing-and-not-showing-skeletal-data/10694)._
