The estimate of the control point error depends on size of the output panorama. The default size of the output may be much smaller than the eventual size you generate, hence the differing numeric values of the control point errors. Is it just the reported numbers changing or is the optimization worse upon reopening?
On Tuesday, 19 August 2014 20:56:04 UTC+1, [email protected] wrote: > > Hi all, > > I've had a reoccurring issue with control points not saving properly. > > Here's the gist of it... After control points are added and optimized, > I'll save the project. All is well, and it reopens just fine. However, > after I generate a panorama and then save that exact same project, upon > opening it again the control points change from having an average distance > of 2.00 or less to being 15.00 or greater. > > Any idea as to why the distance for the control points does not save > properly after generating the panorama? Also, any help for how to avoid > this would be much appreciated. (It's rather frustrating and time > consuming.) > -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/117c7ac6-097d-445d-b9b8-9132375f1ac6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
