The camera API is unusable for tracking a multiplayer aircraft

[DeelLav]

Frequency: Consistently

Severity: Blocker

Bug description:

The world reference system works much better, but is still unusable for tracking an aircraft.

AI aircraft:

Desktop 2026 03 04 10 51 16 01

My own aircraft tracked in world:

Desktop 2026 03 04 10 57 09 04

On the ground, it seems more accurate to me:

Desktop 2026 03 04 10 52 40 02

[runshotgun]

[Camer API] Race Condition?

Version: 1.7.6.0 Frequency: Consistently Severity: Blocker Context: Using the Camera API through WASM, there is frame skipping/latency happening somewhere in the data. I suspect this is due to a multi-threading race condition (aircraft position vs WASM standalone update function vs camera position processing). The way we need this to be sequenced within the same frame: Aircraft position (user or AI) → WASM update → Camera position injection Repro steps: Load the project sent to PrivateCon…

[FlyingRaccoon]

@DeelLav I agree, this is likely the same issue reported by @runshotgun

[DeelLav]

@FlyingRaccoon
Sorry, I hadn’t seen it. I’ve reposted the message in the other discussion. You can close this one.
Thank you