hugin crash with photometric variables in 'v' lines
Bug #679185 reported by
Bruno Postle
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Hugin |
Won't Fix
|
Medium
|
Unassigned | ||
Panotools |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In order to optimise photometric parameters with vig_optimize it is necessary to add 'v' line entries for the photometric parameters:
v Ra0 Rb0 Rc0 Rd0 Re0 Vb0 Vc0 Vd0
These are correct, but if I open a .pto project like this I get this error (generated by parser.c in libpano13):
Conflict in script: Line 16
Multiple Instances of variable b
Image number: 0
Hugin then crashes or sometimes allows me to continue. The problem appears to be that libpano13 expects single character v-line entries.
Changed in panotools: | |
status: | New → Fix Released |
Changed in hugin: | |
status: | Incomplete → Won't Fix |
To post a comment you must log in.
Does this still occurs? I can't reproduce the issue.
Loading a pto file with photometric parameters in v line works without problems.