Camera Solver - Behavior change or bug?
Another user posted (and now deleted) that they were not seeing User Trackers in their solver node. The pipleine was Auto Tracker>User Tracker>Camera Solver. I accidentally ran into this after not being able to reproduce in 25.12.09 and figured out what is going on. It looks like this happens if you add additional tracker nodes (User/Auto) to the pipeline after initially connecting the a Tracker directly to the Camera Solver (User/Auto Tracker>Camera Solver). In 24.12.19 (pre 25.x.x builds) user could insert additional tracker nodes after the inital connection and the Solver node would pick them up without issue. I'm not sure if this is a required change in behavior, or a bug? Hoping this can go back to the old behavior as I often add user/tracker nodes after the fact to try to improve results. Workaround: If you insert a tracker node after connecting to a camera solver, delete the camera s…

It was my comment. They changed the way trackers add up, so you can properly group different trackers in the same tree downstream for different purposes. Before you would have to manually select which trackers you would use for Camera solve against the ones you would use for object solving, but now you can just assign an entire User Track node for it. In your solver, you can choose which tracker groups you want to use I deleted it because I have already asked and they already answered it here :p https://www.thepixelfarm.co.uk/group/pftrack-support-community/discussion/0abfc7ec-037f-4200-9b19-e3fb89a1f284