Group runs twice

[dtmtim]

Running 2019R2. When creating a Grid or UV scan I always use the "to points" option because my customer wants to see T-Values on the individual points in the scan.
In 2019R2 PC-DMIS automatically puts the points in a group. I like this because it saves a step and keeps the edit window nice and clean.
The problem is when the program is executed the group gets executed twice. This is a waste of time and whats worse is PC-DMIS does not move to clearance in between the 2 executions which can cause a crash.

Anyone else experience this?

[KIRBSTER269]

When you first create the scans before turning them into points, how many crossings do you have? sometimes when you have to many crossings it will continue pass your 2nd point on a linear open scan, and the "D" on a closed scan, on a closed scan, you should have no more than 2 crossing, there has been occasions that I had to have more, but not often.

[dtmtim]

When you first create the scans before turning them into points, how many crossings do you have? sometimes when you have to many crossings it will continue pass your 2nd point on a linear open scan, and the "D" on a closed scan, on a closed scan, you should have no more than 2 crossing, there has been occasions that I had to have more, but not often.

No such occurrence on a grid or UV scan. Dumping them to points creates vector points. The problem seems to be related to the "group" function.

[KIRBSTER269]

Just throwing that out there because those vector points are based on your scan. Example if you put a thickness on the graphics and turn them to points, it will create vector points based on that scan settings. Just throwing that out there, because that occurred on a few occasions for me.

[Kp61dude!]

Cut and Paste points outside group and delete the group command... just to test.

[AndersI]

I just did a test offline in 2019 R2 SP1, and no such thing happened. Are you sure you didn't happen to create both a scan and a group of points?