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 PrivateContent
Ensure the framerates are unlocked and Dynamic Settings are disabled in the sim settings to introduce variance in the way things are processed
Once loaded into an aircraft like the FA18, set LVar p42_cin_camera_enabled to 1, enabling the use of the camera API
I’m posting the message here again to avoid duplicates
Frequency:Consistently
Severity:Blocker
Bug description:
The world reference system works much better, but is still unusable for tracking an aircraft.
AI aircraft:
My own aircraft tracked in world:
On the ground, it seems more accurate to me:
This issue seems similar to the multiplayer aircraft locking problem that has been present since the release of MSFS 2024. I previously reported it on the official forum and through Zendesk. I am reposting the link to the official forum thread here for reference.
