Thank you so much for your detailed response! Your insight about the incompatibility of EnhancedTouch with VisionOSSpatialPointerDevice in Hybrid mode was critical—I completely overlooked that. I’ll immediately review the scoping of the activeTouches.Count > 0 condition in my code and adjust the logic for touchData2.Kind as suggested.
The note about input position offsets in the visionOS simulator is also incredibly helpful. We’ll test on a physical Vision Pro device to rule out simulator-specific quirks. If the issue persists after adjustments, I’ll submit a full Bug Report with the project sample for deeper investigation, per your guidance.
I’ve already submitted an “Idea” on the public roadmap for improved Hybrid mode documentation and sample projects! Hope this helps prioritize future updates.
Thanks again for your swift and expert support—your guidance makes a huge difference! I’ll update here promptly after testing and look forward to the continued evolution of Polyspatial workflows.