Thank you I will check it out
--- In PanoToolsNG@yahoogroups.com, "John Houghton" <j.houghton@...> wrote:
> --- In PanoToolsNG@yahoogroups.com, "Garrett Unglaub" <cruc10@>
> > Well, the actual problem is the fact that i keep getting a donut
> > shaped pano in hugin with the same settings as ptgui.
> Maybe you are relying too much on automatic features. These don't
> always work perfectly - neither in Hugin nor in PTGui. Have you
> checked the control point assignments, particularly those between
> images in the neighborhood of the obvious discontinuities of the
> output image? With some intelligent manual intervention, you can
> easily get more-or-less identical results from both PTGui and Hugin.
> As it's a 360 degree panorama, the hfov of the lens will be evaluated
> accurately by the optimizer, provided you have a good spread of
> control points. The optimizer gives a lot of control over what does
> and doesn't get changed in the optimization if you choose to use it.
> It can often help if you initialize the yaw values of the images to
> their approximate known values. (In PTGui, use the Fill Yaw button on
> the Image Parameters tab to automatically calculate the values).
> While your PTGui result is quite good, it could do with levelling to
> get the vertical features properly upright. (Don't overlook the
> cloud reflections in the lake, which should also be vertically
> aligned). If you aren't familiar with using t1 (vertical line)
> control points, I suggest you take a look at this tutorial: