Hey,
We're trying to use Antilatency for tracked camera with tracking data sent from another computer on the same network sending the tracking data through OSC using Aximmetry Community Edition (on the main PC we are using Broadcast Edition).
We've created a simple compound on the PC sending data that uses a camera tracking or game pose module to get the Aximmetry data which then splits the transformation into vectors and sends them over OSC to the main PC.
The problem we ran into is that the data value keeps rising over time causing the camera to rotate over time.
is there a way to make it more stable or to loop the data somehow so it won't rise like that?
Hi,
Aximmetry has a built-in solution for forwarding USB-based tracking data from one computer to another using Aximmetry. You can find a description of it (Tracking Fwd) here: https://aximmetry.com/learn/tutorials/for-studio-operators/using-led-walls-and-ar-together/#using-two-machines
I don't think your tracking data value keeps rising over time cause the Flow logic. You should check if this happens even when you don't send the tracking data to another computer. Incorrect physical setup of Antilatency can cause similar issues: https://my.aximmetry.com/post/1532-antilatency-tracks-data-drift-in-version
Also, you don't need to send both Rotation and Quaternion, they describe the same rotation. And Scale is usually not used in tracking. You could merge all of them into one vector and send them together:
Though, with Tracking Fwd you won't need the above Flow setup.
Warmest regards,