Show Posts
1
Bug Reports / Re: Detect Markers - disable parity
« on: May 29, 2015, 07:06:33 AM »
I too am having a similar issue.
I am running PhotoScan 1.1.6 build 2038, and am trying to reprocess photosets shot using GCT's printed from a machine running Version 1.0.4 build 1847. The updated version is not detecting most targets and when it successfully detects targets, it detects them as having different ID numbers. I have disabled parity and the issue persists. Also, the targets I am using are in the 500-700 range of the old series. Is there a stable fix for this?
If not, is it possible to remap target IDs from the old series so that I can still use the older text files I have to import GCT coordinates? Or is it possible to revert to an older version of PhotoScan so I can process legacy data?
I am running PhotoScan 1.1.6 build 2038, and am trying to reprocess photosets shot using GCT's printed from a machine running Version 1.0.4 build 1847. The updated version is not detecting most targets and when it successfully detects targets, it detects them as having different ID numbers. I have disabled parity and the issue persists. Also, the targets I am using are in the 500-700 range of the old series. Is there a stable fix for this?
If not, is it possible to remap target IDs from the old series so that I can still use the older text files I have to import GCT coordinates? Or is it possible to revert to an older version of PhotoScan so I can process legacy data?
