Hi Can, can you open the .pto file (it's a plain ascii text file, so you could temporarily exchange the extension with .txt) in a text editor and have a look at the control points, look at the lines beginning with 'c'.
This is from the documentation <http://wiki.panotools.org/PTOptimizer> # 'c' lines # ---------------- # Control point lines # One line per point pair # about one pair of points per image per variable being optimized. # The more variables being optimized the more control points needed. # # n0 first image # N1 second image # x1066.5 first image x point position # y844.333 first image y point position # X239.52 second image x point position # Y804.64 second image y point position # t0 type of control point (optional) # 0 - normal (default) # 1 - optimize horizontally only # 2 - optimize vertically only # 3+ (all other numbers) - straight line x/y/X/Y should never contain negative values or values that exceed the image size. Maybe this somehow happened in your case. If so, just delete that line or comment it out by starting that line with a '#'. Does that help? Carl Can-C. Dörtbudak schrieb am 11.01.10 13:06: > Hi Guys, > > i have a strange problem. I'm using the newest hugin Version from > sourceforge on a win7 64bit system. > > The thing is, when i'm trying to make some controlpoints on my own, > hugin crashes by clicking on the first point in the preview window. > This is happening really everytime i try it. > > When i start hugin a again with the same project, i get an error, that > there are 4 corrupt controlpoints. Does anyone know how to fix this > problem? > > Can >
-- 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
