Doing some pretty basic programming, vector points. I have noticed that when picking the vector points, the vectors only show 3 decimal places in the auto feature window. No big deal, I kind of figured that was partially due to the fact that I have it set to report 3 decimal places (or the fact that some 'new' programmer didn;t like to see all those numbers in a little bitty box). Then, when I create the point, the vectors carry out to 7 places, just like they did in V3.5 and ALL previous versions. Then, just for shitsandgiggles, I clicked on FIND (not FIND VECTORS) to see what it would give me for an answer (I had previously noticed that when using FIND, the vectors went out to 7 places) and I got some bogus values.

I click on the surface and it gave me a vector (in Z) of 0.657

I created the point and in the edit window the vector was 0.6570417

FINE SO FAR!

I clicked on FIND and got a vector of 0.6569384!

Tried on the next point, FIND VECTORS and they STILL don't match what is created in the edit window.

I didn't change anything, no values, nothing. By clicking FIND it should give me all the same values as I had when I clicked on the surface since thepoint isn't moving. SO, WHY is the vector not 'calculating' the same when you click on the surface as it does when you then tell it to FIND? They should match 100% all the way out to 50 decimal places.

SO, which vectors are right and which are wrong? Granted, it isn't much, BUT IT HAS NEVER BEEN A PROBLEM BEFORE (V3.5 and older), WHY IS IT ONE NOW? Just yet another case of something that was working correctly now being totally MESSED UP!!!!! WHY IS THIS? WHY IS SOMETHING as basic as the VECTOR POINT, something that EVERY VERSION OF PCDMIS HAS, BEING MESSED WITH WHEN THERE WAS NOTHING WRONG TO BEGIN WITH, nor has there been for, what, 10 years? I can do this all day long in V3.5 and it will give me the same vector, over and over and over and over, point after point. But OH NO, NOT IN THE NEW VERSION, it's messed up there!

"Here ya go, bend over, and receive the blessing of B&S/Wilcox/Hexagon. Sorry, no lube today!"

Gee, it really makes you start to wonder if ANY PART of this software can be trusted if something as basic (to CMM's) as the VECTOR point can be messed up after all these years of working correctly. What else is messed up that no one has caught yet? Something else that is so basic, so simple, and has worked correctly as long as anyone can remember, and so are not even looking now to see if it is still right?

Well B&S/Wilxcox/Hexagon, anyone looking? Y'all say that you "try" to keep up with what's happening on the forum, but "no guarantee" that you will look. Well, are you looking now?

I click on the surface and it gave me a vector (in Z) of 0.657

I created the point and in the edit window the vector was 0.6570417

FINE SO FAR!

I clicked on FIND and got a vector of 0.6569384!

Tried on the next point, FIND VECTORS and they STILL don't match what is created in the edit window.

I didn't change anything, no values, nothing. By clicking FIND it should give me all the same values as I had when I clicked on the surface since thepoint isn't moving. SO, WHY is the vector not 'calculating' the same when you click on the surface as it does when you then tell it to FIND? They should match 100% all the way out to 50 decimal places.

SO, which vectors are right and which are wrong? Granted, it isn't much, BUT IT HAS NEVER BEEN A PROBLEM BEFORE (V3.5 and older), WHY IS IT ONE NOW? Just yet another case of something that was working correctly now being totally MESSED UP!!!!! WHY IS THIS? WHY IS SOMETHING as basic as the VECTOR POINT, something that EVERY VERSION OF PCDMIS HAS, BEING MESSED WITH WHEN THERE WAS NOTHING WRONG TO BEGIN WITH, nor has there been for, what, 10 years? I can do this all day long in V3.5 and it will give me the same vector, over and over and over and over, point after point. But OH NO, NOT IN THE NEW VERSION, it's messed up there!

"Here ya go, bend over, and receive the blessing of B&S/Wilcox/Hexagon. Sorry, no lube today!"

Gee, it really makes you start to wonder if ANY PART of this software can be trusted if something as basic (to CMM's) as the VECTOR point can be messed up after all these years of working correctly. What else is messed up that no one has caught yet? Something else that is so basic, so simple, and has worked correctly as long as anyone can remember, and so are not even looking now to see if it is still right?

Well B&S/Wilxcox/Hexagon, anyone looking? Y'all say that you "try" to keep up with what's happening on the forum, but "no guarantee" that you will look. Well, are you looking now?

## Comment