# ZED SDK 5.3 pose\_confidence behavior inconsistent between sl::camera and sl::fusion

**URL:** <https://community.stereolabs.com/t/zed-sdk-5-3-pose-confidence-behavior-inconsistent-between-sl-camera-and-sl-fusion/11313>\
**Category:** C++\
**Tags:** sdk, jetson, depth\
**Created:** [May 14, 2026, 12:03am UTC](https://community.stereolabs.com/t/zed-sdk-5-3-pose-confidence-behavior-inconsistent-between-sl-camera-and-sl-fusion/11313 "2026-05-14T00:03:26Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![ShashankVSS](https://community.stereolabs.com/user_avatar/community.stereolabs.com/shashankvss/32/6120_2.png) [@ShashankVSS](https://community.stereolabs.com/u/ShashankVSS)\
**Post date:** [May 14, 2026, 12:03am UTC](https://community.stereolabs.com/t/zed-sdk-5-3-pose-confidence-behavior-inconsistent-between-sl-camera-and-sl-fusion/11313/1 "2026-05-14T00:03:26Z")

</div>

Hi,

I’m testing `sl::Pose::pose_confidence` on a ZED X Mini using SDK 5.3 on Jetson Orin NX, and I’m seeing behavior that seems inconsistent with the documentation / expected tracking quality reporting.

Setup: ZED X Mini on a Jetson Orin NX running SDK 5.3 with positional tracking enabled.

What I’m observing in a single-camera `Camera::getPosition()` test:

- `pose.pose_confidence` stays locked at `100`
- `POSITIONAL_TRACKING_STATE` remains `OK`
- timestamps continue updating normally

However, this occurs even when the camera is fully covered and moved around in space.

At the same time, the SDK prints internal warnings such as:

`[ZED][WARNING] Degraded or noisy image(s) detected on X keyframe(s) in the last tracking interval. These keyframes will be removed from the map to maintain tracking quality.`

So internally, the SDK seems to detect degraded image/tracking quality, but `pose.pose_confidence` still remains at `100`.

I’m also seeing a related behavior when using Fusion. If I call `fusion.getPosition()` and inspect the returned pose confidence, the confidence value does not appear to update at all and remains at `0`.

So I’m seeing two different behaviors:

- `Camera::getPosition()` returns confidence fixed at 100
- `Fusion::getPosition()` returns confidence fixed at 0

Questions:

1. Is `pose.pose_confidence` expected to remain fixed at 100 in GEN3 positional tracking?
2. Is `pose.pose_confidence` populated/meaningful when using `Fusion::getPosition()`?
3. Is this field currently recommended for runtime tracking-quality validation or failure detection?
4. Is there another recommended metric/API for detecting degraded visual tracking quality in real time?
5. Is confidence only updated under certain tracking-state transitions or tracking modes?

Right now, it seems difficult to use `pose.pose_confidence` as a sanity metric, since it does not appear to reflect degraded visual conditions in the direct camera case, and does not appear to be populated in the Fusion case.

Thanks.

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [May 18, 2026, 7:52am UTC](https://community.stereolabs.com/t/zed-sdk-5-3-pose-confidence-behavior-inconsistent-between-sl-camera-and-sl-fusion/11313/2 "2026-05-18T07:52:04Z")

</div>

Hi @ShashankVSS  
Welcome to the [StereoLabs](https://www.stereolabs.com/) community.

> [@ShashankVSS](#):
>
> I’m testing `sl::Pose::pose_confidence` on a ZED X Mini using SDK 5.3 on Jetson Orin NX, and I’m seeing behavior that seems inconsistent with the documentation / expected tracking quality reporting.

`sl::Pose::pose_confidence` is not yet populated when using `GEN_3`, you can ignore it with this version of the SDK.  
This information will be available with one of the next versions of the ZED SDK.

> [@ShashankVSS](#):
>
> At the same time, the SDK prints internal warnings such as:
> 
> `[ZED][WARNING] Degraded or noisy image(s) detected on X keyframe(s) in the last tracking interval. These keyframes will be removed from the map to maintain tracking quality.`
> 
> So internally, the SDK seems to detect degraded image/tracking quality, but `pose.pose_confidence` still remains at `100`.

This is expected to appear only on heavily degraded images (typically low-light, noisy frames from the ZED X in dark conditions) and should not impact tracking quality.  
In the meantime, the best way to monitor tracking quality at runtime is to use either:

- `getPositionalTrackingLandmarks2D` (2D landmarks)
- `getPositionalTrackingStatus` (tracking status)

---

<div class="post-metadata">

**Author:** ![ShashankVSS](https://community.stereolabs.com/user_avatar/community.stereolabs.com/shashankvss/32/6120_2.png) [@ShashankVSS](https://community.stereolabs.com/u/ShashankVSS)\
**Post date:** [May 19, 2026, 1:31pm UTC](https://community.stereolabs.com/t/zed-sdk-5-3-pose-confidence-behavior-inconsistent-between-sl-camera-and-sl-fusion/11313/3 "2026-05-19T13:31:35Z")

</div>

Thanks for the reply! I had one more question about the covariance matrix.

The covariance behavior also seems unexpected on my setup. The first three diagonal terms (presumably X/Y/Z position covariance) rapidly grow to extremely large values, reaching on the order of billions, and do not appear to recover once tracking conditions improve.

The last three terms (presumably roll/pitch/yaw orientation covariance) remain near zero, but still exhibit a similar growth trend relative to their baseline.

This behavior seems inconsistent with the actual tracking quality in some cases, since positional tracking can remain visually stable while the covariance diverges significantly. Is this expected behavior, or is there a recommended interpretation of the covariance values in SDK 5.3 for positional tracking?

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [May 20, 2026, 1:06pm UTC](https://community.stereolabs.com/t/zed-sdk-5-3-pose-confidence-behavior-inconsistent-between-sl-camera-and-sl-fusion/11313/4 "2026-05-20T13:06:44Z")

</div>

This behavior is not normal.  
Are you reading the covariance from Fusion or from the Positional Tracking module?

In the SDK, the covariance is computed primarily by accumulating the odometry covariance over time, except when a loop closure occurs — in that case, we recompute it from the graph.

That said, a sanity check is applied to the reported covariance to prevent it from exploding.

If you confirm that this is coming from the Positional Tracking module, could we get an SVO to reproduce and fix the issue?

---

<div class="post-metadata">

**Author:** ![ShashankVSS](https://community.stereolabs.com/user_avatar/community.stereolabs.com/shashankvss/32/6120_2.png) [@ShashankVSS](https://community.stereolabs.com/u/ShashankVSS)\
**Post date:** [May 20, 2026, 3:45pm UTC](https://community.stereolabs.com/t/zed-sdk-5-3-pose-confidence-behavior-inconsistent-between-sl-camera-and-sl-fusion/11313/5 "2026-05-20T15:45:24Z")

</div>

Hi Myzhar,

I added a debug comparison between the Fusion pose covariance and the raw camera positional tracking covariance from the same run.

The camera positional tracking covariance appears normal, while the Fusion position covariance grows extremely large:

```auto
zed_state fusion    
conf=0 cov=[5954960896.0000 5061733376.0000 10295344128.0000 0.0303 0.0157 0.0057] 
zed_state camera_pt trk=1 cov=[0.0060 0.0051 0.0103 0.0303 0.0157 0.0057]

```

The last three orientation covariance terms match between Fusion and camera PT, but the first three position covariance terms diverge only on the Fusion side.

This was from `sl::Fusion::getPosition(…, WORLD)` versus `sl:Camera:getPosition(…, WORLD)` on the tracking camera.

Does this point to a Fusion-side covariance issue? Or is this expected behaviour? I can provide the SVO for this run, but its 270 MB and the max limit is 10 MB here. Is there a method you would like me to send it to you?

Best regards,  
Shashank

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [May 21, 2026, 3:32pm UTC](https://community.stereolabs.com/t/zed-sdk-5-3-pose-confidence-behavior-inconsistent-between-sl-camera-and-sl-fusion/11313/6 "2026-05-21T15:32:06Z")

</div>

> [@ShashankVSS](#):
>
> This was from `sl::Fusion::getPosition(…, WORLD)` versus `sl:Camera:getPosition(…, WORLD)` on the tracking camera.
> 
> Does this point to a Fusion-side covariance issue? Or is this expected behaviour? I can provide the SVO for this run, but its 270 MB and the max limit is 10 MB here. Is there a method you would like me to send it to you?

Yes, it does. The ZED SDK detected a bug on the Fusion-side covariance.  
The next patch release will provide a fix.

Meanwhile, you can use the covariance from the positional tracking module.

---

<div class="post-metadata">

**Author:** ![ShashankVSS](https://community.stereolabs.com/user_avatar/community.stereolabs.com/shashankvss/32/6120_2.png) [@ShashankVSS](https://community.stereolabs.com/u/ShashankVSS)\
**Post date:** [May 21, 2026, 6:31pm UTC](https://community.stereolabs.com/t/zed-sdk-5-3-pose-confidence-behavior-inconsistent-between-sl-camera-and-sl-fusion/11313/7 "2026-05-21T18:31:50Z")

</div>

Hi Myzhar,

Thanks for confirming the Fusion covariance bug, that explains part of what we were seeing.

While debugging this, we also started looking at the latency between the tracking camera `grab()` timestamp and the fused pose timestamp returned from `Fusion::getPosition(…, WORLD)`.

We typically see ~40–70 ms latency, but periodically there are spikes to ~180–300+ ms. The odd part is that they appear somewhat periodic, roughly every ~0.6 s in some runs and ~1 s in others.

This is on a drone with a downward-facing camera flying over a reasonably feature-rich scene (concrete with markings and scattered objects). Tracking remains valid during these events, and we do not observe obvious tracking failures.

Is this type of periodic latency expected for downward-facing UAV tracking, or does Fusion perform any periodic synchronization / optimization that could delay pose updates?

Also, during these delayed periods, is any form of prediction or dead reckoning used internally? In some cases we effectively lose fresh pose updates for ~300–400 ms, which becomes problematic for our controller.

Best regards,  
Shashank

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [May 27, 2026, 3:03pm UTC](https://community.stereolabs.com/t/zed-sdk-5-3-pose-confidence-behavior-inconsistent-between-sl-camera-and-sl-fusion/11313/8 "2026-05-27T15:03:38Z")

</div>

> [@ShashankVSS](#):
>
> We typically see ~40–70 ms latency, but periodically there are spikes to ~180–300+ ms. The odd part is that they appear somewhat periodic, roughly every ~0.6 s in some runs and ~1 s in others.

This is a known behavior, and it will be improved in the next releases of the ZED SDK.

Can I ask why you are using Fusion? Are you fusing multi-camera information or are you fusing GNSS data?

---

<div class="post-metadata">

**Author:** ![ShashankVSS](https://community.stereolabs.com/user_avatar/community.stereolabs.com/shashankvss/32/6120_2.png) [@ShashankVSS](https://community.stereolabs.com/u/ShashankVSS)\
**Post date:** [June 15, 2026, 8:05pm UTC](https://community.stereolabs.com/t/zed-sdk-5-3-pose-confidence-behavior-inconsistent-between-sl-camera-and-sl-fusion/11313/9 "2026-06-15T20:05:57Z")

</div>

We were planning to do multi-camera fusion and combining GNSS data.
