So I just grabbed my phone and timed an edit on an Xact measure t.p.
Time from clicking edit until dialogue box opens and fully loads: 41 seconds
Time from clicking okay until dialogue box closes: 1 minute 6 seconds
That's nearly two minutes just to open and close. It's been this way with every t.p. dimension that I have created in 2017. Saving the program also gives me several seconds of the spinning blue wheel. If this is a bug and not just something on my end then I might have to go back to 2016 until the first service pack. Ain't nobody got time for that.
So I just grabbed my phone and timed an edit on an Xact measure t.p.
Time from clicking edit until dialogue box opens and fully loads: 41 seconds
Time from clicking okay until dialogue box closes: 1 minute 6 seconds
That's nearly two minutes just to open and close. It's been this way with every t.p. dimension that I have created in 2017. Saving the program also gives me several seconds of the spinning blue wheel. If this is a bug and not just something on my end then I might have to go back to 2016 until the first service pack. Ain't nobody got time for that.
I haven't seen this at all, even with large programs.
Is your computer busy with other tasks?
Nothing more than the usual memory load. If it means anything, two of my datums are autoplanes created with the new measurement strategies, which seem to still be in sort of a beta stage. Don't know if that's slowing things down.
Might also be noteworthy that all autofeatures were dialed in because I'm measuring a fixture that I don't have a model for. Again...don't know if that's relevant.
Seeing the same issue as
Numbers Game , although I haven't timed it, but 2017 feels quite a bit slower in XactMeasure than 2016. And with the "Group" coordinates issue is back in 2017, it takes even longer time to finish creating a TP as I have to uncheck them and each uncheck is a 2-3 second hourglass - just to uncheck it... I assume there is some calculating going on in the background that is taking longer time in 2017. No - there are no background tasks going on.
I expect this to be fixed to the next release (at least uncheck the "Groups" checkboxes as default, ffs).
New odd little bug. I'm not 100% sure it is 2017 specific, but it happened on 2017.
I accidentally fat fingered an extra 0 in an auto feature. No big deal. The weird part is what happened on execution.
There is a vector point followed by an edge point. The edge point was at 10000 in Z, which is 9000mm away from reality. The program ran the vector point, and stopped as it triggered on the surface of the part with an out of machine parameter error. So,
no retract or avoidance move of the vector point before erroring out.
It should have at least finished the retract and/or avoidance move of the vector point before throwing an error for the next feature.
I have some strange problems too. I want to measure the hole with Auto Circle and the graphics of tip paths show some strange paths. If I have smaller number of hits, paths are shown on different heights, if I have a bigger number of hits (over 10) the graphics show less paths then defined, and the machine takes less points for circle (if there is 6 hits on graphics it takes 6 hits). I hope the pictures are big enough to see my problem.
