Thank you Lukas, > ... copying enblend and enfuse executable from the older > build to your current installation should be enough.
Yes that seems to have done the trick; at least on my "awkward.pto" - testing memory limits obviously requires big projects which takes a long time ... > IIRC the reason why the new build has the image cache disabled is that > the image cache sometimes causes black lines with large panoramas and > it doesn't work with multithreading. If the Hugin FAQ [1] is still up-to-date, enfuse.exe enables image_cache and enfuse_openmp.exe doesn't. I found copies of both in my "program files/Hugin/bin". Though I haven't tried it, perhaps setting enfuse_openmp as the "alternative" to enfuse in Preferences/Programs dialogue might be a more obvious way to disable image_cache when necessary ? The same trick might also work for enblend.exe and enblend_openmp.exe ? [1] http://wiki.panotools.org/Hugin_FAQ#Selecting_right_version_of_enblend-enfuse_binary_for_Windows Many thanks for your help, John. -- 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
