2014-11-06 19:09 GMT+01:00 John Muccigrosso <jmucc...@gmail.com>: > I've tried to quit and restart the app, even boosting the image cache > memory to 2048 when I did it. No luck. > > Now, I just added some more control points and re-optimized and all is > well. Not sure those steps had anything to do with it though. >
I am almost sure that some (most?) optimization results will never trigger this bug, so that re-optimizing quite probably was why the issue disappeared. I always use the "progressive" optimization technique (where you first optimize by positions, then by positions-and-view and so on and I often noticed that when this bug appeared, I could avoid it by resetting all optimization parameters and then stopping at the last step which did not trigger the bug. So my workflow when seeing this issue would be: - use one optimization level - check in the preview if the bug does not appear - use the next optimization level ... - if the bug appears, undo the last optimization. -- Frederic Da Vitoria (davitof) Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- 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 hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CANe_y9S_pNDrZdQXXtGjJ3ch8z3HhB9k-k-95iKM%2BqcpF8265w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
