For those who don’t know the tool: The Pixel Farm develops PFTrack, a node-based 3D camera tracking and photogrammetry system used in VFX, virtual production, and survey-driven pipelines. It exports to DCC tools including Autodesk Maya and integrates LiDAR and image based reconstruction.
The Pixel Farm has released PFTrack 26.02, a point update to its camera tracking and photogrammetry software. The release focuses on export reliability, Survey Solver behaviour and data validation rather than new solver technology. According to the published change list, the update introduces improvements to Maya export scripts, OBJ texture handling, LiDAR import logging and node connectivity within the Survey Solver. It also resolves a keyboard shortcut conflict in the Orient Camera node.
Maya export scripts corrected
The updated Maya export scripts now automatically parent background image planes to cameras on export. This addresses a long standing friction point in matchmove handoff. Previously, depending on scene configuration and export path, artists could end up manually re-parenting image planes inside Maya to maintain alignment between the solved camera and its background plate. The revised script automates this relationship at export time.
For tracking teams delivering camera solves into Maya-centric pipelines, this reduces post-export clean-up and the risk of misalignment during layout or scene assembly. The vendor statement does not detail changes to other DCC export scripts.
Survey Solver and OBJ texture loading
PFTrack 26.02 updates the way OBJ mesh textures with numbered filenames are loaded into the Survey Solver node. OBJ sequences or assets that rely on incrementally numbered texture files will now load correctly when imported into Survey Solver. The official notes do not specify naming conventions, but refer to numbered filenames in general terms.
For facilities using photogrammetry meshes or survey derived assets with multiple texture tiles, correct automatic loading reduces manual reassignment inside the node graph. It also limits the possibility of mismatched textures during camera solve refinement. The change appears limited to texture loading behaviour inside Survey Solver and does not reference modifications to the OBJ importer elsewhere in the application.
LiDAR import logging added
The update adds explicit error logging when importing corrupted or incomplete LiDAR survey data files. PFTrack supports LiDAR survey data within its camera-solving and scene-reconstruction workflows. In previous versions, incomplete or damaged files could fail during import without detailed diagnostic output.
With 26.02, the system now logs errors when such data is detected. The vendor documentation does not describe the logging format, verbosity level or where logs are written. It does state that error logging is triggered when corrupted or incomplete LiDAR files are imported.
Photogrammetry node connectivity fixed
A further fix addresses connector logic in Studio and Enterprise editions. Photogrammetry nodes can now be connected to secondary inputs of the Survey Solver where appropriate. The official wording specifies that this applies to Studio and Enterprise only.
This suggests that earlier builds restricted valid node graph connections in certain configurations, potentially limiting more complex photogrammetry driven solves. The updated connector logic restores the ability to route photogrammetry outputs into secondary Survey Solver inputs when supported by the node’s design.
The vendor has not published technical detail about which specific input sockets were affected or how the internal validation rules have changed. Not independently verified at press time.
Facilities using advanced node graphs that combine survey data, image based reconstruction and manual constraints should review existing templates to confirm expected behaviour after updating.
Scope and positioning
This release does not introduce new solver models, GPU-acceleration changes, or major UI revisions. It is positioned as a maintenance and workflow refinement update. The focus remains on export reliability, data validation and node graph correctness. For studios that rely on PFTrack for camera tracking, survey alignment and photogrammetry reconstruction, these adjustments address specific operational irritations rather than expanding feature breadth.
PFTrack is available in three editions. PFTrack Solo is priced at £699 for a permanent licence. PFTrack Studio is offered on a rental basis, with pricing listed at £59 for a five day rental period. PFTrack Enterprise pricing is available on request from The Pixel Farm. As always, facilities should confirm current licensing terms and support options directly with their vendor before procurement.
As always, new tools and updates should be tested in controlled conditions before being introduced into active production pipelines.
