Hello Matthew Installed your new version and found the following not working properly when going back to the standard defaults.
1 In the preference screen of the control point generators is then the absolute path C:\program files\Hugin\CPG\ folder cpg to use\cpg.exe. When applying the standard defaults it becomes a relative path? ..\CPG \folder cpg to use\cpg.exe. All cpg's can handle that, except autopano of Alexandre Jenny, I have to put the path back to the absolute path, 2 In the parameters of autopano-SIFT-C the parameter --projection %f %v is back again. Kind regards, Henk Tijdink On 2 okt, 03:07, Matthew Petroff <[email protected]> wrote: > On Sep 30, 4:17 pm, Henk Tijdink <[email protected]> wrote: > > > when you go to the preference screen and > > you load the defaults the path to the CPG folder is gone and Hugin > > expects then the control point generators in the Hugin binary folder. > > This is because the paths are hard-coded into the hugin binary and > have nothing to do with the installer. It does however make sense to > have the binary in the installer revert to the paths used by the > installer, so I patched the binary to do so. This updated build is > available here:http://www.box.net/shared/meeaobr9ec > > I updated the default paths to the control point detectors for Windows > in hugin, and also added functionality so that hugin checks if a path > relative to hugin.exe was entered as the control point detector > executable so the new paths will work. > > The patch to the hugin-2010.2.0_rc2 tarball is available > here:http://www.mpetroff.net/hugin/hugin_windows-CPG-defaults_patch_2010-0... > > I would ask someone with commit access to apply the patch to the > mercurial repository, but the new paths, while better organizing the > detectors in lieu of package management, would make it more difficult > for those not using an installer. One remedy would be to create empty > folders for the various detectors when hugin is compiled so they could > be populated with detectors later if desired. Detectors in bin still > work of course, but the default paths have to be changed. Could one of > the developers please voice an option on the issue? > > A patch to the installer that makes the control point detector folders > the same as the new hard coded values is available > here:http://www.mpetroff.net/hugin/installerchanges_2010-10-01.7z > > Matthew -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
