Am Dienstag, 20. September 2016 14:47:50 UTC+2 schrieb Bernd D: > > I want to show 4 issues: > > 1. On site *Optimizer* in table *Image Orientation*, column *Trx*, > *TrY*, *TrZ* show only rounded to integer values. > > No. The values are shown with 1 digit.
> > 1. On site *Stitcher*, edit fields *Horizontal* and *Vertical* show > only rounded to integer values. > > Yes. The optimal fov calculates with a resolution of 1 deg. And the most use case is a panorama with a high fov. So for this use case you don't need a higher resolution. > > 1. On site *Stitcher*, button *Calculate field of view*: Calculate for > *Vertical* a value that is *Horizontal*-1 (this is reported on my > first post). > > The is a special case and happens only in this particular case. This is already fixed in the repository, as written in my answer already. > > Per default the *-–fullscale* option for *cpfind.exe* is not set. Without > this option *cpfind* work not correct (find lesser CPs and misplace > this). > Please don't state such general statements. In most case cpfind works fine without fullscale. There may be case where full scale is better suited, e.g. your images with a very low resolution and a repeating pattern. But this is specific to this use case and does not apply in general. -- 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/2a51987a-91f4-46f9-b13f-4041edf13d36%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
