"Failed to detect a focus position for feature <featurename>"

Thank you all, I am very grateful that it isn't a local issue (just me). It saddens me though that the quality of the software is moving backwards - again.
Why wasn't this detected during the testing of the software? I don't mean the technical preview - I mean the "rigorous testing" Hexagon is mentioning in the readme's that accompany each released version? If there really was a rigorous testing, issues like this should not pass by unnoticed. Let's sprinkle this with the fact that bfire85 reported this very same error during the 2016 TP. At that point, this very error/issue should have been included in the internal testing routines! I think we have different dictionaries when it comes to the definition of "rigorous"...

I think I speak for everyone using PC-DMIS when I say that I'd rather wait longer for a "more working" version than forcing two releases/year that are below standard.

Shape up, ffs.

Thank you all, I am very grateful that it isn't a local issue (just me). It saddens me though that the quality of the software is moving backwards - again.
Why wasn't this detected during the testing of the software? I don't mean the technical preview - I mean the "rigorous testing" Hexagon is mentioning in the readme's that accompany each released version? If there really was a rigorous testing, issues like this should not pass by unnoticed. Let's sprinkle this with the fact that bfire85 reported this very same error during the 2016 TP. At that point, this very error/issue should have been included in the internal testing routines! I think we have different dictionaries when it comes to the definition of "rigorous"...

I think I speak for everyone using PC-DMIS when I say that I'd rather wait longer for a "more working" version than forcing two releases/year that are below standard.

Shape up, ffs.