This rarely happened in previous versions, but it was not flawless. However, now every single exported track to maya has the image plane and camera disconnected. My usual workflow Clip-Auto or user track-camera solve-orient camera-test geometry-scene export.
Is not even an option as an output node.
This used to be the standard workflow for this node (From an older project):
Hello Angel,
Thanks for reporting this - it looks like the node connectors and menu logic is not allowing the link, I’ve reported to the developers and they will get this fixed in the next build update. I can’t say how soon, but it has been raised as a priority so shouldn’t be long.
Hello, to help you understand more quickly, I’m attaching a zoomed-in view of one of the points. (This is not an occluded point — it’s a clean feature that remains visible throughout the entire footage.)
I created a sufficient number of tracker points using User Tracks and proceeded with the tracking. I also set the focal length and sensor size to match the original footage. (The tracking itself worked well.)
However, I have a question. Many of the tracking points flicker between green and yellow, and when I inspect those points, I notice that some sections are partially missing or empty.
Even when I try to fix this manually using the Adjust function, it doesn’t seem to resolve the issue.
Hello thanks for providing the screenshots.
It appears that trimming is enabled, which is why you’re seeing gaps in the Scrub Bar. These gaps correspond to the spikes for that particular tracker in the Residual Errors graph; those frames fall outside the trim line and are therefore ignored during the solve. Either delete or adjust your trim line then use Adjust to fix or disable any trackers with high residual error and run Refine All again.
For further information on residual errors and trimming trackers, please consult the documentation here
Regarding the “flickering green and yellow”, I’m assuming you’re referring to the tracker colours in the Cinema view after solving/refining. Any rapid flickering in the residual error may be caused by compression artefacts in the footage.
You can find out more about what the colours mean here
Hello,
I tracked two versions of the same footage: the original distorted footage and a version with an STMap applied.
For the original distorted footage, tracking worked well when I entered the actual focal length used during shooting.
However, when I tracked the STMap-applied footage and entered the same real focal length, the tracking points continuously showed sliding behavior and the solve was unstable.
Thanks for uploading your screenshots, they made it much easier to see what’s going on. This doesn’t appear to be an STMap issue. The main problem is that the camera sensor size isn’t set.
Without a sensor size, a real focal length has no proper context, since both values are needed to calculate the correct field of view. If you enter a focal length alone, PFTrack assumes a default sensor size (full-frame). If your footage was shot on a smaller sensor or cropped mode, that assumption will be wrong and can cause inaccuracies.
When you enter the FOV directly, PFTrack simply calculates the focal length needed to match it, which is why the value changes to ~32mm and the tracking becomes stable. This also ‘might’ indicate that the camera has a smaller format sensor or the focal length has been noted down inaccurately.
The key takeaway is that when working with STMaps, accurate and matching camera and lens settings, especially sensor size and focal length, are essential for accurate results.
Hello Angel,
In the latest versions of Maya, imagePlanes aren’t automatically parented to the camera. You can easily do this yourself in the Outliner by holding Shift and using the middle mouse button to drag the imagePlane node onto the camera node (e.g., Camera01).
We also have new export scripts for Maya 2026 that handle this parenting automatically. You can find them in the resources section of the PFTrack website here:
https://www.pftrack.com/post/maya-2026-export-scripts
The page includes installation instructions. Once installed, you can select “Maya 2026” as the export format. These scripts should also work with earlier versions of Maya.