I've found a bug in the property distance components (both the regular and NxN versions).

If one of the properties that you are providing as part of the distance calculation has no variance (but is not equal to 0), and you select Mean Center and Scale, all of the distance values return as 0 or NaN.

Also, (and I think this is a feature, but one that is not explained well) if you define a range of properties to use in the distance calculation, the range is based on the first and last properties you provide, not on a numerical range that may exist in the property names. So if you have Prop1, Prop2, Prop4, Prop3, if you specify Prop1-Prop4, in this case you only include the first 3 properties (i.e. the numerical range is ignored). This is sensible, I suppose, if you have property names that are all text, but can be confusing if you have numerically indexed properties. Just thought I'd mention it.

I've attached a protocol that illustrates these bugs/features.