Latest release caused hole selection issues with CAM

[robpicinic]

The latest release of Fusion 360 (Nov 28th 2018) seems to have broken the hole selection command with drilling in CAM. see attached image for issues. Selection of similar holes does not consistently select all holes that match size and shape as it did before.

[paul.clauss]

Hi @robpicinic

Thanks for posting! I've seen a variety of issues with "Select Same Diameter" not working - would you mind sharing the file you are working with so I can try to place which particular issue may be occurring? If you'd like to keep the design private, please feel free to direct message me a downloadable link.

If you are working with a model imported from a different CAD program, please let me know where the file is from and what file format was used to bring it into Fusion.

We appreciate you bringing this to our attention - please let me know if you have any questions.

[paul.clauss]

Hi @robpicinic

Thanks for sending the file over - this appears to be related to internal ticket CAM-12080. I'll pass the design along to the development team and we appreciate you reaching out!

For the time being, I was unable to find a way to work around the problem without manually selecting points for all the holes. This is not an ideal workaround, but the diameter range selection option also missed a number of the holes even when given a large tolerance. We'll be looking into this.

[jeff.kelley · Accepted solution]

Hello @robpicinic,

Thank you for the file. I'm sorry I broke this workflow for you, I was trying to clean up and correct some of our low level code and seem to have missed test cases like this one when trying to check that I hadn't broken anything. We have a fix that should be coming out soon though I cannot make any promises. With this upcoming fix I did manage to see the correct behavior on your file.

Sorry again

Jeff Kelley

Software Engineer

[robpicinic]

Thanks for the feedback. I can’t wait to see the update and hope it’s soon. 😃

[jeff.kelley · Accepted solution]

@robpicinic I hope 2 weeks wasn't too long for you to have to wait. Today's update contained the fix.