Meta Quest Pro coordinate system conflict with external motion capture - origin reset issue

Problem Summary

We're developing VR applications that integrate Meta Quest Pro with external motion capture systems（Nokov）. The Quest Pro's automatic origin reset mechanism is causing severe coordinate system misalignment, making it impossible to maintain stable synchronization between headset tracking and external mocap data.

Technical Details

Core Issue

• Automatic Origin Reset: Quest Pro automatically resets its tracking origin to the current virtual node position during runtime
• Coordinate System Conflict: This conflicts with our external motion capture system's fixed coordinate system
• Cannot Disable: The automatic correction mechanism appears to be hardcoded and cannot be disabled

Current Behavior

1. We successfully calibrate and align Quest Pro tracking with external mocap
2. Quest Pro automatically resets origin after some time/movement
3. All previous positioning/calibration becomes invalid
4. Hand tracking and head tracking become desynchronized

Code/SDK Observations

• Positioning logic is encapsulated in Meta's DLL
• Hand tracking code is also sealed in the SDK
• No apparent API to control coordinate system behavior

Impact

• Professional Applications: Unsuitable for commercial VR experiences requiring precision
• User Experience: Significant hand-eye coordination problems
• Development Workflow: Requires complex manual recalibration for each session

Questions for the Community

1. Has anyone encountered similar coordinate system conflicts when integrating Quest Pro with external tracking systems?
2. Are there any undocumented APIs or workarounds to:
   • Disable automatic origin reset
   • Override hand tracking coordinate system
   • Access lower-level tracking data
3. Alternative Solutions: What approaches have worked for professional mocap integration?

What We've Tried

• Researching SDK documentation (limited info on coordinate system control)
• Attempting to override both head and hand tracking with external data
• Various calibration approaches

Looking For

• Official guidance from Meta developers
• Community solutions or workarounds
• API recommendations for professional mocap integration
• Similar experiences and how others solved this

This appears to be a fundamental limitation for professional VR development. Any insights, experiences, or official responses would be greatly appreciated!

Has anyone successfully integrated Quest Pro with external motion capture systems? What approach worked for you?

Thanks for any help! 🙏