Found an issue using 1.2.3 and the DotTune module on 5D3.
I found it working fine on prime lenses, but on my zoom lenses DotTune would scan all the ranges and would never find a boundry (like described above). I tried the prime/tele both, and the applicable wide / tele settings and got the same result.
I assumed that ML was having trouble adjusting the values, so I switched to "All by same amount" mode, and this worked fine. So it appears when a zoom lens is attached ML can only adjust the AFMA on the "All by same amount" mode.
Anyhow, so the easy workaround is to do the DotTune with this mode then manually change the values for the Tele and Wide once the values are calculated.
I found it working fine on prime lenses, but on my zoom lenses DotTune would scan all the ranges and would never find a boundry (like described above). I tried the prime/tele both, and the applicable wide / tele settings and got the same result.
I assumed that ML was having trouble adjusting the values, so I switched to "All by same amount" mode, and this worked fine. So it appears when a zoom lens is attached ML can only adjust the AFMA on the "All by same amount" mode.
Anyhow, so the easy workaround is to do the DotTune with this mode then manually change the values for the Tele and Wide once the values are calculated.