[Hugin-devs] [Bug 1856345] Re: Running geometric optimizer after stitcher producing drastically different result

2019-12-14 Thread tmodes
> In the stitcher window "Calculate Field of View" and "Calculate Optimal Size" were clicked. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1856345 Title: Running geometric optimizer after

[Hugin-devs] [Bug 1856345] Re: Running geometric optimizer after stitcher producing drastically different result

2019-12-13 Thread Sergei Steshenko
"The control point error distances are calculated in the output space" - which action of mine changes output space ? -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1856345 Title: Running

[Hugin-devs] [Bug 1856345] Re: Running geometric optimizer after stitcher producing drastically different result

2019-12-13 Thread tmodes
The control point error distances are calculated in the output space. When you change the output size (or projection), it is expected that the cp error distance changes. (This is a design decision in the underlying panotools library.) ** Changed in: hugin Status: New => Invalid -- You