It is hard to see well in those tiny images, but it is still very clear that you didn't get picture 2 (the middle one) to fit. It is also clear that you have control points on clouds (that I expect moved between shots) connecting images 1 and 2. I don't think those control points on clouds are actually doing much harm. But they are certainly doing no good. Delete them.
Why does image 2 fit so badly: I'm not sure. But I think it is a parallax problem. You have a cluster of CPs not far from the camera and another cluster quite far AND you must have moved the camera between shots. So it is confusing motion (translation) with rotation. Maybe you just didn't enable the necessary translation, or maybe the optimizer is just doing a rotten job. It often does a rotten job and needs a better starting place. There are also projection issues that can lead to that kind of curvature (and I'm much less expert in that subtopic, so someone else could help more). But the CP/optimization problem is so bad in what you showed that it ought to be fixed first. I'm currently experimenting with CP optimization issues in hugin++ and would like a few more problem examples. If you want to share the whole thing (images as well as pto file) I might be able to give back a good manual correction for your pto quickly (no promises, but part of longer term improving what happens automatically is manually tweaking the example to decide what should have happened). In this case no tweaks of the optimization make sense before zooming in to check which CPs are simply wrong. -- 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/CALe0Q_kT80eoUxxXeopg5-%3DZoM%2BvmN0o5SBR8Prrek-BvL_CVA%40mail.gmail.com.
