Hi, that are a lot of questions...
Am Freitag, 29. Mai 2020 02:42:40 UTC+2 schrieb LF Martins: > > > and it happens even if in the project sets the optimization as only: > # specify variables that should be optimized > v r1 > v p1 > v y1 > v TrX1 > v TrY1 > v TrZ1 > > > This I can't reproduced. When only the variables of the second images are marked for optimisation, then only the variables of second images are modified. > > It is also clear the *autooptimizer* does not respect the "disabled" tag > for the third image. This means the GUI uses something else to do the > optimization? > > Is it a known bug? If yes, is it planned to be fixed? > Optimisation of only active images is a feature of the GUI. This was not yet ported to the command line tool. So I would not call it a bug, instead it is a missing feature ;-) I implemented this feature for autooptimiser in the default repository. So now the active state of the images is respected when additional specifying the switch --only-active-images. So the new behaviour is backward compatible to the old behaviour. Side question: how do add and remove the "disable" tag in a batch script? > pto_var --enable-image=.. --disable-image=.. (added last week) Thomas -- 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/253b0349-bdaf-4057-bb6e-9ebe5c6d5966%40googlegroups.com.
