The Pixel Farm User Community

#PFTrack Hello, We're using PFTrack Enterprise 24.09.24 We're having scaling issues when exporting .fbx; the export size is not 1:1 with the original data that was imported. We're having to export with the scaling set to 91.45 to get our geo to line up in MAYA. We are exporting Autodesk FBX 2018 and 2020 with the same issue. We have been using PFTrack 22.09.14 with no issues for a while and recently upgraded to 24.09.24 Any insight is appreciated. Michael

Hello! I'm trying to track an interior shot, which I also took some lidar scans of. When I track the conventional way, it get's kinda rough and I find that it takes way to long. But when I use a geometry track, import the scan. click off the "moving object" button so the camera moves instead, I get a really good track. Everything seems to stick. But I can't get a solve from that. If I go to a camera solver, It seems to only use the trackers and disregards my track from the geometry track. Even if I use the "upstream hint". I would like to have the solve to get an accurate st map for use later. Is it possible to use the camera you got from a geometry track to use in a solve?

New PFTrack learning article! #PFTrack #distortion If you're curious about lens distortion, distortion calibration, and why they are essential for your camera tracking and visual effects workflow, we've created a learning article to explain it all. This guide answers your key questions and highlights the importance of correcting distortion for more accurate and seamless VFX results. Start Reading here https://www.thepixelfarm.co.uk/post/why-you-need-to-know-about-distortion-calibration