Oh yeah good point Acid... I did forget about that! I will have to play around with NumOptCycles more. It seems like manually finding and setting the optimal "start" value might be the best choice (since parameters are inter-dependent on each others start values) but perhaps NumOptCycles is a good compromise if you just need a quicker result.